Re: Semi-document architecture
Re: Semi-document architecture
- Subject: Re: Semi-document architecture
- From: Kyle Sluder <email@hidden>
- Date: Thu, 3 Sep 2009 23:42:11 -0700
--Kyle Sluder
On Sep 3, 2009, at 11:10 PM, Rob Keniger <email@hidden> wrote:
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).
Sounds like a job for a custom NSDocumentController subclass.
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.
Your NSDocument subclass can handle this And you can disable the
titlebar path control easily enough.
However, I still want one window per app, undo support and Save menu
item functionality, which all come "for free" with the NSDocument
architecture.
I assume you meant one window per document?
Would I be best off to migrate away from the NSDocumentController/
NSDocument architecture and shoehorn my own document management
controller logic in its place?
No. You will still get a lot out of NSDocument with a moderate amount
of customization.
--Kyle Sluder
_______________________________________________
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