Xref: utzoo comp.graphics:2880 comp.windows.misc:621
Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!rutgers!ucla-cs!sm.unisys.com!trwrb!trwspp!spp2!urban%algol
From: urban@algol (Michael Urban)
Newsgroups: comp.graphics,comp.windows.misc
Subject: Re: windowing system independent -- user interface toolkit
Message-ID: <1369@spp2.UUCP>
Date: 27 Jul 88 14:45:24 GMT
References: <677@mv06.ecf.toronto.edu> <11334@jade.BBN.COM>
Sender: news@spp2.UUCP
Reply-To: urban@spp2.UUCP (Michael Urban)
Organization: TRW Inc., Redondo Beach, CA
Lines: 20

In article <11334@jade.BBN.COM> mlandau@bbn.com (Matt Landau) writes:
>In comp.windows.misc, apollo@ecf.toronto.edu (Vince Pugliese) writes:
>>for those looking for a user-interface toolkit that is more or less 
>>independent of windowing system though X will be needed...
>
>Contradiction in terms.  "Window system independent" means you do 
>NOT require X11, or any other particular underlying window system,
>for the client application to compile and run.  That's the whole point.

Yes and no.  The real world is occasionally an illogical place.
We have similar requirements here, in which the toolkit should
be fairly WS independent, but must first be built on X (for example,
because the customer is currently using HP workstations).  However,
X dependencies are not allowed, since someday the package might
have to run on NeWS or Macintoshes or some yet unwritten base.
It is a bit like requiring a Curses-like package that will be
operating system independent, but must be able to run on Unix.
   Mike Urban
	...!trwrb!trwspp!spp2!urban 

"You're in a maze of twisty UUCP connections, all alike"