Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!crdgw1!crdgw1.ge.com!barnett From: barnett@crdgw1.crd.ge.com (Bruce Barnett) Newsgroups: comp.windows.misc Subject: Re: Open Look versus Motif, and it's effect on NeWS vs. X. Message-ID: <5355@crdgw1.crd.ge.com> Date: 19 Feb 90 11:27:38 GMT References: <2935@auspex.auspex.com> <:8S1SU7xds13@ficc.uu.net> Sender: news@crdgw1.crd.ge.com Reply-To: barnett@crdgw1.crd.ge.com (Bruce Barnett) Organization: GE Corp. R & D, Schenectady, NY Lines: 24 In-reply-to: peter@ficc.uu.net (Peter da Silva) In article <:8S1SU7xds13@ficc.uu.net>, peter@ficc (Peter da Silva) writes: >> Unless: [dynamic linking] + a single API for both Motif and Open Look + >> [binary compatible interface] > >That's a good point. If you can get the APIs together for Motif and Open >Look it should be possible to let the user select them. So "unreasonable" >isn't a fair description. Solbourne has a C++ package that supports both OpenLook or Motif. I saw a flyer from some vendor who has a high level toolkit that supports both Motif and Open Look. I can post a follow-up with the companies's name if people want.(I'm home right now). The problem with this is that it would be difficult to design a well-tuned application that really makes use of the UI. A good application pays attention to layout, common actions, screen management, etc. Assuming several commercial products are available, the best ones will be the ones that really make use of the UI to the fullest extent. -- Bruce G. Barnett uunet!crdgw1!barnett