From: Gary Robinson <grobinson@tr...> - 2003-05-11 15:41:47
I've gotten great help so far from this list so I thought I'd continue
asking questions. Thanks!!! Maybe I'll be able to contribute to the
documentation as I come to understand things better.
This question is about the mechanics of working with Information Builder and
Suppose that I create an Information Builder representation of my app, then
use NibClassBuilder.py to create a skeleton Python. All well and good, but
later in the development process I will almost certainly have reason to add
new classes in Interface Builder. If I run NibClassBuilder.py I'll lose the
Python code I write in the skeleton.
Obviously, I can manually add any new classes to the skeleton and not run
NibClassBuilder at all. But I have a slight fear that there may be other
side-effects when NibClassBuilder is called other than creating the
skeleton, so that if I don't run it, I'll have problems.
So a it would be useful to have "official" suggestions for how to handle
From: Ronald Oussoren <oussoren@ci...> - 2003-05-11 15:58:49
On Sunday, May 11, 2003, at 17:41 Europe/Amsterdam, Gary Robinson wrote:
> Obviously, I can manually add any new classes to the skeleton and not
> NibClassBuilder at all. But I have a slight fear that there may be
> side-effects when NibClassBuilder is called other than creating the
> skeleton, so that if I don't run it, I'll have problems.
Your fear is unnecessary. When NibClassBuilder is used as a script is
only creates the skeleton, there are no other effects. I don't always
use NibClassBuilder, but often just create the entire script by hand.