Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-pcd!hpvcfs1!stevem
From: stevem@hpvcfs1.HP.COM (Steve Miller)
Newsgroups: comp.sys.next
Subject: Interface Builder
Message-ID: <770001@hpvcfs1.HP.COM>
Date: 10 Nov 89 20:26:01 GMT
Organization: Hewlett Packard, Vancouver, WA
Lines: 25


I saw a demonstration of the NeXT yesterday and have a couple of questions
on the Interface Builder (IB), especially from people who are familiar with
Prototyper on the Mac.  On the surface IB looked very similar to Prototyper
except for the fact that (I assume) IB will generate object orientated code
and (I would hope) you can create your own interface objects to be used in
Inteface Builder.

However, one concern that I have is when you finally build you interface and
then you add all of you custom code to do the special things you program is
ment to do, can you go back to IB and change things without any grief.  With
Prototyper, you often have to re-insert your own code after making interface
changes effectively making Prototyper a one way street:  once you create an
interface and add your own code, you will probably not use Prototype again
since you've modified the files it created.

Does Interface Builder have similar problems? I would like to get a feeling
to how it works and how easy it is to use Interface Builder through the
entire development process.  I'm looking for the dream development 
evironment that would allow truely using object orientated (visual)   
programming through the whole development process.

Steven Miller
Vancouver Division
Hewlett Packard      ...hplabs!hpvcfs1!stevem