arm@sps.com (Annette Myjak) (12/07/90)
(and vice versa!!!)
i know that in comp.windows.x(.motif) there was a bit of discussion about
this very subject, but at the time, i didn't need to know so i didn't save
the messages.
a recent request for some kind net soul to forward me this discussion thread
yielded only requests for me to forward the discussion on to other interested
parties (alas, no forwarded discussion thread was received).
therefore, i'd like to open this discussion thread again.
question 1: if you have developed a motif interface for your application,
and you want to port it to run in ms-windows, what's involved?
(problems, headaches, tricks of the trade, how difficult . . .)
question 2: reverse of question 1 -- what's involved in porting an
ms-windows interface to motif?
assistance in understanding what's involved and how difficult these ports
would be is greatly appreciated in advance.
annette myjak
arm@sps.combahman (Bahman Khamneian) (12/07/90)
In article <286@sps.com> arm@sps.com (Annette Myjak) writes: >(and vice versa!!!) > >i know that in comp.windows.x(.motif) there was a bit of discussion about >this very subject, but at the time, i didn't need to know so i didn't save >the messages. > Imagesoft have been promising to release Motif version of CommonView (windows object library) for some time now. CommonView comes in DLL form. It captures the commonalities amoung MSwindows, Presentation Manager, and hopefully, Motif. Their package comes with Glockenspeil C++. Bahman Khamneian |Tel: (206)487-5947 |Fax: (206)483-3400 MDI - Motorola |INTERNET:bahman@MDI.COM 19807 North Creek Parkway North|UUCP: uunet!mdisea!bahman Bothell, Washington 98011 | uunet!van-bc!mdivax1!bahman -- -------------------------------------------------------------- Bahman Khamneian |Tel: (206)487-5947 |Fax: (206)483-3400