You don't need to split your app into pieces. You can use any of the current
GWT standard solutions for menu-like structures (Vertical MenuBar,
StackPanel, Tree, SplitPanel, whatever best suits your app requirements). To
update your menu depending on user actions, you may use some sort of
listener pattern: a static class would register listeners for specific event
types (like refreshing data from the server), like the observer/observable
pattern. The History class from GWT lib is a good example.

For the server part, I'm currently using JSON only. I think the GWT RPC
support is an amazing idea that may increase productivity of small/medium
projects. However, my server business layer will be accessed through several
client types, and a GWT-exclusive RPC API would only make it harder to plan
and control security, auditing, etc.  My server code is on a totally
different subversion repository. The ant build process allows the static
content (gwt compiled code, images, etc) to be on a different server farm,
althrough this would require GWT code to use script/JSONP calls instead of
simpler XHR/JSON (and consequently limit it to GET HTTP requests - not an
option for an interactive application).

-- 
Renato Mangini
http://www.linkedin.com/in/mangini

On Sat, Aug 30, 2008 at 7:12 AM, jbdhl <[EMAIL PROTECTED]> wrote:

>
> > I'd split the page in two with a horizontal panel.
>
> I like that way of doing it. But how should I structure the code for
> the individual sub-pages? In separate modules? More specifically: How
> would you structure the
>  1) client side code and
>  2) sever side code
> to reflect that the application has been split up into several pages?
>
> I would really like to avoid maintaining a large monolithic chunk of
> code.
>
> >
>

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

Reply via email to