Hi NullPointer, Thanks for posting up about this. There are a couple of issue reports and potential patches in the works to try to help with both problems (helping to load large, multi-module applications asynchronously and slow compile times), but some of them still have a way to go.
I think it would be great if you could follow-up on those issue reports to help surface them to the team. You can find them at the link below: Issue #620 - Better multi-module support through GWT.runAsync(): http://code.google.com/p/google-web-toolkit/issues/detail?id=620 Issue #356 - There are a few dupes of this one with useful info, just search for "compiler speed" on the Issue Tracker http://code.google.com/p/google-web-toolkit/issues/detail?id=356 Help for compilation speed is actually available in the trunk, so you can already get an idea of how much faster your compilations can get in a parallelized compiler. While waiting for GWT.runAsync(), I think a solution along the lines of what Ian and Ruquan have suggested could help in the interim. From what you mentioned, it seems that it might be a bit of a pain to implement since you have a lot of custom adapters, but it might be something to try until runAsync() becomes available. Hope that helps, -Sumit Chandel On Mon, Oct 6, 2008 at 5:17 AM, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > Hi Dear, > > I think my solution will help for large GWT applications, even the > application my have more than 2000 screens. > > 1. We defined a general screen rendering engine; > 2. The screen definition are defined in XML where it can be > unmarshalled into java object graph and then could be serialized into > string in GWT RPC format. > 3. The screen definition could be put on the server file system or > database, and the screen could be loaded on demand on GWT client side. > 4. The screen definition could also be put on the javascript > dictionary, and then loaded on demand on the client side. > screens["orderForm"]="abdddkdklfdkalfjaf;alsdla"; > The String is the GWT serialized screen definition, the javascript > dictionary is generated based on the user role, and is generated in > the main page, for GWT we only have one page, right? > 5. Only event listener need to be added for a new screen, where the > code lines amount is pretty small. > > > The compilation time and javascript size is never a problem for > us,and the screen could be customized on the fly. > > > > > On 10月5日, 下午10时20分, NullPointer <[EMAIL PROTECTED]> wrote: > > Sorry, in the last line in the above post I meant to say 'Also the > > generated code is much like a hand-coded code and therefore > > there are no runtime rendering overheads. I hope you are clear.'. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
