Thanks Sean, Benjamin and I. Savant for your responses so far, >You could use the various setMetadata: methods of NSPersistentStore and NSPersistentStoreCoordinator. I thought metadata was meant to make stores searchable with spotlight? Is this the correct usage? I claim ignorance here :)
>You could have a NodeViewState, joined to the Node by a relationship, for each node to store the view-only parameters. This is true, but then I have to include extra entities within the data model that have nothing to do with the graph itself but only with the View. >IF PERSISTED Yes, I'd like to save this document with a specific layout and open it. >What's your aversion to storing this within the nodes themselves? If >they're meant to be persisted at all, and these properties belong to >your Node instances, then there's no obvious reason (from your >description) to create a separate entity to store them. What's the >problem? Be specific. Well, perhaps I didn't explain it well enough. Let's say, in the future I want to have a different View. In that case specific location X and Y for this view will mean different things or may not be required at all. Perhaps other View will not need background color or border info, etc. Within my model objects I just want to store model related information, nothing that pertains to a particular view. Nevertheless I would like to store whatever view information I have with the document so when I open it that view is back to the state user left it at. _______________________________________________ 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
