Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!sun-barr!decwrl!gilroy.pa.dec.com!klee
From: klee@gilroy.pa.dec.com (Ken Lee)
Newsgroups: comp.graphics
Subject: Re: Suntools vs. Xwindows
Message-ID: <1684@bacchus.dec.com>
Date: 16 Aug 89 17:52:29 GMT
References: <2439@canisius.UUCP> <3466@uokmax.UUCP> <7600001@kolmogorov>
Sender: news@decwrl.dec.com
Lines: 24

In article <2439@canisius.UUCP>, jarnot@canisius.UUCP (Kevin Jarnot) writes:
> I've always
> enjoyed working in SunWindow and I'll also disagree that it is 
> "unobject oriented".  It's as close as you can get to object oriented
> in C.  The interfaces are nice and clean and VERY easy to set up.  You
> can get a half decent window interface created in hours.

Sorry, I have to disagree with this.  SunWindow and SunView are not
object oriented.  They have none of the standard object oriented
features such as classing and inheritance.  They're easy to use if the
standard panel items meet your needs, but writing your own is
impossible unless you buy a source licence (which Sun may or may not be
willing to sell you).  The X Toolkit, on the other hand, allows
classing and inheritance.  Writing your own X Toolkit widgets (the
equivalent of Sun panel items) is relatively easy.

If you don't want to write your own widgets, the existing X Toolkit
widget sets (such as Open Look from AT&T, DECwindows from DEC, and
Motif from OSF) are much richer (more powerful and flexible) than the
SunView set.  Other than that, the programming interfaces to SunView
and to the X Toolkit are very similar.  In most cases, neither is
easier to use.

Ken