All right. All who commented seem to be just as undecided
about this as I was. Clearly neither solution is clean. So
I went with the one that does not break the ABI: just add one
more -parent() in the fluid code generator.
Patch and a simple fluid test program are coming up in two
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
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
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
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 terminal.
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.
Don't
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.
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,
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 this week
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2707
Version: 1.3-feature
While working on the patch for STR #2706 I decided to look into some more
fluid issues that have been bugging me for a while. Here is #1:
I
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2707
Version: 1.3-feature
Attached file fluidsubclass.fl...
Link: http://www.fltk.org/str.php?L2707
Version: 1.3-feature
fluidsubclass.fl
Description: Binary data
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
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2708
Version: 1.3-feature
While working on the patch for STR #2706 I decided to look into some more
fluid issues that have been bugging me for a while. Here is #2:
Fluid
13 matches
Mail list logo
