Eclipse Plugin Project Plan

On Sat, Jul 11, 2009 at 8:48 PM, Helfenstein wrote:
> Is there a project plan available for the eclipse scala plugin?
> Or does anybody knows, when the plugin will reach productive state?

"Productive state" meaning what, exactly?

Cheers,

Miles

On Sat, Jul 11, 2009 at 10:10 PM, Miles Sabin wrote:
> On Sat, Jul 11, 2009 at 8:48 PM, Helfenstein wrote:
>> Is there a project plan available for the eclipse scala plugin?
>> Or does anybody knows, when the plugin will reach productive state?
>
> "Productive state" meaning what, exactly?
>

Just to elaborate on what Miles said, what features do you require for
a "productive" plugin?

The 2.7.5 plugin pretty much meets my criteria, whats missing from that for you?

cheers,
Chris

Sorry, the question was not aimed for me, but I'll chime in anyway:

Basic rename refactoring (including rename-in-file without opening a
dialog) and better code completion (one that always works and without
showing duplicates and non-accessible members) is essential before I
consider the plug-in really productive. Without this feature, the
supposed advantage of statical typing for IDE support is kind of missing.

But don't get me wrong, I love the plug-in and really appreciate the
work Miles has been doing and I don't expect just a few people to
produce the equivalent of JDT, considering the countless man-hours that
have been put into JDT. And Miles said these features will likely make
it into 2.8.0 so I will be pretty happy if they do :)

Erkki

Chris Twiner wrote:
> On Sat, Jul 11, 2009 at 10:10 PM, Miles Sabin wrote:
>
>> On Sat, Jul 11, 2009 at 8:48 PM, Helfenstein wrote:
>>
>>> Is there a project plan available for the eclipse scala plugin?
>>> Or does anybody knows, when the plugin will reach productive state?
>>>
>> "Productive state" meaning what, exactly?
>>
>>
>
> Just to elaborate on what Miles said, what features do you require for
> a "productive" plugin?
>
> The 2.7.5 plugin pretty much meets my criteria, whats missing from that for you?
>
> cheers,
> Chris
>
>

Miles Sabin wrote:
>
> "Productive state" meaning what, exactly?
>

Thanks a lot for your answers.

The technology we use in our company is Java based and the tool chain is
eclipse based.
So in order to convince my colleagues using Scala, Scala has to be
integrated to our tool chain as much as possible.
Each feature that is missing in Eclipse–Scala Plugin, compared with the JDT,
will be a negative point. But of curse we can not expect that the Scala
plugin will cover everything that JDT covers.
For “productive state” I meant, that the plugin matches the following basic
requirement:
1. stability
2. compatibility: eclipse 3.5, newest AspectJ, newest Subclipse
3. basic Type navigation Scala-Scala, Scala-Java
4. Code completion (Scala-Scala, Scala-Java)

Best regards,
Alain

On Sun, Jul 12, 2009 at 11:47 AM, helpy wrote:
> The technology we use in our company is Java based and the tool chain is
> eclipse based.
> So in order to convince my colleagues using Scala, Scala has to be
> integrated to our tool chain as much as possible.
> Each feature that is missing in Eclipse–Scala Plugin, compared with the JDT,
> will be a negative point. But of curse we can not expect that the Scala
> plugin will cover everything that JDT covers.
> For “productive state” I meant, that the plugin matches the following basic
> requirement:
> 1.      stability
> 2.      compatibility: eclipse 3.5, newest AspectJ, newest Subclipse
> 3.      basic Type navigation Scala-Scala, Scala-Java
> 4.      Code completion (Scala-Scala, Scala-Java)

The 2.7.5 release of the Scala IDE lacks compatibility with the most
recent AspectJ release, but otherwise everything else on your list is
supported to a greater or lesser degree. Only you and your colleagues
can decide if it supports them sufficiently well for your purposes.

There's a great deal more to be done, and contributions of bug
reports, patches, documentation and general constructive criticism are
the best way to get the IDE closer to parity with the JDT.

Yours,

Miles