What we have doneDesigned and implemented an elaborate client/serverconnection structure Learned how (not) to use Git Researched how X works, extensively Failed multiple times trying to find shortcuts inside X to makeour lives easier Further developed how Flick will work conceptually
How X Works (in a nutshell)Program uses X libraries for user interfaceX takes the output from the program X puts the input out onto the screenUsers input is recorded by the X and analyzed by the program
How Networked X Works (in a nutshell)Program uses X libraries for user interface X client takes the output from the program X client sends info to the X server on the remote computer X server put the input out onto the screenUsers Mouse and Keyboard are sent via the X server Program never knows that it is not running on the hostcomputer
Difficulties and DiscoveriesTransferring information from X clients is a difficult problem Programmatic creation and manipulation of X clients (and howsome projects have tried, or failed, doing this) Switching display environment mid-program using the xhostprogram for remote connection authorizationAuthentication methodology (a.k.a. why not SSH?)How will we make all this work in Windows again?
Avoiding Convalescence Reliance on X11 What about Wayland? The Problem(s) with X How Wayland solves them (without breaking everything) Cross-Platform Compatibility Xming, pthread, Winsock, (oh my...)
Future Plans (short term)Simulate an SSH-like tunnel that will initiate an X programsstart up Encrypt the simulated tunnel to protect the users Pipe the socket to which ever computer the user wants tosend it to and have the remote X server accept it
Thank Yous Sean OSullivan Generosity and Support Professor Moorthy Organizing an managing RCOS Ben Boeckel Background using (projects involving) X11 RCOS Community Encouragement and Criticism Why hello there, i am glad that yo found me, it is hard to do!