Your 'activity' idea seems to be the best one. Fragments can be used to better separate Views from Controllers, where Fragments (and it constituent child-views) are the Views and Activities are the Controllers (note that Activities would still 'directly' update the action-bar, the title-bar, options-menu, etc). You can add your own methods to Fragments. These methods can register listeners or they can update the state/appearance of a Fragment. An Activity registers a listener (e.g. Fragment.set/addOnXXXXXListener methods) with one Fragment. When the listener (e.g. the listener.onXXXX method) gets called by a Fragment, the Activity updates another Fragment in response. This way, one Fragment does not need to know anything about other Fragments, maintaining a nice separation.
-- You received this message because you are subscribed to the Google Groups "Android Developers" 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/android-developers?hl=en
