i just tried to implement one little part of my little app with activities and places (before i tried "MVP Part2"). while this was nearly no problem i stumbled on refactoring/redesigning the rest - the main layout, entry point class and so on. this problems don't arose by using views and presenter since this concepts are very use case related i think (one v/p-pair for each use case?!).
but with activities and places the hole application management/ transition between use cases are involved. so i am asking me for what elements i should implement activity/place/view/Containers that only "AcceptsOneWidget". In my case my main layout is a tab layout. each tab stands for a "sub application" (different apps with different purposes).
so if i want the tabs "bookmarkable" (and log tab changes in history probably?!) how to layout the app. what should the main tab layout become - a "view" that accepts n widgets? or a simple tab layout with n tabs - each "AcceptsOneWidget"? what should the content of each tab become - a place with an activity for the sub-app? at the moment i only want to implement one sub-app with docklayoutpanel. the "real things" of each app happen in children of this layout panel. For example the west-side is a stacklayoutpanel and the one use-case i implemented so far (activity/place/view) is a child panel of this stack.
So how to layout more complex layouts in general, using activities and places? Or how should i layout my app?
thx in advance
--
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.
No comments:
Post a Comment