On Monday, December 13, 2010 5:57:03 PM UTC+1, Daniel wrote:I have solution for nesting activities that appears to work for all general cases. I would like to share my solution and find out how others are solving this problem. Here is my process:
1) for each panel of my site I have a unique Activity Manager/Mapper 2) the mapper maps to one or more activities via the 'getActivity' method 3) when a place change occurs getActivity is called for each mapper and has 3 possible outcomes a) returns a new Activity so that it can update its associated panel b) returns the current Activity so that the panel does not change (stays the same as from previous state) c) returns null so that the panel is removed from the ui I don't see nesting here. It's exactly how activities are meant to be used (from what I've been told): http://tbroyer.posterous.com/gwt-21-activities-nesting-yagni Note the above solution requires keeping a copy of the current Activity inside each Activity Mapper. Does anyone see flaws in this solution? No, that's how it's supposed to work. You can use a CachingActivityMapper though instead of doing the book keeping yourself (possible coupled with a FilteredActivityMapper so the Place that reaches the CachingActivityMapper can be compared equal to the previous place). Have a look at the Expenses sample, that's exactly what it does for the "master" activities. Thanks, Daniel -- 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.
