thx for the hints,
but as i mentioned before - the (tab)-layout isn't my main concern: my main
problem is how do i map/use those activities,places,views. most example
suggest 1:1:1 releationship. also the interfaces imply this: the start
method of activity "acceptsOneWidget" (i know this could be ignored by
simply create a compisite widget and return/ show this one - but is this the
intended use?). Examples for activityMapper (and the Interfaces**) accept a
place and return one activity.
but 1:1:1 would mean that each display area is a view "presented" by one
activity started/bound ton one place. but this conflicts with my (current)
understanding of places and activities. my understanding is that a place
could start/bound to n(>=1) activities, each activity could controll/present
m(>=n) views.
my question is: is this contradiction a problem of my understanding or a
problem with examples and some interfaces delivered with places/activities?
(or probably an problem of my understanding of the interfacess**)
**
AppActivityMapper implements ActivityMapper
...
@Override
public Activity getActivity(Place place)
---------------------------
...HelloActivity extends AbstractActivity...
...
@Override
public void start(AcceptsOneWidget containerWidget, EventBus eventBus) {
HelloView helloView = clientFactory.getHelloView();
helloView.setName(name);
helloView.setPresenter(this);
containerWidget.setWidget(helloView.asWidget());
}
...
--
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.
