I usually associate the url/token in the browser address with a single
Activity/Place. I usually just revert back to the old style
Presenters , rather than attempting to nest additional Activity/
Place(s).
Most of my apps use this pattern:
Activity/Place associated with the url / Activity making rpc and
loading a View
This also works if multiple Views need to be managed from the same
Activity.
If however different Views require their own data sources then the
pattern changes to:
Activity/Place associated with the url / Activity managing
multiple Presenters / Presenter making rpc and loading a View
On Dec 16, 8:52 am, Jens <[email protected]> wrote:
> Your activity mappers are responsible to do this. If you dont need an
> activity for a given place then just return null (or a placeholder activity
> that can show a custom message or something, e.g. "Please select an entry
> in the table above"). If you return null in your details activity mapper
> then your details panel will be empty.
>
> -- J.
--
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.
