Hi Daniel, This sounds a lot like what I described in http://groups.google.com/group/google-web-toolkit/msg/2debad456eda5de9 and it seems to be the pattern that's emerging.
There's some great stuff from the community on that thread re: code splitting and GIN, too. /dmc On Mon, Dec 13, 2010 at 11:57 AM, Daniel Simons <[email protected]> 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 > Note the above solution requires keeping a copy of the current Activity > inside each Activity Mapper. Does anyone see flaws in this solution? If so > could you provide a more appropriate way to solve this? > 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. > -- David Chandler Developer Programs Engineer, Google Web Toolkit http://googlewebtoolkit.blogspot.com/ -- 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.
