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 really redudent.. >
Hm if you want to define the activity by the place I think you can simply do it. Create an AbstractPlace that contains an abstract method like getActivity() that returns new activities for that place. Your ActivityMapper would then be more or less a three liner. If you have more than one display area you would need more than one method, e.g. getMainActivity, getSideActivity. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/8UhwpTWBmhgJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
