Xref: utzoo comp.windows.x:32755 comp.windows.x.motif:1930 comp.windows.open-look:588
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!ukma!rex!wuarchive!zaphod.mps.ohio-state.edu!ncar!ico!attc!marbru
From: marbru@attc.UUCP (Martin Brunecky)
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: <1057@attc.UUCP>
Date: 14 Feb 91 16:02:05 GMT
References: <1322@ixos.de>
Reply-To: marbru@auto-trol.UUCP (Martin Brunecky)
Organization: Auto-trol Technology, Denver
Lines: 50

In article <1322@ixos.de> dieter@ixos () writes:
>Toolkit for Open Look *and* OSF/Motif Look and Feel
>
>We are searching for a special toolkit for the
>development of graphical user interfaces(GUI) based on the X Window System.
>This toolkit should allow to get the Look and Feel of both toolkits,
>namely OSF/Motif and Open Look,
>out of one single applikation programming interface(API)!
>
   Solbourne OI is probably as close as you can ever get. I think
   they did a very good job implementing UI *components* which can
   act "both ways". 

   However.
   Keep in mind that you are asking for almost impossible. The UI
   "styles" mentioned above have significant differences in the
   overall structure, layout and philosophy (though in many aspect
   both are pretty close). 
   Most "toolkits" provide COMPONENTS, and make it APPLICATION
   responsibility to use those components according to their Style
   Guide / Specification.

   So while you may find a toolkit that will provide the same API
   to (lets say) pushbutton which can be toggled between Motif and
   Open Look look and feel (behavior), the way HOW and WHERE you are
   supposed to use this pushbutton may vary significantly.

   As a result, the application layer in charge of UI *may* be
   completely different. I am saying *may* because it depends
   on the application. Where the UI is very simple, chances are
   that the application layer may be (almost) identical.

   Probably the best way to find out where a particular application
   stands is to take two guys with a paper and pencil, and let one
   of them sketch the UI using Motif Style Guide, the other one using
   Open Look specification.

   You may find out that a single API (though very desirable just
   from the learning curve standpoint) may buy you much less than
   you expect.
   Using high level UIMS may be a different ballgame. But so far
   I haven't seen one that would be so "high level".



-- 
=*= Opinions presented here are solely of my own and not those of Auto-trol =*=
Martin Brunecky                           {...}sunpeaks!auto-trol!marbru
(303) 252-2499                        (sometimes also:  marbru@auto-trol.COM )
Auto-trol Technology Corp. 12500 North Washington St., Denver, CO 80241-2404