hey, I'm asking you guys for a best practice. Imagine the following case:
- there is a class ``UserProfileActivity`` where you as user see your profile - you switch from your profile to another persons one, this causes the class ``UserProfileActivity`` to be used again - ``UserProfileActivity`` won't get a call to ``start`` again, cause the ActivityManager knows this is the same instance again. But it needs a notification to reload its data for another user... Problem: for the ``ActivityManager`` this is the same thing, for the user/context/content its not. I see two solutions so far, but I'm not that much convinced of any. Maybe there is one much better ;) - any activity must be handled as a unique instance - no singletons - we apply a custom interface that triggers some kind of ``reloadData`` method. Anyone has two cents left ;) andi -- 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.
