Re: How do copy:/past: messages get sent to NSDocument?

FROM : Adam P Jenkins
DATE : Mon Feb 25 23:03:51 2008

On Feb 25, 2008, at 4:09 PM, I. Savant wrote:

>> Does anyone know where this is documented, so I can
>> see exactly which events get forwarded to the document and under 
>> which
>> circumstances?

>
>  No, nobody's discovered how this works yet. It's a deep,
> impenetrable mystery, a black art the depths of which not even Apple
> fully grasps. Of course I'm kidding. :-)
>
>  The Cocoa Fundamentals guide is your best friend:
>
> http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaFundamentals/CommunicatingWithObjects/chapter_6_section_5.html#
>
>  There's also this (see the very last paragraph):
>
> http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/EventOverview/EventArchitecture/chapter_2_section_6.html#


Thank you very much for the pointers.

>  You may not like the bluntness of this, but it's meant to be helpful
> *and* realistic: You're trying to run before you can walk.  Your best
> bet is to take a detour from the advanced technologies (Core Data,
> Cocoa Bindings, etc.) and make sure you've mastered the basics (or at
> least the organization of the documentation).


I'm not sure how you assume that from this single question.  I do 
already understand Cocoa's binding system pretty well, especially 
since it's quite similar to what Smalltalk has had for many years, and 
Java's bindings framework as well.    I've got about 15 years of 
professional development experience, including a bit of database 
programming, using various ORM systems, various GUI frameworks in C++, 
Java, Smalltalk, etc, so none of the Cocoa technologies seem 
particularly novel or hard to understand.  I just find the 
organization of Apple's documentation especially unintuitive compared 
to other libraries and frameworks I've used.  Often important 
information about a class is buried somewhere in some related guide 
rather than in the class's documentation itself, so I don't know about 
it until I happen to stumble across the information while learning 
about something else.

Anyway, sorry for the rant, and thanks again for your pointers.
Adam