Xref: utzoo comp.windows.x.motif:3123 comp.windows.ms.programmer:2748 comp.windows.x:36960
Newsgroups: comp.windows.x.motif,comp.windows.ms.programmer,comp.windows.x
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!boulder!yertle.Colorado.EDU!raney
From: raney@yertle.Colorado.EDU (Scott Raney)
Subject: Re: Motif API for Windows 3.0 SDK
Message-ID: <1991May29.174438.19174@colorado.edu>
Sender: news@colorado.edu (The Daily Planet)
Nntp-Posting-Host: yertle.colorado.edu
Organization: University of Colorado, Boulder
References: <1991May23.062443.22131@syacus.acus.oz.au>
Date: Wed, 29 May 1991 17:44:38 GMT
Lines: 18

One potential problem with this is that on the same hardware (386) a
trivial Motif application is about 1.2 MB while a comparable
MS-Windows application is about 100KB.  While it's true that 386
systems with lots of RAM are becoming more common, they're still
relatively rare.  Given the tuning required to get a widget based app
to work properly, it would not be possible to just have a Motif API
without carrying along most of the widget code as well.

If you really want portability, use XVT (from XVT here in Boulder).
It works, and without the huge memory penalty for Windows (plus it
runs on the Mac, too!).  Porting an application is usually pretty easy
(hours or days, not weeks) if you're careful not to use OS calls too
often.
-- 
======================================================================
Scott Raney                            No other person or organization
raney@boulder.colorado.edu              can be held responsible for my
(303)499-9855                                opinions or actions