From: Chad Perrin <perrin@...>
Date: 2006-07-29T08:51:52+09:00
Subject: Re: ruby threads? the point?

On Sat, Jul 29, 2006 at 08:42:58AM +0900, Eric Armstrong wrote:
> Chad Perrin wrote:
> >On Sat, Jul 29, 2006 at 08:07:10AM +0900, Eric Armstrong wrote:
> >>So how would you implement a simple keyboard-controller
> >>for threads on Windows?
> >>
> >>Or are my options restricted to full-blown GUI
> >>or nothing at all?
> >
> >You could always just implement your own text-based captive interface,
> >if that's what you really want.
> >
> Riiigghttt....
> 
> Given infinite time and energy, I could build everything
> I ever wanted or needed, and then some.
> 
> I was kind of looking for a simple solution that "just
> works" until I can get around to adding the GUI I
> eventually plan to add anyway.
> 
> It sounds so seductively simple, too: "just implement
> my own text-based captive interface". (What the heck
> is that, anyway?)

What is what -- a captive interface?  It's an interface that forces you
to do everything you want to do with a program without letting you do
other things between minor operations.  For instance, a non-captive CLI
is something like apt-get on Debian GNU/Linux or ipconfig on Windows,
while a captive interface is something like an ncurses-based program
that starts, takes input, gives output, and doesn't go away until you're
all done with it.

-- 
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
unix virus: If you're using a unixlike OS, please forward
this to 20 others and erase your system partition.