Re: [Pyobjc-dev] AppKit/__init__.py complexity

[Chris R. <cp...@em...>]

Bill--

Can you expand on this thought a bit for a Cocoa/PyObjC newbie?

I guess I'm not sure what the informal protocols are used for, and why 
they're interesting...

Thanks for any explanation.

On Friday, February 28, 2003, at 12:46  PM, Bill Bumgarner wrote:

> On Friday, Feb 28, 2003, at 12:41 US/Eastern, Ronald Oussoren wrote:
>> The current versions of the informal_protocol definitions also list 
>> whether methods are optional or not, and that cannot be inferred from 
>> the header files. Not having the additional information wouldn't be 
>> too bad, I'm sure Cocoa will complain loudly if an object doesn't 
>> implement the required parts of a protocol.
>
> Yes.  It does... but not as loudly or as elegantly as PyObjC.   Having 
> whipped off about a dozen little PyObjC apps to make my world a more 
> sane place, I can say with enthusiasm that the informal protocol 
> validation done by PyObjC is a huge boon!  It'd be even better if it 
> spewed a method definition that could just be copied/pasted and even 
> better if there were a command line tool that could be used to dump 
> all the decls for a particular informal protocol.
>
> I would hate to see that functionality lost -- given that the 
> protocols don't change over time, I will volunteer for the tedious 
> task of making sure that there are decls for all of 'em based on my 
> previous emails analaysis of what needs to be wrapped.   Then it is 
> just a matter of updating them over time based on the release notes 
> coming from Apple -- given that there have been no major API changes 
> except with major releases of the OS and *that* has only been 
> additions, it should not be hard to stay on top of this stuff.

Cheers!
--Chris Ryland / Em Software, Inc. / www.emsoftware.com