Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!uwvax!puff!cat17!blochowi
From: blochowi@cat17.CS.WISC.EDU (Jason Blochowiak)
Newsgroups: comp.sys.apple
Subject: Re: NeXT's interface builder
Keywords: NeXT, oop, objects
Message-ID: <2233@puff.cs.wisc.edu>
Date: 6 Feb 89 19:58:10 GMT
References: <8902050737.AA25930@crash.cts.com>
Sender: news@puff.cs.wisc.edu
Reply-To: blochowi@cat17.CS.WISC.EDU (Jason Blochowiak)
Organization: U of Wisconsin CS Dept
Lines: 14


	I don't know the details about NeXT's setup specifically, but the way
that it'd _probably_ work is: The application would request that the object
be activated (brought in from disk) - I forgot exactly how this is specified
in Objective-C, but it can be done... At that point, the application would
send a message to a dialog box telling it to include (in this case) the icon
that was just activated. At some point after that, the application (or perhaps
some part of the builtins) would send a message to the dialog box telling it
to draw itself. The dialog box would, in turn, send messages to each of its
members telling themselves to draw themselves, etc., etc.

Disclaimer: This is my understanding of how something like this (an object-
oriented windowing system) _MIGHT_ work, and it may be completely different
from what they actually did.