Please note the change in the 2nd bullet point. There is no GWT version dependency when running compiled code.
On Tue, Dec 1, 2009 at 9:47 AM, Jeff Chimene <jchim...@gmail.com> wrote: > A couple things: > > - You don't need to establish such an Eclipse -> browser link for GWT. > Eclipse has a lot of web development framework you don't need for > developing > w/ GWT. > - You test your compiled code in any of the Linux browsers. This means > deploying and serving the JavaScript in response to an HTTP request. That > is > a step that you ordinarily don't do while in the code->compile->debug loop. > You don't need Eclipse Web development for this. Simply compile the code in > GWT, deploy it to a web server, start your browser outside Eclipse, > navigate > to the URL. > - You don't say which GWT version you're using. For anything < 2.0, GWT > provides its own browser for Linux. It's a standalone version of FireFox > packaged for embedded development in tools like GWT called "XULRunner". > Please note that this hosted mode browser is what you will use most when > developing GWT code. GWT is designed to test your application before it's > compiled; which means that you won't use a standalone browser while testing > your application (for GWT < 2.0) > - The upshot is that what you're trying to do probably isn't what you > want > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
