@Thomas Thanks for the feedback. I use the same pattern as you describe. I have many commons modules that every application include if required. - Ed
On Wed, Oct 12, 2011 at 10:57 PM, Tomasz Gawel <tomaszga...@op.pl> wrote: > @Uemit > you can write one module to be used in all pages and use code > splitting feature to download only what is needed by the particular > page. > i do that this way. > another habit i worked out over years using gwt is to use onModuleLoad > method only to register js callbacks. how does the module behave on > particular page is then "scripted in javascript". however i had to > slightly "enhance" bootstraping script :). > generally my pattern is to write "whole client logic" with gwt (using > code splitting and merging modules as much as possible) an then > slighlty "script it" on page to customize its behaviour. > > > -- > 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 > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
