Re: NSDocument-based app limitations?
Re: NSDocument-based app limitations?
- Subject: Re: NSDocument-based app limitations?
- From: Mark Munz <email@hidden>
- Date: Mon, 29 Mar 2004 23:35:40 -0700
On Mar 29, 2004, at 10:24 PM, Scott Anguish wrote:
On Mar 29, 2004, at 10:44 PM, Mark Munz wrote:
I sure wish TextEdit would have been written as an NSDocument-based
application, or maybe it can't be?
TextEdit predates NSDocument by a good bit, which is why it isn't
written with it.
For me, seeing a good example (like TextEdit) that uses NSDocument
would I think
1. Show how to do some very common tasks in a document-based program
2. Show some of the weaknesses in the current NSDocument model so they
could be improved
So I'll rephrase my main question. Can I dynamically change the
filetypes that show up in the save dialog? Do I hack in and muck with
the UI elements (doesn't seem the "right way" -- but maybe that's the
way everyone does it)? Or do I have to by-pass the whole NSDocument
code completely and do it myself (like TextEdit does)? I keep thinking
that I must be missing something obvious for this type of behavior.
Or is it better to create another subclass for my RTF-type document
--making it harder to switch between plain and RTF text, but perhaps
solving the save as filetype problem with showing all types. That
creates new UI issues -- like requiring two "new document" menu items
since they would be very different documents now.
Or should I just abandon the whole NSDocument model and do what
TextEdit does?
Thanks.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.