Re: NSDocument-based app limitations?
Re: NSDocument-based app limitations?
- Subject: Re: NSDocument-based app limitations?
- From: Ralph Pöllath <email@hidden>
- Date: Tue, 30 Mar 2004 12:50:57 +0200
IIRC, someone had posted a NSDocument-based rewrite of TextEdit a while
ago (pre-Bindings). Unfortunately, I cannot find it right now.
Cheers,
-Ralph.
On 30.03.2004, at 05:44, Mark Munz wrote:
In my readings, I've always heard that NSDocument is the preferred
model to use for document-based applications. However, it seems that
NSDocument is designed for only the most basic examples of documents.
Or is it that I just don't have a good NSDocument example to learn
from? Is there one out there?
I'm trying to mimic some of the behavior that TextEdit has (which does
not use NSDocument) for my application.
Like TextEdit, I have either plain text files or rich text files.
Right now they're are both using the same subclass of NSDocument.
When I save a file, I'm shown all the file types (both plain and rich)
in the filetype popup and there doesn't seem to be a way to just show
some of them. Am I missing something obvious here? The filetype info
seems to be class based and immutable -- which seems really strange.
Any pointers to perhaps some sample code that shows how to write a
NSDocument-based application that supports multiple types would be
great. Or any insights to make this easier.
I sure wish TextEdit would have been written as an NSDocument-based
application, or maybe it can't be?
Any help is always appreciated. Thanks.
Mark Munz
_______________________________________________
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.