From: tmoran@bix.com (Tom Moran)
Subject: Re: OO and large packages
Date: 1998/04/24
Date: 1998-04-24T00:00:00+00:00 [thread overview]
Message-ID: <3540ac93.302795@SantaClara01.news.InterNex.Net> (raw)
In-Reply-To: 353f7983.1926480@SantaClara01.news.InterNex.Net
>You could look at the (by now conventional) approach of
>Xaw/Motif/Tk/Java, and for all I know MS-Windows, and regard the outer
>window as a container for window interface components or widgets
>(which may of course be themselves containers, recursively, but
This is a painting/drawing sort of window, so on input it needs to
handle mouse movement and buttons, keyboard, and menu. On output it
needs to draw various things. Then there is the general window
housekeeping. It makes for a large package and doesn't break into
obvious pieces.
.
The question is more general, though: Do non-trivial OO objects
always lead to large packages.
next prev parent reply other threads:[~1998-04-24 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-23 0:00 OO and large packages Tom Moran
1998-04-23 0:00 ` Simon Wright
1998-04-24 0:00 ` Tom Moran [this message]
1998-04-24 0:00 ` Joseph Wisniewski
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox