[nvda] Re: What would it take for a graphics dictionary

Thanks for the response. It seems a bit of a crude technique and potentially bulky, but may be I am forgetting how many situations graphics aren't the only way, and icon graphics aren't that large really (I think when graphics are mentioned I think of files containing a photo which is much larger).
On reflection may be a graphics dictionary isn't very important (and anyway it probably will require extra features in NVDA). Its just I keep being reminded of it as both my linux system or when I am using window-eyes I get this extra information about emails. Outlook express is probably only one of a few cases when a graphics dictionary would be useful, just a shame its such an obvious thing though. 

From
Michael Whapples
----- Original Message ----- From: "James Teh" <jamie@xxxxxxxxxxx> 
To: <nvda@xxxxxxxxxxxxx>
Sent: Tuesday, March 27, 2007 11:32 PM
Subject: [nvda] Re: What would it take for a graphics dictionary



Hi Michael,
A graphics dictionary in other screen readers is indeed just that - a list of graphics and text descriptions. Tne general idea is that graphics are assigned a number which can hopefully be guaranteed to be the same across instances of the application or different systems (if the colour settings are the same). Any screen reader tries not to rely on graphics except where there is no other decently reliable/fast way, so there's no reason it should swamp your hdd.
A graphics dictionary or even the ability to read graphics is totally out of the question for NVDA at present, as we have no video intercept or display hooks, which is required for obtaining such information. There has been a lot of discussion on display hooking and the like; see the archives for more info. 

Jamie

Michael Whapples wrote:

Hello,
There was a question about nvda and outlook express and the status of messages, and the answer someone suggested is that it is done with graphics. This leads me to the question, if it is graphics, are the other screen readers doing it through graphic dictionaries, and what would this take to be implemented in nvda? How do they identify different graphics? Surely not just with a list of graphics and an associated text description, or is it really that basic (and if so how do you stop it swamping your HD?) So how valuable would a graphics dictionary be, and how many uses would it have? Considering that is it something that needs further consideration at the moment, or can it wait? I know there are certainly other areas which will improve the usability of NVDA, I would just like to get an idea of what will yield the best results for the time spent on it, so an idea of the priorities and where a graphics dictionary is in the list. 
 From
Michael Whapples


--
James Teh
Email: jamie@xxxxxxxxxxx
WWW: http://www.jantrid.net/
MSN Messenger: jamie@xxxxxxxxxxx
Jabber: jteh@xxxxxxxxxx
Yahoo: jcs_teh
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To unsubscribe from the list send a blank message to:
nvda-request@xxxxxxxxxxxxx
with 'unsubscribe' in the Subject field.
Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: 
http://www.nvaccess.org/nvda/
Message Archive:
http://www.freelists.org/archives/nvda



To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To unsubscribe from the list send a blank message to:
nvda-request@xxxxxxxxxxxxx
with 'unsubscribe' in the Subject field.
Thank you for your continued support of Nonvisual Desktop Access, an open 
source free screen reader for Microsoft Windows:
http://www.nvaccess.org/nvda/
Message Archive:
http://www.freelists.org/archives/nvda

Other related posts: