Re: GWT 2.1 Activities – nesting? YAGNI ? - an example of where you NEED it !

Another option would be to look at a 3rd party framework. As Thomas pointed out, the GWT team isn't trying to address every use case, and that's where pulling in other frameworks can help. There's no shame in recognizing that you have a complex use case and using any tools available to help. I haven't tried them, but people often speak favorably about gwt-platform (http://code.google.com/p/gwt-platform/).

Finally, I want to point out that you may not want to affect the history for every interaction in sub-views. It's nice for bookmarking, but would make use of the browser history buttons very frustrating. You may only want to change the history token when the main subject of the activity (the thing typically in the center display) changes. You could always provide a feature to create a reliable link from the current view (like the Google maps "Link" feature). That might have the same complexity in terms of implementing your view state management, but it's still something to consider for usability.

-Brian

On Tue, Nov 30, 2010 at 6:57 AM, Thomas Broyer <t.broyer@gmail.com> wrote:

On 29 nov, 23:44, zixzigma <zixzi...@gmail.com> wrote:
> the article also argued, that having the same size/fixed regions leads
> to consistent layout.
>
> in the case of Fixed "WIDTH", that is true.
>
> but if your regions have sub-regions, the sizing is no longer the
> Width, but rather the HEIGHT.
>
> our WEST region, can have WEST_NORTH, WEST_MAIN, WEST_SOUTH,
> and the "HEIGHT" of these sub-regions might required to be different
> in different workspaces.
>
> in one workspace, WEST_NORTH height could be 100px, while WEST_SOUTH
> height is 300px, in another workspace, different Height size.
> having different heights, while maintaining the same width, is STILL
> CONSISTENT.
>
> with the approach suggested in the article posted above,
> one has to add additional West Regions, to accommodate for the use
> case described above,
> resulting in ActivityManagers/Mappers/Code size to grow
> exponentially !

Your "regions" are not required to have a fixed size, you're not
required to use layout panels either. How about using SimplePanel
widgets inside a FlowPanel, without specifying explicit sizes? That
would work too.

In your case though, I'd probably go with either:
 - Ashton's proposal
 - make each "workspace" it's own GWT app (if they're sufficiently
different to deserve it)

Or:
 - do not use activities (you can still use places if you like)
 - use activities but make your own activity manager (or whatever) to
break the limitations and og beyond what's possible with the stock
implementations; maybe try to use a main activitymanager to switch
between workspaces, and then a set of activitymanager/mapper/regions
within each workspace.

There are many possibilities, and there are no one-size-fits-all.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.