Re: NSDocumentController singleton problem, part 2

FROM : Brad Oliver
DATE : Wed Dec 18 20:36:00 2002

On 12/18/02 11:49 AM, "matt neuburg" <<email_removed>> wrote:

> But you don't need the document architecture to get those, as TextEdit proves.

By that logic, I don't *need* anything in AppKit to do what I'm doing.
Rather, I'm trying to leverage as much of AppKit as possible to save myself
work, as was the general impression I had before I started working with
AppKit. I guess I was under the (perhaps mistaken) impression that I
wouldn't have to bypass a fundamental part of the framework to get what I
want. I could do away with NSApplicationMain and process events myself, but
I don't want to do that either. ;-) Anyway, I've started writing my own
NSDocument replacement class.

Suggestion for Apple: open-source AppKit. Every other major framework comes
with source, which helps developers either work around shortcomings, or
gives them a head start at developing classes that work like they want. If I
had the source to NSDocument.m, I could remove that "couldn't open a new
document" dialog, and I'd be happy as a clam.

--
Brad Oliver
<email_removed>
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.