Re: Semi-document architecture
Re: Semi-document architecture
- Subject: Re: Semi-document architecture
- From: Rob Keniger <email@hidden>
- Date: Fri, 4 Sep 2009 17:15:27 +1000
On 04/09/2009, at 4:42 PM, Kyle Sluder wrote:
Sounds like a job for a custom NSDocumentController subclass.
Of course, thanks for the pointer.
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.
Ah, I see, I can override -synchronizeWindowTitleWithDocumentName in
NSWindowController. That is easier than I thought.
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?
Yes, sorry, that was a typo.
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.
Great, thanks!
--
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