[jawsscripts] Re: JSX Questions
- From: Jamal Mazrui <empower@xxxxxxxxx>
- To: jawsscripts@xxxxxxxxxxxxx
- Date: Tue, 15 Sep 2009 12:07:34 -0400 (EDT)
Getting back to you belatedly, Don.
I'll reflect further but cannot think of an easy code change to address
the commented line problem in a .jcf file. I am using standard ini file
routines of the WinBatch language to read all keys of each section, and
apparently, these routines skip commented lines, considering them not to
be valid keys (which is true in the conventions of ini format).
Regarding merging .jgf files, I just looked at one and it appears to be
in ini format, which means I could use the same merging algorithm as for
.jcf and .jkm files. Can you or others confirm that a .jgf file does
follow ini format?
Jamal
On Fri, 28 Aug 2009, Donald Marang wrote:
> Date: Fri, 28 Aug 2009 17:55:04 -0400
> From: Donald Marang <donald.marang@xxxxxxxxx>
> Reply-To: jawsscripts@xxxxxxxxxxxxx
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] JSX Questions
>
> Hi Jamal and others,
> I have been using jsx to package scripts for VMware Player and Workstation.
> As you might have noticed, Chris Hallsworth started these scripts and I have
> been working with him to add a little and am package them. The Player
> scripts are a no brainer to package with jsx. Jsx does a good job of
> packaging the Workstation as well. In fact, I have packaged them together.
> JAWS comes with a "vmware.jss" script file, so I placed our scripts in
> "VMwareWorkstation.jss" file and let jsx merge them together. I am using the
> statement at the top of the script file to instruct jsx how to merge.
>
> I have two additional things I would like the merge to handle, but I do not
> know if it is possible.
>
>
> 1. I like to add debug messages throughout certain code in the format:
> SayMessage (OT_DEBUG, "Menu Event: new mode = " + IntToString (iMode) + ",
> handle = " + IntToString (hMenu))
>
>
>
> To enable this to speak I add the following line to the JCF file:
>
> [OutputModes]
> DEBUG=1|1|1|DEBUG Message
>
>
> Before I package the scripts I place a semicolon in front of the second line
> so that these statements will be silent. When this file gets merged, even if
> there was not previously a JCF file present, the section name and a dummy
> line gets placed in the "vmware.jcf" file as follows: .
>
> [OutputModes]
> (NONE)
>
> The problem is that it can be handy if a user has a problem, to tell them in
> an email to remove the semicolon and listen for certain information at the
> spot where they have problems or just the last thing it said before going
> south. I currently get around this by simply adding a "vmware.jcf" file to
> the package with these commented lines already added . The only problem with
> this solution is that this would overwrite any JCF file there before
> installation. Would it be possible to have the merge process add these
> comment lines to the result file? Perhaps only specially marked comment
> lines like a double semicolon (;; ) would be copied to the result file. ?
>
>
>
> 2. I was able to use the auto graphics labeler on this application to make
> sense of some of the dialogs. I may need to label more manually. I would
> like to add this information in the package in the file,
> "VMwareWorksttation.jgf" file, and have it merged with any graphics that the
> user labeled in the "vmware.jgf" file. However, jsx does not merge these
> files for me. Is it possible to get jsx to do this?
>
>
>
> Don Marang
>
>
> __________
> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
__________
Visit and contribute to The JAWS Script Repository http://jawsscripts.com
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
Other related posts:
