Xref: utzoo comp.windows.misc:605 comp.graphics:2831
Path: utzoo!attcan!uunet!husc6!tut.cis.ohio-state.edu!allosaur.cis.ohio-state.edu!bob
From: bob@allosaur.cis.ohio-state.edu (Bob Sutterfield)
Newsgroups: comp.windows.misc,comp.graphics
Subject: Re: Window Toolkits and Systems for a bunch of systems.
Keywords: Window Toolkits, Window Systems, Portability
Message-ID: <18311@tut.cis.ohio-state.edu>
Date: 21 Jul 88 13:15:49 GMT
References: <732@muddcs.Claremont.EDU>
Sender: news@tut.cis.ohio-state.edu
Organization: The Ohio State University Dept of Computer & Information Science
Lines: 25

In article <732@muddcs.Claremont.EDU> lam@muddcs.Claremont.EDU (Grace Lam) writes:
>Are there any graphics toolkits around that can help?  For example a
>drawing and widget toolkit that provides a common interface to a
>variety of window systems, so I only have to write graphics code
>ONCE.

This is what Open Look (OPEN LOOK is the real name of it, but I don't
like to SHOUT all the time) is supposed to provide.  Sun is
implementing it for NeWS, ATT is implementing it for X11, and the spec
book will allow others to implement it for Joe's Window System,
Plumbing Supply and Bowl-a-teria.

In theory, there will be common set of objects and toolkit calls for
you to code.  Then you take your same source and link it against
libOLX11.a or libOLNeWS.a or perhaps libOLJWSPSB.a, depending upon
your mood and what platform you'd like to ship it on.  Careful
adherence to the specs should lend portability, at the possible
expense of nifty features native to a particular window system.

I haven't seen either toolkit nor the specs, but the demos look kinda
pretty and the idea is attractive as well.
-=-
 Bob Sutterfield, Department of Computer and Information Science
 The Ohio State University; 2036 Neil Ave. Columbus OH USA 43210-1277
 bob@cis.ohio-state.edu or ...!{att,pyramid,killer}!cis.ohio-state.edu!bob