Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!sei.cmu.edu!fs7.ece.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!bk19+
From: bk19+@andrew.cmu.edu (Bradley D. Keister)
Newsgroups: comp.os.msdos.programmer
Subject: MS Windows 3.0, X Windows and C++
Message-ID: <gbpaive00Uh_01nmJ1@andrew.cmu.edu>
Date: 7 Mar 91 16:35:07 GMT
Organization: Physics, Carnegie Mellon, Pittsburgh, PA
Lines: 21

I'm interested in hearing from those with experience in all of the
above.  I've spent about one year writing my research programs in C++.
I have essentially no experience with window environments, though I
have written screen interface code in C and Pascal.  I'd like to get a
sense of whether it's feasible to write interface code which could be
ported both to X (maybe Motif in particular) and MSW by encapsulating
the specifics of each into generic classes which could then be invoked
in higher-level modules.  I've seen product announcements for
commercial packages which may do this exactly, but my experience is
that large packages of this sort which "do everything" are rather
unwieldy for my purposes -- I'd rather "build from the ground up",
unless X and MSW are so intrinsically different that only large
commercial packages can address the problem.

Brad Keister
Physics Department
Carnegie Mellon U

please reply to:

keister@poincare.phys.cmu.edu