Talk:Keyboard input/Obtain a Y or N response: Difference between revisions

This task is to demonstrate operational facilities through the use of a keyboard
(This task is to demonstrate operational facilities through the use of a keyboard)
Line 7:
: This is a task that typically requires some kind of terminal. A lot of languages, but not all, work in such environments and have their standard input and output directed to such by default. There are nuances, but they're still portable in principle. As such it's worth having the task. Restrictions on applicability of solutions should be noted, of course; that's normal rules for RC. (I'd expect most solutions to work on either Unix or Windows, but not both.) –[[User:Dkf|Donal Fellows]] 18:44, 18 October 2010 (UTC)
::So we are requiring [[User input/Text|console input]] rather than [[User input/Graphical|graphical input]]? That should be clarified, shouldn't it? I know I can do this in Java for graphical input, but for console input I'm not sure. I haven't been able to find a library that does well with console manipulation like this (though I haven't had enough need to look too hard). --[[User:Mwn3d|Mwn3d]] 14:54, 28 June 2011 (UTC)
:::This task is really to demonstrate operational facilities through the use of a keyboard on computers that have a keyboard attached. A solution using only touchscreen widgets would not fulfil this task, unless these widgets also responded to keypresses from an attached keyboard (ie they operate in parallel with the keyboard). We could always create a separate task for obtaining responses through keyboardless touchscreens, if this is required in future. [[User:Markhobley|Markhobley]] 17:30, 28 June 2011 (UTC)