Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!dimacs.rutgers.edu!seismo!seismo.CSS.GOV!bonnett
From: bonnett@seismo.CSS.GOV (H. David Bonnett)
Newsgroups: comp.windows.x
Subject: Re: MOTIF vs Athena. Practical to conditionalize?
Message-ID: <49296@seismo.CSS.GOV>
Date: 27 Dec 90 16:13:22 GMT
References: <3132@gazette.bcm.tmc.edu> <7036@mitech.com> <3165@gazette.bcm.tmc.edu> <1990Dec14.164540@ap.co.umist.ac.uk> <2024@metasoft.UUCP>
Sender: usenet@seismo.CSS.GOV
Reply-To: bonnett@seismo.CSS.GOV (H. David Bonnett)
Organization: Center for Seismic Studies, Arlington, VA
Lines: 19

In article <2024@metasoft.UUCP>, alan@metasoft.UUCP (Alan Epstein) writes:
|> 
|> 	...
|> >|> MOTIF is awfully dependent upon itself.  It is very easy to use
|> >|> Athena widgets in any other Xt-based toolkit, but not MOTIF.
|> 	...
|> 
|> Does this mean that an application cannot use Motif and Athena
|> widgets together, or that they cannot co-exist in the same widget
|> hierarchy, or that sometimes there are problems with some
|> organizations of these widgets?

I have been able to mix Athena widgets into my Motif app. I am stuffing
an Athena-based group of widgets, including a homegrown table widget inside
a motif xmform. Getting the form to handle the alignment correctly is a tad
tough, but then again, it is without the addition of Athena stuff ;-)

-dave bonnett; Center for Seismic Studies, Arlington VA
      bonnett@seismo.css.gov-