Thanks! I'll try those solutions. What is the best practice? To put everything in a single module or to have many small modules? I guess that the compiler can optimize a lot if you put everything on a single module, but the browser is downloading code that it doesn't need if the page that the user is requesting doesn't use a specific component.
On Mar 10, 12:17 pm, Thomas Broyer <[email protected]> wrote: > On 10 mar, 15:08, renatu <[email protected]> wrote: > > > My problem is that this is getting umanagable. I have 6 compile > > scripts, 6 entry-points and etc. > > I know that I can create one big module and put all this components > > inside of it, but I couldn't figure out how to start a specific module > > with a specific host page. (eg. Page A needs component A, page B needs > > components B and C) and so on. > > Possible options: > a) if RootPanel.get("id_name") is 'null', just "don't run" > b) use a com.google.gwt.i18n.client.Dictionary to communicate > "options" from generated HTML/JS to GWT (if myDictionary.get > ("option_name") throws a MissingResourceException, or if > myDictionary.keySet() doesn't contain "option_name", then just "don't > run") --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
