[Pyobjc-dev] toplevel modules

[Ronald O. <ous...@ci...>]

I'm getting worried about the toplevel modules/packages introduced by 
PyObjC, especially after introducing 3 new ones while playing around 
with the PreferencePanes framework (none of these are in CVS at the 
moment).

We currently introduce 4 toplevel packages, the bridge itself and 
wrappers for Foundation, AppKit and AddressBook. If the hacking I'm 
doing on Python based plugins ends up with something usefull there will 
also be PreferencePanes, ScreenSaver and InterfaceBuilder packages.

The reason I'm starting to get worried is that both AddressBook and 
InterfaceBuilder are not only Cocoa frameworks but also AppleScriptable 
applications. From my limited research I deduct that the Python 
interface to the AppleScript functionality in AddressBook would also be 
in a module named AddressBook if MacPython would have such a 
convenience module (which is doesn't) [e.g. try 'import CodeWarrior', 
you get a module that allows access to CodeWarrior through its 
AppleScript interface].

Another reason for worries is that AddressBook also has a C API 
(although just using PyObjC would probably be easier). Other frameworks 
might also have both a C and Objective-C API, which might lead to 
conflicts if both versions are wrapped (DiskRecording seems to have 
both C and Objective-C APIs).

Opinions?

Ronald