Xref: utzoo comp.windows.ms.programmer:1931 comp.windows.x.motif:2589
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!sdd.hp.com!wuarchive!uwm.edu!ogicse!unicorn!n8443916
From: n8443916@unicorn.cc.wwu.edu (John Gossman)
Newsgroups: comp.windows.ms.programmer,comp.windows.x.openlook,comp.windows.x.motif
Subject: Re: Has anyone ported MS Windows code to X windows?
Message-ID: <1991Apr18.003750.26085@unicorn.cc.wwu.edu>
Date: 18 Apr 91 00:37:50 GMT
References: <1991Apr17.185135.1050@beaver.cs.washington.edu>
Organization: Western Washington University, Bellingham
Lines: 20

In article <1991Apr17.185135.1050@beaver.cs.washington.edu> bnfb@june.cs.washington.edu (Bjorn Freeman-Benson) writes:
>Some non-network connected friends of mine are interested in experiences
>Bjorn N. Freeman-Benson
	The programming models are pretty different.  If you are familiar
with lots of GUIs and program with that experience in mind, it is relatively
easy to port between them.  If you are familiar with one GUI, and try to port
to another, good luck.  MS Windows code is usually based around a huge
message receiving switch statement (the switch statement from hell).  This 
does not port well to Motif.  It works slightly better for OpenLook (using
the SunView toolkit).  
	Motif and OpenLook are certainly more than powerful enough to do
anything (and more) a Windows program would want to, but the programming
style is apt to be a bit different.

// *************************************************************** //
John Gossman
SoftSource      (206)676-0999 Phone
WWU Math Dept.
My employer stands behind all my opinions, except in public.
// ************************************************************** //