Re: [OVC-demo-team] New version of RII

From: Eron Lloyd <elloyd_at_lancaster_dot_lib_dot_pa_dot_us>
Date: Thu Feb 12 2004 - 16:01:04 CST

Hi Jan,

Did you happen to see any of the discussion regarding the curses dependancy in
RII? We should probably decide how this is going to integrate into the UI
shell; I'd like to see it componentized and slice away the SOX and curses
dependancy, and instead use Qt's native QSound class/NAS to handle the audio,
and let the shell handle input and navigation. Shouldn't be too difficult and
I can definately help.



On Sunday 08 February 2004 4:36 pm, Jan Karrman wrote:
> I have uploaded a new version of the RII to Sourceforge now. It is
> available from the CVS Repository and from the Files release section.
> The README file is included below.
> /Jan
> Reading Impaired Interface (RII).
> The source code and the audio files can be downloaded from:
> either from the CVS Repository or from the Files section.
> Put the audio files in a subdirectory 'audio' to the directory 'rii'.
> The script is written to run under Linux (the platform chosen for the
> demo). But to make it available to a wider audience for testing, it
> has also been ported for Windows. It is tested under Windows 2000, but
> should hopefully work for other windoses as well.
> Linux:
> The script calls the program sox to play the audio files. This was
> installed by default on my RedHat 9 system. It is available from:
> If some other audio player is used, or if sox is not installed as
> /usr/bin/sox, the script must be modified to reflect this. Search for
> 'sox' in
> Windows:
> The Python Win32 Extensions must be installed:
> Put the audio player WAV.EXE in the same directory as It is
> included in the BVA application, also available from Sourceforge above.
> If some other tool is used, the code needs to modified accordingly.
> It is possible to run the application ( without the audio
> files - text will be printed that is supposed to be read out. Note that,
> along with the text, the name of the corresponding audio file is written.
> The application can be reset by pressing Ctrl-C. Terminate with two
> quick Ctrl-C.
> Text mode (no audio) is forced by calling the script with the command
> line option -t. This makes it a bit quicker to test. You can use the
> option -s to save postscript to a file, and -p to print to a
> printer. You will need to configure the printing command, defined at the
> top of the file for this. You will of course also have to install
> the postscript printing routines to be able to save or print postscript.
> There is also an option -d that gives some debugging output.
> To view postscript files, you can use ghostscript (installed by default
> on Linux) together with previewers gv (Unix/Linux) or gsview (Windows).
> Download from:
> This implementation is more structured than the first version. It has a
> number of methods that are called after each valid key-press. Which method
> that is to be called depends on which key is pressed, and what the current
> state in the voting process is. For example, if in the candidate selection
> state (the slow list), and the voter selects a candidate by pressing the
> down arrow key - then the select_down() method is called.
> Things to be done:
> * Implement the arrow key chase - you know like "no, that's the Shift
> key. The arrow keys are to the right." etc. I'm not sure if this is
> really necessary, though. Since there is a possibility that another
> voter left in the middle of the process, shouldn't a pollworker
> follow the voter to the voting booth and make sure that the app is
> its initial stage. Then he can at the same time give instructions:
> "Here are the arrow keys, use them to navigate. This is the Escape
> key, press it for help.". A person that isn't used to computer
> keyboards must probably be instructed anyway; "Press a key" does not
> mean "press and hold", etc.
> * Some instructions need rewriting. For example Printing.wav has the
> order of events wrong (insertion into the privacy folder must precede
> checking for accuracy). Also, Intro2.wav need to be reformulated.
> Cory Hamma is working with this.
> * If the wrong key is pressed, this is signaled with a beep. Maybe in
> some cases it should be by some instruction instead.
> * The ballot data is hardcoded ( It should be taken from
> ballot.xml but its structure has not yet been fixed (or?).
> * Improve the documentation.
> ---
> [This E-mail scanned for viruses by Declude Virus]

Eron Lloyd
Technology Coordinator
Lancaster County Library
Phone: 717-239-2116
Fax: 717-394-3083
[This E-mail scanned for viruses by Declude Virus]
= The content of this message, with the exception of any external 
= quotations under fair use, are released to the Public Domain    
Received on Thu Apr 1 02:40:17 2004

This archive was generated by hypermail 2.1.8 : Thu Apr 01 2004 - 02:40:36 CST