On 08/29/11 01:26, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>> The example opens up a tcsh prompt.
> See, that's gotta be a bug, right there! ;-)
>
You're right, it is a bug.. in bash!
During dev, I was getting inconsistent behavior from bash
on an old OSX 10.4.11
On 29.08.2011, at 02:37, Greg Ercolano wrote:
> 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:
Cool! Thanks you!
__
> 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 an
On 08/26/2011 09:05 AM, Matthias Melcher wrote:
>
> Hi guys,
>
> OK, I think I moved and renamed everything as planned. So at this point, feel
> free to participate, add, remove, change as you like. If anyone has code that
> can act as a frontend to command line tools, and that can handle stdin,
On 08/26/11 23:55, Matthias Melcher wrote:
> Well, for now the popen solution is somewhat OK.
> I want Fluid to launch all kinds of tools, which usually
> only requires reading characters from the tools.
> It would be nice to have some way to send characters as well,
> for example for launching gd
>
> Oh, and please send me reports for any problems you have during compilation.
>
I've just passed in a commit that was mostly a bunch of sed scripts. I mostly
translated the zlib / libjpeg / libpng headers from "..." to "fltk3jpeg/..."
and the like.
There were also a few files in all.h that
On 27.08.2011, at 02:06, Ben Stott wrote:
>
>> Hi guys,
>>
>> OK, I think I moved and renamed everything as planned. So at this point,
>> feel free to participate, add, remove, change as you like. If anyone has
>> code that can act as a frontend to command line tools, and that can handle
>>
On 27.08.2011, at 01:10, Greg Ercolano wrote:
> On 08/26/11 13:13, Evan Laforge wrote:
>>> Mmm, it probably could by replacing popen() with pipe()'s
>>> and fork()/exec(), with select() to watch the stdout/err pipe,
>>> and trapping keystrokes yourself and sending them to the stdin
>>> pi
> Hi guys,
>
> OK, I think I moved and renamed everything as planned. So at this point, feel
> free to participate, add, remove, change as you like. If anyone has code that
> can act as a frontend to command line tools, and that can handle stdin,
> stdout, stderr, and signals simultaneously, pl
On 08/26/11 13:13, Evan Laforge wrote:
>>Mmm, it probably could by replacing popen() with pipe()'s
>>and fork()/exec(), with select() to watch the stdout/err pipe,
>>and trapping keystrokes yourself and sending them to the stdin
>>pipe.
>>
>>Tricky though. I'd do it myself, but
On 26 Aug 2011, at 17:05, Matthias Melcher wrote:
> OK, I think I moved and renamed everything as planned. So at this point, feel
> free to participate, add, remove, change as you like.
Yay!
> If anyone has code that can act as a frontend to command line tools, and that
> can handle stdin, s
On 26 Aug 2011, at 17:08, Matthias Melcher wrote:
> Oh, and please send me reports for any problems you have during compilation.
The "cairo" folder needs to be moved out of the top level into the src folder
somewhere, fltk3cario I suppose, and then probably fltk3-ised too.
__
> Mmm, it probably could by replacing popen() with pipe()'s
> and fork()/exec(), with select() to watch the stdout/err pipe,
> and trapping keystrokes yourself and sending them to the stdin
> pipe.
>
> Tricky though. I'd do it myself, but this week is nuts for me
> schedule wise.
On 08/26/11 10:27, Greg Ercolano wrote:
> On 08/26/11 09:05, Matthias Melcher wrote:
>> If anyone has code that can act as a frontend to command line tools,
>> and that can handle stdin, stdout, stderr, and signals simultaneously,
>> please send code ;-). I need some kind of simple FLTK text termin
On 08/26/11 09:05, Matthias Melcher wrote:
> If anyone has code that can act as a frontend to command line tools,
> and that can handle stdin, stdout, stderr, and signals simultaneously,
> please send code ;-). I need some kind of simple FLTK text terminal.
This is as close as I'd ever got
Oh, and please send me reports for any problems you have during compilation.
The know issues are:
- no dll's yet
- always use --enable-localzlib from the command line
- many features of autoconf are not yet implemented
Matthias
___
fltk-dev mailing
Hi guys,
OK, I think I moved and renamed everything as planned. So at this point, feel
free to participate, add, remove, change as you like. If anyone has code that
can act as a frontend to command line tools, and that can handle stdin, stdout,
stderr, and signals simultaneously, please send c
17 matches
Mail list logo
