Eclipse tooling for Lift?

[Miles Sabin]

I'm about to start putting together a Lift-based website for my Scala
consulting business, and it struck me that it might be helpful if
there were support for Lift applications, either as part of the main
Scala IDE or as an extension.

Would there be any interest? What would people like to see?

Cheers,

Miles

--
Miles Sabin
tel: +44 (0)7813 944 528
skype: milessabin
http://twitter.com/milessabin

[David Pollak]

On Tue, Apr 14, 2009 at 4:46 AM, Miles Sabin <mi...@milessabin.com> wrote:

I'm about to start putting together a Lift-based website for my Scala
consulting business, and it struck me that it might be helpful if
there were support for Lift applications, either as part of the main
Scala IDE or as an extension.

Would there be any interest?

That'd be totally awesome!

 

What would people like to see?

Cheers,


Miles

--
Miles Sabin
tel: +44 (0)7813 944 528
skype:  milessabin
http://twitter.com/milessabin

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

[maku]

First of all, thank you for your efforts to provide an eclipse plugin
for Scala.

From my point of view, I would really like to have more tool support
for developing my scala apps in general. (not only in context of Lift)
As a beginner in Scala and also in Lift, tooling is the weakest
point.

In my opinion it is painful to get information via inspecting the used
libraries (Scala / Lift) (generally in Scala but especially using
Lift because of the powerful abstractions)
Inspection libraries is a main source for usage.

From my point of view I would not really benefit from "special" Lift
functionality.
But I would really benefit from a stronger general support like in
Java.


e.g. a simple example of the current situation when I want to inspect
the content of the Lift's MetaMegaProtoUser (Lift Mapper framework)
used in a common User:

object User extends User with MetaMegaProtoUser[User] ...
class User extends MegaProtoUser[User] {
...

When I want to inspect MetaMegaProtoUser (F3 in eclipse) -> the class
User is shown
When I want to inspect MegaProtoUser -> java.lang.Object is shown

When I open MetaMegaProtoUser (by type search) there is an outline
view presented. But it is not navigable and the structure of the open
file is not reflected (several traits in one source file).
It is not possible to search methods in a comfortable way (e.g. with
Eclipse quick search -> CTRL_O)

-> and so on

Important would be correct outlinining of methods, searching of
classes, jumping from method to method and so on...
The current version (I update regularly and use the daily build)
provides some func. but works not as expected.

I strongly believe that the support of the "basic" IDE funct. using
Scala would be the greatest benefit for users. Especially for those
(like me) which come new in the Scala / Lift space.

Regards,
Martin

[Miles Sabin]

On Wed, Apr 15, 2009 at 12:17 PM, maku <martin....@gmail.com> wrote:
> e.g. a simple example of the current situation when I want to inspect
> the content of the Lift's MetaMegaProtoUser (Lift Mapper framework)
> used in a common User:
>
> object User extends User with MetaMegaProtoUser[User] ...
> class User extends MegaProtoUser[User] {
> ...
>
> When I want to inspect MetaMegaProtoUser (F3 in eclipse) -> the class
> User is shown
> When I want to inspect MegaProtoUser -> java.lang.Object is shown
>
> When I open MetaMegaProtoUser (by type search) there is an outline
> view presented. But it is not navigable and the structure of the open
> file is not reflected (several traits in one source file).
> It is not possible to search methods in a comfortable way (e.g. with
> Eclipse quick search -> CTRL_O)

These issues all relate to the way that Scala is presented to the
JDT's indexer ... there are a lot of deficiencies here, I know ... if
you're on trunk at the moment you should see fairly rapid improvements
between now and the release of 2.8.0.

> Important would be correct outlinining of methods, searching of
> classes, jumping from method to method and so on...
> The current version (I  update regularly and use the daily build)
> provides some func. but works not as expected.

Hmm ... these should be pretty much fully functional both on trunk and
the upcoming 2.7.4 ... if you have reproducible examples of these
kinds of issue could you create tickets for them in the Scala Trac
with the component set to "Eclipse plugin".

[maku]

Miles, I updated today (again). And yes you are right. I can see
really beneficial improvements :-)
It feels better and better.

Thanks for your hard work!!!

Regards,
Martin

On 15 Apr., 14:22, Miles Sabin <mi...@milessabin.com> wrote:

[Heiko Seeberger]

What I really would like to see is editor support for templates, e.g. validation of lift-elements, autocompletion (attributes), etc.

2009/4/14 Miles Sabin <mi...@milessabin.com>

--
Heiko Seeberger
www.heikoseeberger.name
OSGi on Scala