> > What's the idea behind having two modules for each area (non-dev and dev)? >
The dev version contains an <entry-point> declaration that can start and show your smaller part of the app as described in my original post. So GameArea acts als library and DevGameArea is a small app that shows you the GameArea only. During compilation of your main app the compiler does not see the additional entry points if you put them into separate dev modules. Well and in general you most likely want to user different log levels / specific user agents during development anyways so a dev module is always a good idea (you don't have to change the production module). In my apps I always have: App.gwt.xml (production configuration) DevApp.gwt.xml (inherits App.gwt.xml and sets development configurations like log levels) DevAppSafari.gwt.xml (inherits DevApp.gwt.xml and defines safari as single user.agent) In all three modules I have "rename-to=app" so I only need a single host html page that includes app.nocache.js. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/tE28oshfWqYJ. To post to this group, send email to google-web-toolkit@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.
