> 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
> 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)
- 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 firstname.lastname@example.org.
To unsubscribe from this group, send email to email@example.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.