We built a micro-framework on top of Activities, specialized in a few places
for editors and/or RF, but it was only to enforce best practices because the
team was new to GWT, new to MVP, new dependency injection, new to many
things.
For instance, we're using singleton views with disposable
actually i think there should be no code activity mapper as the place itself
should contain the logic on what activity it should be refferred, for each
new place activity combo i have to go though lots of boiler plate code which
is really redudent..
On Mon, Jun 20, 2011 at 3:43 PM, Thomas Broyer
The place cannot (and shouldn't!) contain anything more than an immutable
representation of some state, some place. As soon as you start having
several ActivityManagers, you can no longer ask you Place to know which
Activity should go in which display region.
See, in our app, we have 18
Am Montag, 20. Juni 2011 14:50:00 UTC+2 schrieb Elhanan:
actually i think there should be no code activity mapper as the place
itself should contain the logic on what activity it should be refferred, for
each new place activity combo i have to go though lots of boiler plate code
which is
actually that's EXACTLY what i did, only on in the place itself as thomas
thinks i did, there is only ONE place class which contains as single token
string.
the reasons for this is override gwt's type system for the places where each
place class is by default a new place, which goes against oo
