Re: [Pyobjc-dev] NGPython

[Helge H. <hel...@op...>]

On 01.03.2004, at 10:19, Ronald Oussoren wrote:
> IMHO the major problems are documentation and effort. If we would 
> rename methods we would basically render most existing Cocoa 
> documentation useless for Python users, using the current scheme it is 
> easy to use the existing documentation and translate Objective-C code 
> snippets into Python. Maintaining a seperate set of documentation for 
> PyObjC would be a lot of work.

Good points, yet the "usual" mapping rule is pretty easy to explain and 
understand and just makes sense. Like if you have an Objective-C method 
with "With", the "With" denotes keyword arguments (initWithSet:, 
NSSet(set=)).
I don't think this is much more difficult for the regular developer to 
remember.

> Maintaining the mapping would also be a lot of work (and the 
> development would be even more work).

No, not at all. Told from experience ;-)

> PyObjC development is done by a very small group in their spare time, 
> there just isn't enough room to do the additional work that would be 
> required for maintaining the mapping.

Well, I would volunteer to do that. Should be some 2h per MacOSX 
release (= per year) ;-)
Don't forget that you do *not* need to map every single selector from 
every single class. You only need to map additional selectors and even 
with those, there can be default mappings.

regards,
   Helge
-- 
http://docs.opengroupware.org/Members/helge
OpenGroupware.org