Re: Core Data using only one object
Re: Core Data using only one object
- Subject: Re: Core Data using only one object
- From: Uli Kusterer <email@hidden>
- Date: Wed, 25 Apr 2007 10:28:55 +0200
Am 25.04.2007 um 01:53 schrieb Steve Israelson:
These can't all be different types of entities because how would my
code ever collect em all up into a palette to provide a list of
things for the user to drag into their document?
I'm not sure I understand you here. Why *wouldn't* the different
kinds of shapes in a drawing app, for example, be different objects?
That's actually how most implementations I've seen so far, plus the
couple I have done do it.
Also, keep in mind that Cocoa has a very nice runtime, which lets
you ask for a list of classes. So, you could use that to see what
tools the client has linked into the project and add those to your
tool palette. You can have plug-in bundles from which you load even
more tools, each their own class based on a "Tool" base class, or in
the latter case better a "Tool" protocol.
By extension, I don't see why they couldn't be different entities
as well. Is there something I'm missing in this discussion?
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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