On Fri, Apr 16, 2010 at 11:24 AM, Quincey Morris <quinceymor...@earthlink.net> wrote: > I think that in this case, if the auto-updating can *safely and correctly* be > encapsulated within a single object, then it's preferable and simpler just to > do so.
This is true, but it does depend on your definition of "safely and correctly," which of course can vary over time. One of the reasons I like to split my models is because a self-contained collection of model objects is a lot easier to split off into a framework and compile into other apps—or even other architectures. Very helpful when you are porting all of your applications to a new shiny platform (in this example, the performance characteristics of NSTimer might differ sufficiently to warrant its replacement), or even just writing an importer for one of your other apps. But of course at some point you need to stop worrying about making your code portable and just sit down and write the code. :) --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
