Differences between Netbeans and Eclipse in programming GWT

[nguyen xuanhiep]

Dear all,
I am a newbie in GWT programming and have a wonder.
When I program, compile GWT program in Netbeans, it seems that the
compiled code can be run in browsers without install any plugin.
However, when I do the same work in Eclipse. Plugins are required for
running the website

So I wonder what the differences in compiling lead to this difference
in running?

[Konstantin Zolotarev]

In eclipse it runing in "debug" model. To run code into browsers without dev plugin you need to compile project Google -> GWT Compile, context menu. 

There is no good plugins avaliable to work with GWT for NetBeans.

You could find lot of info about eclipse here : http://goo.gl/UtzwM 

[Piotr Kosmowski]

We work with Netbeans, GWT, Maven and without any plugin. All you need
is to create proper project from gwt-maven-plugin archetype by
codehaus http://mojo.codehaus.org/gwt-maven-plugin/user-guide/archetype.html.
You can create it directly from Netbeans.
- To clean and compile project to war you need to hit Clean and Build.
Before you use any dev mode you need to compile your project at last
once.
- To run GWT dev console you need to go to Custom-Goals and run goal:
gwt:run (you can save it!) (This mode is faster than debug)
- To run debug GWT dev console you need to go to Custom-Goals and run
goal: gwt:debug (you can save it!) (You must attach debugger on port
8000) (It's slower than run but you can place breaks)
- To deply your project to any installed server just hit run button.
You will be asked for server to deploy.

We've choosed Netbeans because it was faster! in dev mode than
Eclipse, also for code completion, and hints that crush Eclipse.
Despite of big support from Google team for Eclipse we find Netbeans
much more comfortable tool to use.

[J.Ganesan]

We switched over from NetBeans( 6.9.1) to Eclipse because in NetBeans
we had to open two projects one for client and shared and another for
server. Also, if a shared class has some UI Component related code
which is never invoked in sever-side, we had compilation problems. In
Eclipse, it is seamless and there is only one project. But, from user
friendly point of view, we felt NetBeans was better.

J.Ganesan
www.DataStoreGwt.com
Persist objects directly into App Engine

On Oct 11, 7:47 am, nguyen xuanhiep <nguyenxuanhiep0...@gmail.com>
wrote:

[nguyen xuanhiep]

Thank you very much. I got it :)

On Oct 11, 12:36 pm, Konstantin Zolotarev