[jawsscripts] Re: jaws14 public Beta2, enhancements in Scripting.

  • From: "Jim Snowbarger" <Snowman@xxxxxxxxxxxxxxxx>
  • To: <jawsscripts@xxxxxxxxxxxxx>
  • Date: Tue, 9 Oct 2012 22:02:23 -0500

I think, what you have is the text, the location at which it was found, it's 
attributes and colors.
But, you don't know what kind of window it resided in, or control it was 
associated with unless you go look.
You can do all that with existing technology, except for the OCR portion.
I don't know about you guys, but I have not had much luck with inconvenient 
OCr.  Usually, it makes lots of mistakes, or misses text altogether.

But, assuming the best about that, one wonders whether you could turn it 
loose on your favorite bit mapped wizzy application, and go drink a cup of 
coffee.  Then, when you came back, you might be able to use the OCR rendered 
text to perform a single mouse click, at which point you would repeat the 
process until desired results were achieved, or coffee overload, whichever 
came first.
Well, Ok, maybe that might interfere with the creative process.

Seriously though, how about an enhancement to something like the toolTip 
scanner in HotSpotClicker, which builds a list of fired toolTips, as a 
result of a painfully slow mouse scan, and the locations  at which they were 
detected.
This guy would use the .xml as a database of OCR-rendered text chunks, what 
they said, and where they were.  And, you could take the jaws cursor to each 
of them in turn, click there, and decide if anything useful happened.  If it 
did, then it might be a place you would want to save, assign a name to, and 
use in the proper context.   It would help something like HSC deal with 
totally graphical apps that do not support toolTips.






----- Original Message ----- 
From: "Bissett, Tom" <tom.bissett@xxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Tuesday, October 09, 2012 8:57 AM
Subject: [jawsscripts] Re: jaws14 public Beta2, enhancements in Scripting.


Hi,  I am thinking that this can be used for finding text and trigger points 
on the screen.  My guess this is what they use for the convenient OCR and 
now they have made it available to us.  We just need to figure out how to 
parse it and implement what we want to achieve with it.
Could the string returned be used to display its content in the results 
viewer and from there we could activate buttons etc?
I haven't taken the time to play with it so I am just throwing some thoughts 
out there.
Tom Bisset
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx 
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Stefan Moisei
Sent: October 7, 2012 4:02 AM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: jaws14 public Beta2, enhancements in Scripting.

I don't know fs's intended use for this function, but I know how I might use 
it.
The screen xml output includes OCR text, if existent. It is marked as OCR in 
the xml. One can copy it, I guess one can also trigger OCR on a specific 
event and get the new text with this.
-----Original Message-----
From: Jim Snowbarger
Sent: Sunday, October 07, 2012 4:55 AM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: jaws14 public Beta2, enhancements in Scripting.

Very interesting.  The next thing will be how to make use of this .xml 
information.
Basically, this is our equivalent of print screen.
If I understand, from this, you can get all text, including text color and 
attributes.  You don't get graphics, and don't know anything about window 
boundaries.

What is actually the intended purpose of this?  Anybody know?

One idea that comes to mind is that, if a client wanted to pass you a screen 
shot, they could capture this .xml information, and send it to you.  You, as 
a script developer, have some clever tool that decodes the XML jibberish, 
and renders it in some familiar form, a web page, or a virtual viewer, or 
something like that.
Does something already exist?  Or, do I feel a utility coming on.
Sounds like a nice addition to my JLS_utilities, and/or Doug's BX.

JLS actually has a means of collecting the window structure from a  client's 
machine, including window attributes, such as boundary coordinates, style, 
type, class etc, and even the text in each window, done of course only under 
the control of the client.  But, they basically create a big data file that 
they send to me.  I put JLS in a special mode where all the window 
navigation functions, GetFocus, GetPriorWindow, GetNextWindow etc, all 
consult the data file, rather than my own system.
The missing piece was color and attributes for the text.
This would supplement that.

Of course, we still don't have pixel colors in non-textual areas.  But, I'm 
getting the disturbing impression that precious information like that may be 
becoming harder to obtain.  ,sigh>

Anyway, back to the original.  Does anybody know the intended means of 
interfacing with the XML data?







----- Original Message -----
From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Friday, October 05, 2012 2:57 AM
Subject: [jawsscripts] jaws14 public Beta2, enhancements in Scripting.


JAWS 14 includes a new scripting function for obtaining screen content in
XML format. For more information on using this new function, refer to the
JAWS 14 includes a new scripting function for obtaining screen content in
XML format. for further information see:
http://www.freedomscientific.com/documentation/scripts/scripting-info.asp

Short URL:

http://bit.ly/RFtrUd
Geoff C.

__________�

View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts



__________�

View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts

__________�

View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts

__________�

View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts



__________�

View the list's information and change your settings at 
http://www.freelists.org/list/jawsscripts

Other related posts:

  1. Home
  2. jawsscripts
  3. Archive
  4. 10-2012