Here was the key to my original question (and looking at it, I think it
may be more an IB question than a PyObjC question):
I thought that once one uses IB to "define" a class (pick the parent
class and add outlets and actions) and subsequently to instantiate a
class into an instance that goes into that palette window, the only way
to add more outlets/actions after the instance has been wired was to
delete the instance, add the outlets/actions to the class definition
and then re-instantiate and re-wire it.
However, it seems as though all one needs to do is to switch over the
class definition and add the actions/outlets as appropriate. After
that, when ctr-clicking to/from the instance, the new actions/outlets
of the class definition will appear.
Hope this helps anyone reading this thread. I wholeheartedly agree with
Jack's point. PyObjC is true magic on the scale of pixie dust but right
now there are just too many hurdles to get through unless one is really
family with the cocoa way of doing things. I've found that the PyObjC
examples help a ton, especially the "WebServices Tool" one which is the
closest to being a real app. Perhaps one thing to do is to have others
who have created 'real' apps submit them to be included in the examples
Thanks to all who answered.
On Monday, March 24, 2003, at 01:47 AM, Ronald Oussoren wrote:
> On Sunday, Mar 23, 2003, at 22:00 Europe/Amsterdam, Jack Jansen wrote:
>> On zaterdag, maa 22, 2003, at 19:48 Europe/Amsterdam, Ronald Oussoren
>>> What I usually do is:
>>> - Paint a UI in Interface Builder, including the initial definition
>>> of one or
>>> more model classes/objects.
>>> - Generate a template using AppKit.NibClassBuilder (used a script)
>>> - Fill in the template.
>>> If the model interface changes later on I change the definition in
>>> IB and update the python files. There is no need to rewire anything
>>> in > IB.
>> This procedure needs to be documented. and probably in a step-by-step
>> way. It is essential to PyObjC
>> development, but it is also pretty obscure. Even more obscure than
>> the corresponding ObjC procedure
>> (which you also will never find if you don't do one of Apple's
> Thanks for the tip. It is pretty obvious to me, hence the lack of
> documentation. I'm sure there are more features/procedures that are
> obvious for someone familiar with PyObjC but not for a newby. Please
> keep us informed of them. "There are no dumb questions, only lacking