Re: GWT MVP Re-Using Activities where Caching and Filtered ActvityMapper don't work ?

Thank you for your suggestions.

I am going to experiment with them and implement them.

I have two related questions.

What do you think of the approach below:

- using GIN Providers to give us the Activities for Top/Left regions,
and binding these activities in Singleton.
do you think there is something wrong with this ?

- is it a bad idea to make an Activity singleton ?
and changing its internal state - (for example Id of the entityproxy
to display) - via setter methods
(given we have an ActivityFactory that can set few fields on an
Activity,
before returning the Activity with new state to the ActivityMapper)
for example: within ActvitiyFactory, doing something like this:
employeeDetailsActivity.setCurrentEmployeeId(employeePlace.getId())
return employeeDetailsActivity;

maybe it might be unnecessary in this case, but in a broader sense,
is it a bad design decision/code smell to make a class (activity in
this case) Singleton,
and changing its internal state, via setter methods ?

Thank You

--
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.