[ossrp-control] Re: Features So Far

Hi,

Yes.  Configuration, at least at a basic, user understandable, level, should
be there.  Things to control the output, input, etc. will tailor the
software more towards the individual needs of users.

So, it's something that should be there.

Will
----- Original Message ----- 
From: <gerald.g.weichbrodt@xxxxxx>
To: <ossrp-control@xxxxxxxxxxxxx>
Sent: Wednesday, April 27, 2005 8:25 PM
Subject: [ossrp-control] Re: Features So Far


>
> But perhaps, just perhaps, to make the task slightly simpler for the first
> pass, we could have some configurability but just permit saving a single
> set of settings as the user's preferences.  Life starts to get, uh,
> interesting when you get into the mess of sorting out what application is
> really in control at any given moment.  Witness, for instance, how JAWS
> will sometimes report the current application as some underlying DLL or
> other widget that's in control unbeknownst to the user.  Just a thought in
> the name of managing that scope creep a bit.  Honestly, I didn't *really*
> expect the BIOS stuff to be in version 1.  Just thought it was a nice
> thought as we did a little dreaming.
>
> Cheers,
> Jerry
>
>
>
>
>                       "Saqib Shaikh"
>                       <me@xxxxxxxxxxxxxxx>           To:
<ossrp-control@xxxxxxxxxxxxx>
>                       Sent by:                       cc:
>                       ossrp-control-bounce@fr        Subject:
[ossrp-control] Re: Features So Far
>                       eelists.org

>
>
>                       04/27/2005 03:02 PM
>                       Please respond to
>                       ossrp-control
>
>
>
>
>
>
> Excuse me for stating the obvious Will, but I'd like to add a few more
> things.  Since you know me, you can guess where I@m coming from <smile>
>
> * Ability to use the command line
> * Ability to set preferences relating to the screen reader
> * Ability to make these settings specific to a particular application
>
>
> I'm not sure the mouse support belongs in alpha 1 but I guess it could be
> useful to some.
>
>  Saqib
>
>
> From: ossrp-control-bounce@xxxxxxxxxxxxx
> [mailto:ossrp-control-bounce@xxxxxxxxxxxxx] On Behalf Of Will Pearson
> Sent: 27 April 2005 20:02
> To: ossrp-control@xxxxxxxxxxxxx
> Subject: [ossrp-control] Features So Far
>
> Hi,
>
> Here's my understanding of the important features that should be
> investigated for version 1.  It doesn't feature everything, but then
> there'll be versions after 1 in which more things can be brought in.
>
> Functional requirements:
> * ability to read *windows* login screen
> * ability to work with widely used types of applications, e.g. word
> processors, spreadsheets
> * support for TTS engines that use the SAPI interface, as some of these
> provide clearer speech than current formant synthesisers
> * ability to use mouse or equivalent functionality
> * must work with User Interface Automation
> * ability to update components over the web
> * support for Braille devices
>
> Architectural requirements:
> * based on .Net Framework/WinFX
> * component based architecture
>
> * Research requirements
> * investigate mechanisms to provide more efficient interaction mechanics
> * investigate techniques to convey all the semantic information contained
> within a GUI through auditory and tactual/haptech transmission media.
> * investigate means for clearer speech
> * investigate perceptual psychology techniques for semantic conversion of
> web based graphical turing tests to text
>
> Project management requirements:
> * risk analysis
> * avoid scope creep
> * requirements management
> * beta 1 to be made publically available April 2006
>
> These are fairly high level requirements, and if anyone feels anything is
> being missed or would like to include anything, then say now.
>
> Will
>
>
>
>
> To post to the list, send a message to:
> ossrp-control@xxxxxxxxxxxxx
> To unsubscribe, send a message to:
> ossrp-control-request@xxxxxxxxxxxxx
> and set the subject field of the message to "unsubscribe" (without the
quotes
>
>


To post to the list, send a message to:
ossrp-control@xxxxxxxxxxxxx
To unsubscribe, send a message to:
ossrp-control-request@xxxxxxxxxxxxx
and set the subject field of the message to "unsubscribe" (without the quotes

Other related posts: