Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!raven.alaska.edu!bionet!agate!ucbvax!cis.ohio-state.edu!magnus.acs.ohio-state.edu!sample.eng.ohio-state.edu!purdue!news.cs.indiana.edu!mips!samsung!munnari.oz.au!mel.dit.csiro.au!yarra!bksmel!cwy
From: cwy@bksmel.oz.au (Chris Young)
Newsgroups: comp.windows.x
Subject: Re: XView Toolkit
Message-ID: <540@bksmel.oz.au>
Date: 28 Jun 91 09:01:23 GMT
References: <9106180734.AA04888@delphi.uucp> <1991Jun18.161315@wsl.dec.com> <1991Jun19.052126.9204@aplcen.apl.jhu.edu> <537@bksmel.oz.au> <1991Jun24.090219.28243@resam.dk> <1991Jun27.212000.15348@aplcen.apl.jhu.edu>
Organization: BKX AUSTRALIA Pty Ltd, Melbourne, Australia
Lines: 10

> Having written Xview, OLIT, Xaw, and Motif code, I think that Xview is far
> easier to learn than any of the others. To say otherwise is plain silly. You

Bad luck for you.....
As I said, this may be your opinion, it's not mine !

"Silliness is in the eyes of the coder"

Frankly, if you are so damn smart - why don't you write a better toolkit and
we will all immediately start using it -):