Re: Use UI or data for logic? (hijacked from Two NSRects adjacent/touching?)
Re: Use UI or data for logic? (hijacked from Two NSRects adjacent/touching?)
- Subject: Re: Use UI or data for logic? (hijacked from Two NSRects adjacent/touching?)
- From: Paul Bruneau <email@hidden>
- Date: Thu, 28 Jun 2007 16:07:24 -0400
On Jun 28, 2007, at 3:54 PM, Daniel T. Staal wrote:
On Thu, June 28, 2007 3:36 pm, Wagner Truppel said:
OK thank you again. I will aim at doing all the logic in the
controller, keeping the data in the model and the UI in the view. I
would like to (for once) do things the right way.
I am planning on NOT using a document architecture (our company
will have only one schedule). Does that sound stupid to anyone?
It sounds fine to me. If you don't need more than one document, why
have to deal with all the extra functionality (and associated
headaches!) that come with the multiple document architecture?
Note that you'll want to be sure that they'll never -- for instance --
want to open a previous backup as well as the current schedule.
Perfectly possible to make sure that's never needed, but do try to
think
of situations like this to be sure.
Thanks. I have been thinking about and wrestling with that
possibility (and similar ones) but my current thinking based on the
skill set of my scheduling user is that one instance of the schedule
will be plenty for him to deal with :)
_______________________________________________
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