Problem with the Grooy Eclipse plug-in 1.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
14 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Problem with the Grooy Eclipse plug-in 1.0

Cedric Beust
I just tried the latest version of the plug-in it and it doesn't seem to do neither completion nor outline.

Surely I missed something...  ?

--
Cédric
http://testng.org

Reply | Threaded
Open this post in threaded view
|

Re: Problem with the Grooy Eclipse plug-in 1.0

Scott.Hickey
The outline should be working if the code is compiling. Code completion has
not be implemented.
Scott Hickey



                                                                           
             "Cédric Beust ♔"                                              
             <[hidden email]                                            
             >                                                          To
             Sent by:                  [hidden email]            
             [hidden email]                                           cc
                                                                           
                                                                   Subject
             07/25/2006 03:30          [groovy-user] Problem with the      
             PM                        Grooy Eclipse plug-in 1.0          
                                                                           
                                                                           
             Please respond to                                            
             [hidden email]                                            
                  aus.org                                                  
                                                                           
                                                                           




I just tried the latest version of the plug-in it and it doesn't seem to do
neither completion nor outline.

Surely I missed something...  ?

--
Cédric
http://testng.org
Reply | Threaded
Open this post in threaded view
|

Re: Problem with the Grooy Eclipse plug-in 1.0

Alex Shneyderman
In reply to this post by Cedric Beust
there is no completion yet,
outline should work in outline view; Ctrl+O would not work.



On 7/25/06, Cédric Beust ♔ <[hidden email]> wrote:

> I just tried the latest version of the plug-in it and it doesn't seem to do
> neither completion nor outline.
>
> Surely I missed something...  ?
>
> --
> Cédric
> http://testng.org
>
>


--
Thanks,
Alex.
Reply | Threaded
Open this post in threaded view
|

Re: Problem with the Grooy Eclipse plug-in 1.0

Cedric Beust


On 7/25/06, Alex Shneyderman <[hidden email]> wrote:
there is no completion yet,
outline should work in outline view; Ctrl+O would not work.

Outline doesn't seem to work on this simple class:

package test;

class GTest {
  static void main(args) {
    def List list = ["Rod", "Phil", "James", "Chris"]
    def shorts = list.findAll { it.size() < 5 }
    shorts.each { println it }
  }
 
  void foo() {
   
  }
}

Any ETA for completion?

Also, the plug-in chokes on classes in the default package.

--
Cédric
Reply | Threaded
Open this post in threaded view
|

Re: Problem with the Grooy Eclipse plug-in 1.0

Jochen Theodorou
In reply to this post by Scott.Hickey
[hidden email] schrieb:
> The outline should be working if the code is compiling. Code completion has
> not be implemented.

well... I tested the version people get when using the update site and I
saw that the outline is no longer repainted after a groovy file is
saved. I know the plugin was once able to do that. It is a bit iritating
to see classes and methods in the outline I deleted hours before, even
if the script is compilable. Oh and of course syntax errors are not
recognized if I save the file. Again this was possible some time ago.
Especially when not running the script directly that bahvior is not very
good. All but syntax highlighting becomes useless then. Is this intended?

And the colors... it would be nice to have the same colors as the java
plugin and to make it a bit more configurable. choosing the color is one
thing, making it bold or not another. I don't want Groovy keywords to be
bold. And some colors are not changeable, like the coloring of
Strings... pink is really not my color ;) Numbers are red, without the
possibility to change that color.... A color and fontmetrics dialog like
the one from the java editor for syntax highlighting would be very nice.

bye blackdrag

--
Jochen Theodorou
Groovy Tech Lead

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|

Re: Problem with the Grooy Eclipse plug-in 1.0

Scott Hickey-3


--- Jochen Theodorou <[hidden email]> wrote:

> [hidden email] schrieb:
> > The outline should be working if the code is
> compiling. Code completion has
> > not be implemented.
>
> well... I tested the version people get when using
> the update site and I
> saw that the outline is no longer repainted after a
> groovy file is
> saved. I know the plugin was once able to do that.
> It is a bit iritating
> to see classes and methods in the outline I deleted
> hours before, even
> if the script is compilable.

I will try to get the version on the update site
updated soon. I am always running the latest from CVS
so I don't have that an Eclipse installation handy to
test with the version on the udpate site. I just added
a method and watched the outline view update.


>Oh and of course syntax
> errors are not
> recognized if I save the file.

I'm not sure what you mean by this. Can you elaborate?

>Again this was
> possible some time ago.
> Especially when not running the script directly that
> bahvior is not very
> good. All but syntax highlighting becomes useless
> then. Is this intended?
>
> And the colors... it would be nice to have the same
> colors as the java
> plugin and to make it a bit more configurable.
> choosing the color is one
> thing, making it bold or not another. I don't want
> Groovy keywords to be
> bold. And some colors are not changeable, like the
> coloring of
> Strings... pink is really not my color ;) Numbers
> are red, without the
> possibility to change that color.... A color and
> fontmetrics dialog like
> the one from the java editor for syntax highlighting
> would be very nice.

These are good suggestions for improvement to the
editor. The default colors are the same as those JEdit
- which had (IMHO) the most extensive and helpful
color highlighting at the time I started looking at
Groovy editors. Personally, I like it that the Groovy
editor colors are different from the Java. It makes it
obvious what language I'm coding in. It sounds like
adding a checkbox/button to set colors to Java
defaults would be useful feature.

>
> bye blackdrag
>
> --
> Jochen Theodorou
> Groovy Tech Lead
>
>
---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>


Scott

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|

Re: Problem with the Grooy Eclipse plug-in 1.0

Jochen Theodorou
Scott Hickey schrieb:
[...]
>> Oh and of course syntax
>> errors are not
>> recognized if I save the file.
>
> I'm not sure what you mean by this. Can you elaborate?

I write ">>>>>" and get no error marker. I gues the compiler isn't
running then, so no outline update and no error markers

[...]

>> And the colors... it would be nice to have the same
>> colors as the java
>> plugin and to make it a bit more configurable.
>> choosing the color is one
>> thing, making it bold or not another. I don't want
>> Groovy keywords to be
>> bold. And some colors are not changeable, like the
>> coloring of
>> Strings... pink is really not my color ;) Numbers
>> are red, without the
>> possibility to change that color.... A color and
>> fontmetrics dialog like
>> the one from the java editor for syntax highlighting
>> would be very nice.
>
> These are good suggestions for improvement to the
> editor. The default colors are the same as those JEdit
> - which had (IMHO) the most extensive and helpful
> color highlighting at the time I started looking at
> Groovy editors. Personally, I like it that the Groovy
> editor colors are different from the Java. It makes it
> obvious what language I'm coding in. It sounds like
> adding a checkbox/button to set colors to Java
> defaults would be useful feature.

as taste matters here, yes ;)

bye blackdrag

--
Jochen Theodorou
Groovy Tech Lead

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|

Re: Problem with the Grooy Eclipse plug-in 1.0

Scott.Hickey
In reply to this post by Cedric Beust
Cédric,

I tried your class in the default package and in a test package, and it
compiled with the plugin that is in CVS. I will try to post a new version
to the plugin update site this evening.

I have seen people having this problem when they import projects from
outside the workspace and don't copy the files into the workspace project
directory - something that everyone running Grails seems to be doing
recently. A patch was just applied to address this bug.

Scott Hickey



                                                                           
             "Cédric Beust ♔"                                              
             <[hidden email]                                            
             >                                                          To
             Sent by:                  [hidden email]            
             [hidden email]                                           cc
                                                                           
                                                                   Subject
             07/25/2006 03:46          Re: [groovy-user] Problem with the  
             PM                        Grooy Eclipse plug-in 1.0          
                                                                           
                                                                           
             Please respond to                                            
             [hidden email]                                            
                  aus.org                                                  
                                                                           
                                                                           






On 7/25/06, Alex Shneyderman <[hidden email]> wrote:
  there is no completion yet,
  outline should work in outline view; Ctrl+O would not work.

Outline doesn't seem to work on this simple class:

package test;

class GTest {
  static void main(args) {
    def List list = ["Rod", "Phil", "James", "Chris"]
    def shorts = list.findAll { it.size() < 5 }
    shorts.each { println it }
  }

  void foo() {

  }
}

Any ETA for completion?

Also, the plug-in chokes on classes in the default package.

--
Cédric
Reply | Threaded
Open this post in threaded view
|

Re: Problem with the Grooy Eclipse plug-in 1.0

Edward Povazan
In reply to this post by Cedric Beust
Cédric Beust ? wrote:

> Outline doesn't seem to work on this simple class:
>
> package test;
>
> class GTest {
>   static void main(args) {
>     def List list = ["Rod", "Phil", "James", "Chris"]
>     def shorts = list.findAll { it.size() < 5 }
>     shorts.each { println it }
>   }
>  
>   void foo() {
>    
>   }
> }

It works for me, but I use the CVS build. I know it is not a solution for anyone
who just wants to use the update site, but checking out
groovy/ide/groovy-eclipse/GroovyEclipse from cvs will work.

However - I wonder, what version of Eclipse? I use 3.1.2, but the GroovyEclipse
plugin uses some internal Java API's, I wonder if they could have changed some
things in the latest Eclipse 3.2 M* build (or whatever they are upto now).

> Any ETA for completion?
I am working on 'F3' code browsing as a first step, and even this is getting
interesting with dynamic types. When it does enough, I will go onto completion
if someone doesn't beat me to it.
In the mean time I find I get decent completion out of Alt+/ , but it just
matches to preexisting words in open documents, not actual types/methods.

-Ed

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|

Re: Problem with the Grooy Eclipse plug-in 1.0

Scott Hickey-3
In reply to this post by Jochen Theodorou


--- Jochen Theodorou <[hidden email]> wrote:

> Scott Hickey schrieb:
> [...]
> >> Oh and of course syntax
> >> errors are not
> >> recognized if I save the file.
> >
> > I'm not sure what you mean by this. Can you
> elaborate?
>
> I write ">>>>>" and get no error marker. I gues the
> compiler isn't
> running then, so no outline update and no error
> markers

At present, the plugin only invokes the compiler when
the file is saved. After compiling, the outline view
updates.

> [...]
> bye blackdrag
>
> --
> Jochen Theodorou
> Groovy Tech Lead
>


Scott

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

12