Xref: utzoo comp.windows.x:33072 comp.windows.x.motif:1987 comp.windows.open-look:658
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!shelby!msi.umn.edu!cs.umn.edu!brsmith
From: brsmith@cs.umn.edu (Brian R. Smith)
Newsgroups: comp.windows.x,comp.windows.x.motif,comp.windows.open-look
Subject: Re: Toolkit for Open Look *and* OSF/Motif Look and Feel
Keywords: toolkit, Open Look, OSF/Motif, GUI
Message-ID: <1991Feb21.173041.17254@cs.umn.edu>
Date: 21 Feb 91 17:30:41 GMT
References: <1057@attc.UUCP> <1991Feb19.210822.26826@visix.com> <1991Feb20.170617.15372@cs.umn.edu> <1991Feb20.194928.3022@Solbourne.COM>
Organization: University of Minnesota, Minneapolis, CSci dept.
Lines: 47

In <1991Feb20.194928.3022@Solbourne.COM> imp@Solbourne.COM (Warner Losh) writes:
>In article <1991Feb20.170617.15372@cs.umn.edu> brsmith@cs.umn.edu (Brian R. Smith) writes:
>>Also, OI appeared to be dual-look only on an object-by-object basis -
>>you would still have to adjust for different interface styles in your
>>application code.

>After writing many OI programs, I have not found a case where I had to
>put something like
>	if (I'm in motif)
>		do brain-dead things
>	else if I'm in Openlook
>		do other brain-dead things
>in any of the code that I have written.  Modulo funky "look", the
>Openlook and Motif style guides are not really that different.  There
>are many "feel" issues that the toolkit takes care of and that I as a
>toolkit user need never worry about.  It may take some careful
>planning, but it usually isn't that big an issue.

Hmmm.  But don't you have to limit yourself to a set of objects that
are common to both toolkits?  What happens to command (push-pin)
windows under Motif, for instance?

>>I.E. Say you were making a simple "edit" window that needed to be
>>scrollable.  It consists of a vertical string of data and a scroll
>>bar, pasted together in some magic way.  GUI X *requires* that
>>scrollbars be on the right, while GUI Y lets the user decide.  The
>>edit window must understand both of these conventions, and decide
>>between them.

>In OI there are many different types of scrolled objects.  The
>application writer can either tell the scolled object to have scroll
>bars in a specific place (like on the left and to) or tell it to use
>a vertical scroll bar and the toolkit will place it based on what GUI
>the user selected.

You hit half of my question.  So, scrollable OI objects create their
own scrollbars, correct?

Is there support for attaching completely different scrolling devices
also?  Say you have an object that is scrollable both horizontally and
vertically - could you dispose of the scrollbars and add a panner?

Thanks for investing your time to reply - my knowledge of OI was
based solely on what we got from a sales rep.
--
Brian              | <This space intentionally left almost blank.>
brsmith@cs.umn.edu |