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
-~----------~----~----~----~------~----~------~--~---
