Re: Design question
Re: Design question
- Subject: Re: Design question
- From: "I. Savant" <email@hidden>
- Date: Mon, 14 Jul 2008 21:35:21 -0400
Does anyone have any comments on my design so far?
Overcomplicated. :-) If I were writing a quick utility to do as
you're looking to do, I'd probably implement it all in a single
application controller. There's no real design advantage in something
with so few requirements and simple is always best.
If your project becomes more complicated (the app controller is too
big to manage mentally / textually, or some parts of your controller
layer need to be reusable), you can decide what to parcel out into
more logical divisions. For now, though, there's nothing wrong with
using a single controller and nothing to gain from using multiple ones.
Also, the general advice (with which I concur whole-heartedly) is
to steer clear of Cocoa Bindings until you've masted the Cocoa Basics.
That is, for your tables, try the NSTableDataSource protocol to see
the nuts and bolts of tables before worrying about the more
complicated Bindings machinery.
Good luck and happy coding!
--
I.S.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden