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: "Daniel T. Staal" <email@hidden>
- Date: Thu, 28 Jun 2007 15:54:33 -0400 (EDT)
- Importance: Normal
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.
Daniel T. Staal
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
_______________________________________________
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