[scala-tools] [netbeans] minimizing Shift-F11

[Andrew Gaydenko]

Caoyuan, hi!

I have noticed a fixing of https://lampsvn.epfl.ch/trac/scala/ticket/2280 in
https://lampsvn.epfl.ch/trac/scala/changeset/19310

The ticket was opened wrt Eclipse plugin, but, as I can see, it is related to
compiler interaction with IDEs in a whole.

Can this news be useful for the NetBeans plugin to eliminate frequent Shift-
F11 (as far as F11 is unuseful very often). It is indeed a big problem -
basing on ant scalac/fsc tasks noticeably eats development time and feel.


Andrew

[dcaoyuan]

On Wed, Oct 28, 2009 at 12:13 AM, Andrew Gaydenko <a@...> wrote:
> Caoyuan, hi!
>
> I have noticed a fixing of https://lampsvn.epfl.ch/trac/scala/ticket/2280 in
> https://lampsvn.epfl.ch/trac/scala/changeset/19310
>
> The ticket was opened wrt Eclipse plugin, but, as I can see, it is related to
> compiler interaction with IDEs in a whole.

If this change also affects fsc ant task (I think so), then NetBeans
should benefit from it too. We may build a snapshot and test it. (Do
not need to wait for a new org-netbeans-libs-scala.nbm, which is only
used to run plugin itself, all "ant build" on regular scala project
created by NetBeans will be applied upon $SCALA_HOME)

--Caoyuan

> Can this news be useful for the NetBeans plugin to eliminate frequent Shift-
> F11 (as far as F11 is unuseful very often). It is indeed a big problem -
> basing on ant scalac/fsc tasks noticeably eats development time and feel.
>
>
> Andrew
>

[dcaoyuan]

On Wed, Oct 28, 2009 at 12:20 AM, Caoyuan <dcaoyuan@...> wrote:

> On Wed, Oct 28, 2009 at 12:13 AM, Andrew Gaydenko <a@...> wrote:
>> Caoyuan, hi!
>>
>> I have noticed a fixing of https://lampsvn.epfl.ch/trac/scala/ticket/2280 in
>> https://lampsvn.epfl.ch/trac/scala/changeset/19310
>>
>> The ticket was opened wrt Eclipse plugin, but, as I can see, it is related to
>> compiler interaction with IDEs in a whole.
>
> If this change also affects fsc ant task (I think so), then NetBeans
> should benefit from it too. We may build a snapshot and test it. (Do
> not need to wait for a new org-netbeans-libs-scala.nbm, which is only
> used to run plugin itself, all "ant build" on regular scala project
> created by NetBeans will be applied upon $SCALA_HOME)

BTW, the original bug seemed only affected Eclipse plugin. For
NetBeans, the project is built via fsc ant task, it should already be
that only dependent files are re-built when one source is modified.

>
> --Caoyuan
>
>> Can this news be useful for the NetBeans plugin to eliminate frequent Shift-
>> F11 (as far as F11 is unuseful very often). It is indeed a big problem -
>> basing on ant scalac/fsc tasks noticeably eats development time and feel.
>>
>>
>> Andrew
>>
>

[Andrew Gaydenko]

On Tuesday 27 October 2009 19:29:49 Caoyuan wrote:
> BTW, the original bug seemed only affected Eclipse plugin. For
> NetBeans, the project is built via fsc ant task, it should already be
> that only dependent files are re-built when one source is modified.
>
> > --Caoyuan

Say, when

- edit some A.scala,
- switch to some B.scala with main()
- Shift-F6

it is common to get an error "type X noy found" on attempt to compile A.scala,
where X is, say, a trait defined in third C.scala file. Probably, it is
something related to "not-complete-parsing" problem.

[Andrew Gaydenko]

On Tuesday 27 October 2009 20:33:16 Andrew Gaydenko wrote:
> Say, when
>
> - edit some A.scala,
> - switch to some B.scala with main()
> - Shift-F6
>
> it is common to get an error "type X noy found" on attempt to compile
>  A.scala, where X is, say, a trait defined in third C.scala file. Probably,
>  it is something related to "not-complete-parsing" problem.

...or just edit A.scala, F11 and get  "type X not found".

(latests trunk is in use)

[Andrew Gaydenko]

On Tuesday 27 October 2009 22:47:34 Andrew Gaydenko wrote:

> On Tuesday 27 October 2009 20:33:16 Andrew Gaydenko wrote:
> > Say, when
> >
> > - edit some A.scala,
> > - switch to some B.scala with main()
> > - Shift-F6
> >
> > it is common to get an error "type X noy found" on attempt to compile
> >  A.scala, where X is, say, a trait defined in third C.scala file.
> > Probably, it is something related to "not-complete-parsing" problem.
>
> ...or just edit A.scala, F11 and get  "type X not found".
>
> (latests trunk is in use)

 
Caoyuan,

Another frequent error (just on F11) is like such one:

"error: value cd is not a member of package ab
import ab.cd._
one error found"

Of course, package "ab.cd" does exist.


Andrew

[dcaoyuan]

On Thu, Oct 29, 2009 at 9:24 PM, Andrew Gaydenko <a@...> wrote:

> On Tuesday 27 October 2009 22:47:34 Andrew Gaydenko wrote:
>> On Tuesday 27 October 2009 20:33:16 Andrew Gaydenko wrote:
>> > Say, when
>> >
>> > - edit some A.scala,
>> > - switch to some B.scala with main()
>> > - Shift-F6
>> >
>> > it is common to get an error "type X noy found" on attempt to compile
>> >  A.scala, where X is, say, a trait defined in third C.scala file.
>> > Probably, it is something related to "not-complete-parsing" problem.
>>
>> ...or just edit A.scala, F11 and get  "type X not found".
>>
>> (latests trunk is in use)
>
> Caoyuan,
>
> Another frequent error (just on F11) is like such one:
>
> "error: value cd is not a member of package ab
> import ab.cd._
> one error found"
>
> Of course, package "ab.cd" does exist.

I'll take a look later. BTW, you are using the latest Scala 2.8.0
trunk code, right?

--Caoyuan


>
> Andrew
>

[Andrew Gaydenko]

On Thursday 29 October 2009 16:51:32 Caoyuan wrote:
> I'll take a look later. BTW, you are using the latest Scala 2.8.0
> trunk code, right?

Sure! - both the plugin and Scala itself (if last one buildable).

Andrew