Further to this topic, it makes me wonder on how I design a larger application using GWT. My application has as much as 200-300 screens(each screen a composite panel contains anything more than 500-1000 widgets in different tabpanels, popups etc) and how to load all these screens from a single menubar.
#1. Organizing all the code for 200 screens in to different GWT modules and makig the module containing the Menubar depend on these modules and loading the individual screens by instantiating the respective composite panel and adding to the main panel does not help bring down the JavaScript size. Irrespective of how you organize your modules, there will still be one JavaScript generated for every browser and that JavaScript will contain the code for all the classes in all these separate modules. For an application of the size of mine, the size of JavaScript is 15MB. Correct me if i am wrong #2. Second option i have is to organize the code for these 200 screens in to different modules and have different HTML page for each of these group of screens calling the respective entrypoints. The module containing the Menubar will not depend on these child modules but uses a GWT FramePanel and calls the appropriate HTML with relevant parameters and load the respective screen. But this defeats the AJAX pattern and there will be a number of round trips to the Server to load each separate screen. Any help on how to tackle the JavaScript size and how to load 200-300 different screens from the same Menubar will be much appreciated. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
