On Sep 17, 2010, at 8:58 PM, Richard Somers wrote: > My current inclination now is to change this and do all view composition, > connecting, and binding in the controller. The root view would still be there > but the controller would be doing most all of the work.
It's hard to answer such general questions well, but I'll give it a shot. Whether the views are created programmatically or created by a nib, the overall architecture of where controller code goes shouldn't change, so having view controllers for actually "controlling and interacting" with the view makes sense. As for where to put all of the view creation code, it one way or another is part of the view controller code. You can suck it out into some other reusable helper object if that's logical and useful. And feel free to have nested VCs where it makes sense though so you don't have a massive blob of view creation code, and a big code landfill for every view in the window. Dunno how much that helps, -- Seth Willits _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
