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
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
