Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!mailrus!ames!sun-barr!newstop!sun!turnpike!argv
From: argv%turnpike@Sun.COM (Dan Heller)
Newsgroups: comp.windows.x
Subject: Re: Toolkit decisions (was: XView v. other toolkits, advice wanted)
Message-ID: <132217@sun.Eng.Sun.COM>
Date: 24 Feb 90 20:05:25 GMT
References: <132173@sun.Eng.Sun.COM> <9002240235.AA10428@bach.cs.byu.edu>
Sender: news@sun.Eng.Sun.COM
Reply-To: argv@sun.UUCP (Dan Heller)
Lines: 20

In article <9002240235.AA10428@bach.cs.byu.edu> mike@BACH.CS.BYU.EDU (Mike Burbidge) writes:
> 	XView is not very object-oriented. It is simply a static set of objects
> for building user interfaces. It does not support inheritance. If there is not
> an object in the toolkit that does what you want, you build one from scratch.
> You can put XView objects together in a statically prescribed manner, but very
> often in real world applications that is not what you want to do.

I think you're confusing XView with SunView.  What you said above is
true of SunView, not XView.  Xview's model is pretty much the same as
the intrinsics (Xt).  It uses static subclassing (C doesn't support
dynamic subclassing as far as I know) and the inheritance methods
are the same as Xt.  For example, the "panel" package is subclassed
from the "canvas" package.  It's implementation clearly shows that
it uses inheritance.
dan
-----------------------------------------------------------
		    O'Reilly && Associates
		argv@sun.com / argv@ora.com
	   632 Petaluma Ave, Sebastopol, CA 95472 
     800-338-NUTS, in CA: 800-533-NUTS, FAX 707-829-0104