Re: NSDocumentController singleton problem, part 2
Re: NSDocumentController singleton problem, part 2
- Subject: Re: NSDocumentController singleton problem, part 2
- From: Brad Oliver <email@hidden>
- Date: Thu, 19 Dec 2002 12:18:19 -0600
On 12/19/02 10:57 AM, "matt neuburg" <email@hidden> 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.
>
>
No, that doesn't follow at all from what I said. So please don't pervert my
>
reasoning by claiming it does.
NSDocument does everything I want with a minimum of code, with one
exception. However, that exception means that I'd have to write a whole lot
of code. Given that one of Cocoa's main strengths is doing a lot with a
little bit of code, it's not a leap to suggest at all that Cocoa is not
well-suited for what I'm trying to do. Sure, it could do it, but in doing
so, it negates most of the advantages that I'm getting out of it.
I thank you - sincerely - for your advice and help (your other advice about
poseAsClass was right on), but that doesn't change the fact that I find this
solution very unsatisfying. This shouldn't be construed as a reflection on
your advice - it is a reflection of my surprise at what should be something
with a much simpler workaround, given my naive interpretation of what Cocoa
was before I started on this project.
--
Brad Oliver
email@hidden
_______________________________________________
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.