Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!oliveb!ames!sgi!daisy!klee
From: klee@daisy.UUCP (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: comp.windows.x
Message-ID: <2843@daisy.UUCP>
Date: 17 Mar 89 18:03:31 GMT
References: <571@ubbpc.UUCP>
Reply-To: klee@daisy.UUCP (Ken Lee)
Organization: Daisy Systems Corp., Mountain View, Ca.
Lines: 26

In article <571@ubbpc.UUCP> wgh@ubbpc.UUCP (William G. Hutchison) writes:
> How hard is it to port from SunView to X Windows 11?

Two answers:
1.  Sun is developing an SunView compatibility package for X.  It is
currently called XView, formerly called View2 and SunView 2.0.  Using
this package, SunView programs should port fairly (small source code
changes) easily to X.

2.  The X Toolkit with certain widget sets matches (or exceeds) most
of the functionality of SunView.  I expect that almost anything doable
in SunView is doable using the X Toolkit and a good widget set.  If
you're not doing anything real tricky in SunView, the port is very
simple.  Both X Toolkit widgets and SunView panel items are controlled in
the same way:  set resources (including callbacks) through argument lists,
realize the widgets/panel items, then dispatch events through main loop.
Both SunView and the X Toolkit allow you to dynamically get and set
resources, though the X Toolkit generally gives you more flexibility.
The larger widget sets, such as those from HP and AT&T probably have
widget equivalents to about all of SunView, but the MIT Athena widget
set is missing some things, such as an equivalent to SunView's canvas.
-- 
Ken Lee
Daisy Systems Corp., Interactive Graphics Tools Dept.
Internet and Smail:  klee@daisy.uucp
              uucp:  uunet!daisy!klee