On Wed, May 20, 2009 at 12:37 PM, Ken Thomases <k...@codeweavers.com> wrote: > While target-action is perfectly fine for what you're trying to do, I would > point out that controller's can have properties, too. Binding UI to a > property of your controller is another good way to handle this situation. > It leaves the responsibility in the same place -- the controller -- but > does what bindings usually do: removes boilerplate glue code.
And remember that your custom NSWindowController subclass is indeed a view-controller, and therefore a perfectly fine place to add your properties or other such logic. This is usually the first place I look at implementing any custom UI controller behavior, and it's usually the first class to get subclassed anyway, as a matter of course. --Kyle Sluder _______________________________________________ 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
