I use IntelliJ and have never used the Eclipse GWT plugin (other than a hello world example long before I actually started creating something real in GWT). I find the GWT facet to be extremely helpful, mostly for code navigation and detecting errors with conventions that normally wouldn't be checked until runtime. For example, it understands that the ID that you pass into RootPanel.get() should have a corresponding element in the HTML page. It also knows the methods for setting the style name on a GWT widget and will let you browse between those IDs and your CSS file.
Where I think it really shines is if you use GWT-RPC because it understands the relationships between the client-side async interface and the server-side interface and implementation. What this means is that if you say "go to implementation" on an async method call, it will take you to the implementation of the server-side interface. The navigation works in the other direction, too; if you say "find usages" on the server-side method, it will find invocations of the corresponding method of the corresponding async interface. It may be that the Eclipse plugin has these features too. At any rate, I think those kinds of features are really valuable when it comes to IDE support. -Brian On Nov 18, 2:52 pm, Jason Rosenberg <[email protected]> wrote: > I see in the docs that there seems to be special support for GWT in > Eclipse (with the developer plugin). > > I have been using IntelliJ, I'm wondering if I will be ok, or should > really switch to Eclipse. > > IntelliJ does seem to have a GWT 'facet', but I don't think it has all > that the eclipse plugin has. > > What are the main benefits of using the Eclipse GWT plugin? > > Thanks, > > Jason -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=.
