marbru@attc.UUCP (Martin Brunecky) (04/06/91)
I have a problem. I want my X client program running on machine A (say VMS),
talk to a server B which happens to run a server which supports an
extension I want ( say SHAPE to use something common ).
Now, the vendor providing Xlib on machine A does not provide the client
side of my extension (as his servers don't support it). Note the VMS
example can be equally applied to any vendor/extension combination.
I simply cannot port the MIT client side of the SHAPE extension to my
machine, as it depends on internals of the Xlib implementation,
varying from a vendor to a vendor (the only thing in common is that
the definitions of those internals are "hidden").
May be I don't understand. X was supposed to define a mechanism for
extension. I understand that the extension implementation may be very
server dependent, and that providing a uniform interface between the
X server and extension(s) code is virtually impossible.
However, I assumed that on the CLIENT side, the situation will be much
simpler. That I would be able to take anybody's extension "client side"
and lay it on the top of the vendor's Xlib. In fact, all that the
"client side" of the extension does is building/receiving Xprotocol
messages.
Any help ?
--
=*= Opinions presented here are solely of my own and not those of Auto-trol =*=
Martin Brunecky {...}sunpeaks!auto-trol!marbru
(303) 252-2499 (sometimes also: marbru@auto-trol.COM )
Auto-trol Technology Corp. 12500 North Washington St., Denver, CO 80241-2404 rws@expo.lcs.mit.EDU (Bob Scheifler) (04/06/91)
I simply cannot port the MIT client side of the SHAPE extension to my
machine, as it depends on internals of the Xlib implementation,
varying from a vendor to a vendor (the only thing in common is that
the definitions of those internals are "hidden").
The extension mechanism for Xlib is defined, in Appendix C of the Xlib manual.
Do you know of systems that do not export this interface?