Conference bulova::decw_jan-89_to_nov-90

dcp NETRIX::'~thomas/tmp/{libXmu.a,Xmu.h}' .
ranlib libXmu.a

Xmu.h & libXmu.a as an oversight was left of the UWS 2.0
kit (no one noticed it was required by the Athena widgets).
In some future release, they will appear on the UWS kit.

For now you can copy Xmu.h and the (vax) version of libXmu.a
from my directory on NETRIX::.

[this note was written by an application which is uses the Athena
widget and the above Xmu library.]

    We in ULTRIX have received some bug reports on Xmu.h and
    libXmu.a missing from the UWS V2.0 product.  Yes, it was
    an oversight to some extent.  Yes, these two particular
    files will probably be added to a maintenance release coming
    your way before too long.
    
    On the other hand, the ULTRIX product (unlike the VMS product)
    seems to have somewhat open-ended expectations of how much
    MIT stuff gets included and how much of it is supported.
    To complicate matters, the UWS V2.0 PMAX product shipped with more
    MIT clients and later versions of the libraries and header files.
    Your timely comments are encouraged (write a bug report and/or
    notify product management) both for the maintenance release and
    for future major versions of the products.
    
    John Hoffman
    ULTRIX DECwindows Engineering

I am working on the port of a rather large piece of software from the
MIT Athena project to the Ultrix/DECWindows environment (Ultrix 3.0 UWS 2.0). 
Besides the Xmu.h and Xmu.a problems mentioned in this topic earlier (thanks 
john h. for helping me!), the only major problem I have come across an 
inconsistency in two structure definitions between MIT's 
/usr/include/X11/CompositeP.h      file and Ultrix's 
/usr/include/mit/X11/CompositeP.h  files.

At the end of this note I have included the two versions of the structure
definitions. To summarize, Ultrix's definition for the structure types 
CompositePart and CompositeClassPart are missing fields that are in MIT's 
definitions.

Specifically, the field "Cardinal num_mapped_children" in CompositePart from MIT
is missing in Ultrix and the fields "XtWidgetProc move_focus_to_next" and 
"XtWidgetProc move_focus_to_prev" in CompositeClassPart from MIT have been
replaced with "caddr_t extension" in the Ultrix version.

The software I am porting uses these structures and fields when creating
some new widget types. Has anyone else run into this problem? Was this code
written using an old version of these files? Have we tracked accurately
the state of MIT's X environment? Do we care? Any suggestions on coding around 
this inconsistency?

I would also appreciate if anybody could point me to a notes conference or
topic which deals with X/DECWindows software porting issues specifically...

Thanks in advance.....

Mark J. Post, BOSE AD, DTN 381-0897


************************** MIT's VERSION *************************************

typedef struct _CompositePart {
    WidgetList  children;	     /* array of ALL widget children	     */
    Cardinal    num_children;	     /* total number of widget children	     */
    Cardinal    num_slots;           /* number of slots in children array    */
    Cardinal    num_mapped_children; /* count of managed and mapped children */
    XtOrderProc insert_position;     /* compute position of new child	     */
} CompositePart;
 
typedef struct _CompositeClassPart {
    XtGeometryHandler geometry_manager;	  /* geometry manager for children   */
    XtWidgetProc      change_managed;	  /* change managed state of child   */
    XtArgsProc	      insert_child;	  /* physically add child to parent  */
    XtWidgetProc      delete_child;	  /* physically remove child	     */
    XtWidgetProc      move_focus_to_next; /* move Focus to next child	     */
    XtWidgetProc      move_focus_to_prev; /* move Focus to previous child    */
} CompositeClassPart;


*************************** Ultrix/DECWindows Version *************************
 
typedef struct _CompositePart {
    WidgetList  children;	     /* array of ALL widget children	     */
    Cardinal    num_children;	     /* total number of widget children	     */
    Cardinal    num_slots;           /* number of slots in children array    */
    XtOrderProc insert_position;     /* compute position of new child	     */
} CompositePart,*CompositePtr;

typedef struct _CompositeClassPart {
    XtGeometryHandler geometry_manager;	  /* geometry manager for children   */
    XtWidgetProc      change_managed;	  /* change managed state of child   */
    XtWidgetProc      insert_child;	  /* physically add child to parent  */
    XtWidgetProc      delete_child;	  /* physically remove child	     */
    caddr_t	    extension;		/* pointer to extension record      */
} CompositeClassPart,*CompositePartPtr;

That looks like the differnce between X11R2+ intrinsics (DECwindows, UWS) and
X11R3 intrinsics.  We were just a little too close to the end when R3 came out.
I am not in DECwindows development, but I would expect those to be fixed in
the next release.  Any comments from people in the know?

Dick

I just did a diff between these files in UWS2.1 FT 1 and it seems to be fixed.
May also explain why so many of our homegrown widgets here broke down when we
went from UWS2.0 to UWS2.1...

    Yes, you can find a lot of UWS V2.0 problems fixed in UWS V2.1,
    including omitted files and R3 MIT clients.  
    
    No, the DECwindows development environment (include files, Toolkit,
    and other components) is not the same under ULTRIX as in standard MIT.
    The differences are often not large.  Nevertheless, you may have
    noticed that MIT include files are in their own /usr/include/mit/X11
    directory to keep them separate from the DECwindows /usr/include/X11
    files.  No, I am not aware of any requirement to "fix" this (not to say
    that we didn't try in UWS V2.0), but maybe this is on the agenda for
    the next major version.  Unfortunately, I've been too busy getting
    the current version out the door to deal with futures.
    
    If you think it's important to have an integrated X and Toolkit
    development environment, then do the right thing and request it
    through Product Management and the Phase Review process and/or
    write bug reports which clearly indicate what's broken.
    
    John Hoffman
    ULTRIX DECwindows Engineering

    re .5
    
    So now the question is if UWS2.1 FT 1 is available (for internal use
    only) to me....
    
    Mark J. Post BOSE AD DTN 381-0897