[jawsscripts] JLS utilities capture discussion.
- From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Thu, 11 Oct 2012 10:52:41 +1100
ah. right. yes, I get it now.
hahahaha. sounds very cool indeed!
Thanks for the explanation of that below.
that must've been a rather complex thing to build also!
So it was a static but remote system-wide debug utility basically. K I
understand now.
Very fancy!
----- Original Message -----
From: "Jim Snowbarger" <Snowman@xxxxxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Wednesday, October 10, 2012 1:34 PM
Subject: [jawsscripts] Re: jaws14 public Beta2, enhancements in Scripting.
> Jeff,
> Oh, I guess that was pretty much all of it. A situation might be one
> where
> some script was expected to succeed on a remote client's machine, but it
> did
> not. So, I would have the user run the snapshot utility to grab all the
> good stuff. Once I brought that file into my system, Told JLS to use the
> file, instead of the hierarchy on my system, it redirected all the usual
> jaws builtins to access the file instead of the system. I was able to
> debug
> the script essentially in the user's environment. Because JLS replaced
> all
> those GetWindow what have you calls with it's own versions of them. The
> script called them, but unknowingly got the JLS versions, and thus was
> getting data from the file, pretending to be on the client's machine..
> This was long before tandem. And, of course, it can't track changes that
> the script would make, because it could not synthesize windows getting
> created that did not exist in the capture. But, it could synthesize tree
> navigation, and other expectations such as text and type and class and all
> that stuff.
> So, it gave me a way to look at a snap shot of what the user had on
> screen.
> Often, I would find that some other window was open, obscuring windows of
> interest to my script, and that my client was not aware of the windows
> presence. I had not anticipated it either.
> So, I was able to teach the script to be more robust or, shall we say,
> tolerant.
> The cool thing was that, because the data collection was done system-wide,
> I
> could use my JLS utilities, which is analogous to scripting mode, or
> whatever they call it now, to manually explore the entire system and see
> what existed at the time the snapshot was taken.
> Yep, the capture utility clearly told the user to not have any sexy stuff
> on
> screen before proceeding, but it didn't really mean it.
> Most obeyed.
>
>
> ----- Original Message -----
> From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Tuesday, October 09, 2012 8:13 AM
> Subject: [jawsscripts] Re: jaws14 public Beta2, enhancements in Scripting.
>
>
> Hi Jim/Scripters.
>
> It's probably perfectly obvious to many of us Jim, :)
> but I was just wondering,
> would you perhaps mind elaborating with some more specific detail, as to
> what types of problems, this kind of JLS development, has enabled you to
> solve?
> Like I for one would find it really interesting, to hear of a few
> realWorld
> examples as to the types of solutions this kind of development structure,
> actualy facilitates for you? And thus the client with the problem?
>
> You say:
> quote: > 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.>' (end quote.)
>
> GC, and I particularly wanted to highlight that last part as of concern to
> me too! Identifying colors in non-textual areas, has sooo much power when
> it
> can be utilized.
>
> Thanks much for any clarification.
> Geoff c.
>
> ----- Original Message -----
> From: "Jim Snowbarger" <Snowman@xxxxxxxxxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Sunday, October 07, 2012 12:55 PM
> 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:
- » [jawsscripts] JLS utilities capture discussion. - Geoff Chapman