🚀 go-pugleaf

Oh yea.. forgot to say some good things about XVT while I
got caught up in the fervor of denigrating it.

It really does seem to be faster to code in than Motif.  Or
perhaps it's just my relative level of experience when I started
with XVT than with Motif.  After all, when I started with Motif
last year I had never written any interactive program (on a 
graphical interface or not) before.  But when I started with
XVT last december I had written 30,000+ lines of Motif.

Another person in my group started working in XVT recently.
Previously he'd been working on device drivers and performance
improvements, etc.  I don't think he'd done any GUI work.  He
didn't seem to have much trouble picking it up and even came
up with a useful technique for structuring XVT programs so that
main_event() is less cluttered.

So it's easier to learn, but much less powerful than Motif.

Oh yeah.. it is possible to write a geometry manager module
for XVT programs.  I recently had to do that.  Started with
the description of the box "widget" in the Interviews library
and implemented that.  It took 4-5 days but isn't finished
either since the programming interface to the module isn't very
nice (right now) and neither does it do all the Right Things.



-- 
<- David Herron, an MMDF & WIN/MHS guy, <david@twg.com>
<-
<-
<- "MS-DOS? Where we're going we don't need MS-DOS." --Back To The Future