Hi,
The .gwt.xml will be used only when you compile the Java code to
javascript.
So you will not be deploying the .gwt.xml.
Setting the user.agent and locale properties are just to make the
development cycle faster.
And when you actually do the final build you would not use these
properties.
I
Thanks for answering.
Is it correct that the user-agent property should be set to IE6 if I
keep on using the default GWT browser? I guess this tells GWT to only
compile the IE6 version, right? This makes me wonder whether or not
the .gwt.xml file is used on a production server, and if it is,
Is my question so trivial that no-one considers answering?
--~--~-~--~~~---~--~~
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-Toolkit@googlegroups.com
To
Well, if you are running in -noserver mode, then if you change any
server side code, including classes like DTOs passed between client
and server, you will naturally have to redeploy. You don't explain why
you have elected to run in -noserver mode, but if you did you may get
some suggestions as
any clues at all?
--~--~-~--~~~---~--~~
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-Toolkit@googlegroups.com
To unsubscribe from this group, send email to
Hi
I am writing an application that consists of two modules : a main one,
and a toolkit module which is inherited by the first one. The entry-
point used for running and debugging my application is therefore the
one found in the main module.
My problem is, when I modify at runtime a client
