Thanks for picking up the ball on this one Jens, much appreciated.
I had more or less come to the same conclusion about having one
controller per view, with the data model owning the controllers.
My actual situation is that the "data model" is in reality a vector
drawing stack with layers,
On 3 Mar '08, at 6:16 PM, Graham wrote:
The question is: would the better design be one-controller-per-view,
or a single controller supporting multiple views? In other words
should the controller typically associate with a single view or the
data model?
Generally there should be a contro
I have an object embodying a data model. In a document-based app,
there would be one of these per doc. There can be one or more views
on this data (for example a split view of it). Currently I don't have
a controller between the two - the view is pretty specific so it
implements the control
