> I had some time this weekend to make a variation that works > with interactive programs like gdb(1). It's unix only, > but handles stdin, stdout, and stderr asynchronously: > > http://seriss.com/people/erco/fltk/unix-bidir-dumb-terminal.cxx > > It uses pthreads and bidirectional pipe(2)s. All FLTK operation > is handled by the parent; the threads are just data pumps. > [I chose not to use add_fd() to facilitate a Windows port]
On WIN32, add_fd() will work OK for sockets, so I wonder if we could spawn/create a (win32 specific) process that handles the "remote" end of the connection and talk to that via sockets using add_fd() etc. That might be a portable way of isolating the win32 specific weirdness from the fltk end of things? > With some work, it could be extended to support windows; > the mechanics should be able to be ported to use the WIN32 > CreatePipe()/CreateThread()/CreateProcess() and friends. Yup... > The example opens up a tcsh prompt. See, that's gotta be a bug, right there! ;-) SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
