Re: Upgrading NSDocument format, best practice
Re: Upgrading NSDocument format, best practice
- Subject: Re: Upgrading NSDocument format, best practice
- From: "I. Savant" <email@hidden>
- Date: Wed, 16 Sep 2009 10:21:30 -0400
On Sep 16, 2009, at 10:15 AM, I. Savant wrote:
In my opinion, you're on the right track. I think the simplest
solution is to create a new file extension. Forget renaming the file
- a different extension implies a different format. Doing this gives
you all the mechanisms and warnings for free: marking the old format
as "read only" (ie, the app isn't an editor of that format, only a
viewer), then providing the new extension as an "editor role
extension", when the user saves, I believe the dialog will
automatically pop up the Save As dialogue with that format /
extension (or the first editor-role extension) selected.
Wow ... let me decipher this paragraph, which I obviously didn't
proofread. :-D
When defining your document types (in the Info.plist file), you can
designate a type as having an "Editor" role. This is typical.
Unchecking this makes it a type your application will only read, but
not save. If you uncheck the editor role for your old type, then add a
new type that has the editor role, a save action on a document of the
old type should trigger the Save As dialog, with the new format (as an
editor role) selected.
Better? ;-)
As Gemmell would say: Official coffee times.
--
I.S.
_______________________________________________
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