
 The following two lists list the supplied, and missing X library calls.
I used an X11R4 API listing to develop these lists. It is my hope that
people would implement missing API's and post to the forum. Eventually,
we would have the ability to move X programs to Windows NT without having
a vendor supplied X server.

  I have also been thinking on developing a DLL frame work that would
automaticly use this library transparent to a ported X application if
the user is not running a native WIN32 X-server. If the the user is
running a native WIN32 X-server, or sets DISPLAY=Some_Remote_Machine, the
library will transparently connect the application to the "normal" Xlib
runtimes.

  This way, ported X-Windows programs would not require an expensive
($300-$500) X-Server add on package for every user that wants to use
the program, but without sacrificing the network connectivity benefits of
X when the customer has purchased an X-Server runtime.

  X-Server vendors could consider this in offering X-client support libraries
for developing X applications under Windows NT. A free, or low cost
re-distribution fee would enable this Xlib to be bundled with the application,
while having the transparent 'hooks' to take advantage of a network aware
X-server if the user has purchased one.

					John Richardson
					70541,672

