On 29 Aug 2011, at 14:48, Greg Ercolano wrote: > But I don't know if I ever tried using bsd sockets on windows > for unbuffered stdio interaction with a child process; do you > know that to be a stable route?
I can't say it will run 24/7, but it's worked fine where I used it. For what we are looking for here, running a worker shell, I guess the process may be relatively short lived anyway, so even if it leaks a bit it might still be fine! > > I kinda like using threads though, cause I know any weird > blocking won't hiccup the UI; the read/writes can block > all day and not affect FLTK's response. For this purpose, > I do like threads and feel I can trust them. Sure - I'm a big fan of threads, but the asynch socket stuff works well, and my idea of running all the remote stuff in a detached process gives us even better separation, so I think it can work. > > Oh, and BTW, I did try your fl_term app -- neat! No, more like surprising... Well, I was surprised it worked as well as it did anyway, especially if you look at the nasty way I cobbled it together. The real clever terminal emulation stuff I stole from Timothy Miller's GTerm VT100 Emulator (note, that code's pretty old, so that's GTerm from before the days when sticking a G on things meant Gnome...!) > It worked really well. I see it derived from Fl_Box, > so it implements all the text handling itself, and > seemed pretty fast even with big reports, like 'find /'. > (In mine, I cheated and used Fl_Text_Editor which is > imperfect for a tty, but it gets you copy/paste and > screen history for free) Yup - I thought about that, but I couldn't see a simple way to make it just be a terminal and not keep being an editor widget, so I cranked that all out by hand. Which is partly why I was surprised it worked at all... There are vague attempts in the code to make screen capture and so forth work, but I ran out of momentum before it really gelled. > > I didn't have any trouble playing with fl_term in > man pages, vi, and messing with colors, which is saying > a lot for a new terminal app. Usually tty emulation > is buggy, but it seemed pretty good. Too bad about > copy/paste, screen history, and 80x25. Yup - it turns out that getting it to resize the console is trickier than I thought it would be; actually laying out the text is no problem, but telling the shell process that the console it is writing too has changed size is surprisingly awkward. So I gave up... I thought I had a need for a special console, for a task I had in mind, but in the end I found a simpler way, and this kinda got orphaned... > But I see > you've got the bsd + sysv pty stuff in there; nice! Yup - again, the pty stuff was for linux initially, but then I was trying to get it running on OSX and they are all BSD and it got tricky. I had kinda planned to do something for WIN32 as well, but then couldn't see where to go with that. > > Hopefully one of us will get enough time to make > an actual xterm compatible terminal out of it. Might not be me - I've got radiators to drain and take down, and walls to resurface... > I never liked xterm (too much ancient athena), > and kde's term seems to want a bunch of KDE daemons > running, which drives me nuts. I've been using gnome-terminal recently - it suits me well, but I don't use (or need) much (most) of what it can do... _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
