Xref: utzoo comp.windows.x:9726 comp.sys.ibm.pc:28058
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!kodak!ektools!isctsse!pajerek
From: pajerek@isctsse.UUCP (Don Pajerek)
Newsgroups: comp.windows.x,comp.sys.ibm.pc
Subject: Re: x on pc
Message-ID: <225@isctsse.UUCP>
Date: 29 Apr 89 00:37:39 GMT
References: <5309@hubcap.clemson.edu>
Sender: daemon@ektools (The Devil Himself)
Reply-To: pajerek@isctsse.UUCP (Donald Pajerek)
Distribution: usa
Organization: Eastman Kodak Telecommunication Services, Rochester, N.Y. 14650
Lines: 22

In article <5309@hubcap.clemson.edu> rajohn@hubcap.clemson.edu (r alan johnson) writes:
>I'm interested in some sort of prog or dev. tool that will allow me to write
>code that I can generate in a PC environment (DOS, not unix) and when then
>ported to X will run as well. Simply put, I want some sort of
>way to write X apps (or at least use calls that X will understand) that runs
>under DOS, without unix, networking, etc.

Either you're missing something, or I am.  Basically, the problem with
what you want to do is that X applications employ the 'Client/Server'
model; i.e., there are minimally TWO programs running, the client and
the server.  Now, there's no reason why both can't be running on the same
machine, unless that machine happens to be a single-tasking DOS machine.

If you really are restricted to PC's, then you will need two networked
machines. One of them will run an X server (there are several commercial
implementations of the X server for PC's under DOS).  The other will run
your client applications.

>				R. Alan Johnson (rajohn@hubcap.clemson.edu)


Don Pajerek