RE: [Spiderape-devel] adding generic "prompt for input" support

[Jaap de W. <jaa...@gm...>]

basicly, your idea is not new,
Most javascript implementations (in browsers) know about the 'prompt' the
'alert' and the 'confirm' function. When we just agree to use functions with
the same name and behaviour in all UI implementations we are ready with this
part.
Another issue is common graphical and curses like functions.
For this part I think a common (virtal) base class should be nice.
> -----Original Message-----
> From: spi...@li...
> [mailto:spi...@li...]On Behalf Of stephan
> beal
> Sent: dinsdag 3 januari 2006 20:44
> To: spi...@li...
> Subject: [Spiderape-devel] adding generic "prompt for input" support
>
>
> Hi again!
>
> Here's an idea which just came to mind...
>
> Consider a JS function like:
>
> string s = prompt_for_input("prompt: ");
>
> When in "plain" mode we could use stdin/readline to fetch the input, in
> curses mode we could use a dialog, and in Windows we could use a dialog
> box.
>
> The question is: how do we integrate this into the interface? One option
> is a function like:
>
> void set_input_prompt_handler( SomeFunc )
>
> SomeFunc would probably look like:
>
> string funcname( char const * prompt ); // prompt may be 0
>
> Would this be useful at all? The idea is being able to write JS scripts
> which can ask for passwords and such without knowing which UI is being
> used at the time.
>
> Another option might be to write an InputHandler plugin, and simply
> provide different subclasses for specific handlers:
>
> InputHandler.DefaultHandler = new ReadlineHandler();
> str = InputHandler.prompt_for_input( "prompt: " );
>
> Any ideas?
>
> --
> ----- st...@s1...  http://s11n.net
> "Pleasure is a grace... not obedient to the commands
> of the will." -- Alan W. Watts.
>