I'm still thinking this through, here's what I came up with: If there's an on/off button to show additional information on the screen, it would seem weird to m

I'm still thinking this through, here's what I came up with: If there's an on/off button to show additional information on the screen, it would seem weird to me to have the button (view) try and display the additional settings. The view has no idea what kind of environment it is in, how does it know if it can display the information without moving other things around. But a controller object managing all the views on the screen does. This also avoids subclassing or adding methods to the view.