Semi-document architecture
Semi-document architecture
- Subject: Semi-document architecture
- From: Rob Keniger <email@hidden>
- Date: Fri, 4 Sep 2009 16:10:01 +1000
I have an app in development that is currently implemented as a
document-based app, but I'm starting to think it makes little sense
for it to be so.
What I would like is for the app to have a central "document
management" window, from which you could create/delete "documents".
Although these are logically documents, I don't want the user to be
able to be saved the file anywhere on disk, I want all the documents
to be saved centrally in a location of my choosing (i.e. the
Application Support folder).
The user should not be able to do a Save As. I also don't really want
the Command-Clickable title in the document window as the location on
disk is not relevant to the user.
However, I still want one window per app, undo support and Save menu
item functionality, which all come "for free" with the NSDocument
architecture.
Would I be best off to migrate away from the NSDocumentController/
NSDocument architecture and shoehorn my own document management
controller logic in its place?
--
Rob Keniger
_______________________________________________
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