Repository navigation
Replies: 1 comment
It should be pretty straightforward to use an AF_INET socket instead of AF_UNIX for communication between client and server. Look at src/nanox/client.c for details on the client side. Remember that Nano-X client/server is reversed just like X11 is: the client runs on the "host", while the server displays all graphics and handles the keyboard and mouse, communicating all those events to client apps over a UNIX socket.
Nano-X doesn't implement X11 protocol, instead translates X11 API to its own NX protocol using the src/nx11 library. The ELKS version of Nano-X doesn't implement X11 protocol translation, X11 pretty much requires 32-bit implementation.
Most of the NX11 translation library works quite well, enough to run the FLTK GUI library which is based directly on top of X11 without changes. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have not looked at your code yet,
before i do so i thought i would just ask the expert of microwindows,
any means to achieve network server model using a host system?
do you have stubs/complete code in there or anything related to this already?
also none of this would obviously work on a elks system i assume with a full blown x11 protocol
i know for certain x11 via the network would be a very bad time due to past experience managing a business with x11 thin clients
my interest as always is specifically a elk's system.
All reactions