Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!ux1.cso.uiuc.edu!milo.mcs.anl.gov!atlantis.ees.anl.gov!korp
From: korp@atlantis.ees.anl.gov (Peter Korp)
Newsgroups: comp.windows.x.motif
Subject: Re: 1.2 Compatibility
Message-ID: <1990Nov14.061438.3849@mcs.anl.gov>
Date: 14 Nov 90 06:14:38 GMT
References: <9011132152.AA24980@servio.SLC.COM>
Sender: news@mcs.anl.gov
Distribution: inet
Organization: Advanced Computer Application Center, Argonne National Laboratory
Lines: 40
Nntp-Posting-Host: atlantis.ees.anl.gov

In article <9011132152.AA24980@servio.SLC.COM> marcs@SLC.COM (Marc San Soucie) writes:
>
>Call me a heretic, but I don't think this is an absolute must. Depending on the
>magnitude of the changes required, some degree of recompiling and even recoding
>(yes, even recoding) is reasonable, so long as two conditions are met:
>
>    1)  The changes produce some added value above and beyond percentage-point
>        performance gains or interface cleanups.
>
>    2)  You OSF types *document* the changes in a genuine, real-life,
>        ASCII-encoded PS-roffable Official OSF MOTIF 1.2 Upgrade specification.
>

No! No! NO!!!!

IMHO recoding is not an option. A recompile, okay. But if I have to go back and
support routines I wrote just to make them work with the new toolkit, I will
move to a "more stable" toolkit. I can have clients recompile, but damned if
they are about to go through the hassle of recoding or the pain of paying me
to recode it.

>You dropped the ball big-time with MOTIF 1.1, in that you provided little or no
>serious change documentation. The README file described some changes, and
>hinted at others, but determining a code upgrade path was left to the reader as
>an exercise. We are all still suffering from it, as we fuss about with our code
>trying to figure out how to use XmProcessTraversal instead of XmAddTabGroup,
>and other such inconveniences.
>

I whole heartedly agree. How were we ever supposed to figure out what was going
on? Worse yet we did not have the source to look at and see what was up. Please
document your next release!

>
>    Marc San Soucie
>    Servio Corporation
>    Beaverton, Oregon
>    marcs@slc.com

Peter