Re: Design pattern for core data, document based, graphical application
Re: Design pattern for core data, document based, graphical application
- Subject: Re: Design pattern for core data, document based, graphical application
- From: Kenneth Baxter <email@hidden>
- Date: Tue, 17 Aug 2010 20:18:11 -0700 (PDT)
- Date-warning: Date header was inserted by spool004.mac.com
Thanks Erik
Having the model doing the drawing directly like that is something I hadn't thought of. Definitely worth considering. I'll still have to observe changes in related attributes to trigger UI updates, and I have many ancillary objects that need to be involved in the process, so I may have to factor them in as supporting classes or something like that. Anyway, that gives me a good starting point, and gives me the flexibility to represent the objects on whatever view hierarchy works without having to change things.
Time to start making a few prototypes to test out the different design options...
On 18 Aug, 2010,at 01:33 AM, Erik Buck <email@hidden> wrote:
You have too many design options on the table. Try some of them in mini-prototypes to see how well they work and then drop some of the ideas.
_______________________________________________
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