I've been accustomed to making my views as dumb as possible and creating a ViewMediator wrapper class to handle all the "smarts" such as handle user interaction with the view and writing updates from the model to the view.
After reading up how fragments work, I am a bit of a loss as how will this workflow would continue to work. Orientation changes or garbage collections may cause the fragment to disappear and then reappear/restored to a completely new instance. So whatever reference that my ViewMediator referenced could be invalid. With activities, it wasn't so bad because I could always rely on the onCreate() method to re-instantiate all the artifacts.
My questions is how does one craft a fragment such that the behavior of it is separate from the fragment. Or should I be coupling the behavior into the fragment making it essential a Mediator as well. But that comes at the cost of attaching dependencies like the Model (where the Mediator reads & writes data) or the Controller (which needs it to fire off application wide behaviors).
