Re: Documentation frustrations
Re: Documentation frustrations
- Subject: Re: Documentation frustrations
- From: Greg Titus <email@hidden>
- Date: Sat, 9 Jul 2005 15:25:58 -0700
On Jul 9, 2005, at 2:09 PM, Dietmar Planitzer wrote:
However, in the case of the NSWindowScripting category separating
the documentation doesn't make sense. Both NSWindow and
NSWindowScripting are implemented by the AppKit as it is today. In
both cases we're dealing with methods belonging to the same class,
namely NSWindow. Further, NSWindowScripting is not an informal
protocol in the sense that you as an application developer would be
expected to implement any of the methods declared in that protocol
unlike say NSDraggingDestination That's why I would not even call
it an informal protocol. Thus, having NSWindowScripting in the
AppKit protocol section does not make sense. At least not in my view.
Actually, I would argue that NSWindowScripting is much closer to an
informal protocol like NSDraggingDestination than it is to the rest
of the methods in NSWindow, and therefore ought to be documented
separately.
NSWindowScripting is a bunch of methods which should generally _not_
be called from code. They are methods that duplicate other existing
functionality on NSWindow, and exist only as a separate 'interface'
for AppleScript to call. You only need to be aware of methods like -
setIsVisible: if you are subclassing NSWindow and need to have some
kind of different behavior when the "is visible" property is set from
AppleScript. So since they aren't intended for calling in code and
only for subclassing, it is very like an informal protocol with an
existing default implementation.
- Greg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden