Yes: I have a VBS utility for simplifying the management of what I call script
chains:
http://www.dlee.org/JAWSUtil.vbs
I run it from installers to manage things like this:
cscript //nologo %cd%\JAWSUtil.vbs 17.0 chain excel add myscript.jsb
Run without arguments after JAWSUtil.vbs for basic help. For command-specific
help, just include the command
after JAWSUtil.vbs, such as
cscript //nologo %cd%\JAWSUtil.vbs chain
You have to do these interactive ones from a command prompt, or you won't see
the output.
The "dict" command is not yet implemented.
%cd% can of course be an actual path, but from a .bat file %cd% may just work
as is.
JAWSUtil is, like most of my public JAWS-related offerings, covered by the BSD
license, which is now included at
the top of the file. My apologies for it being written in VBScript instead of
something compilable; I wrote
this one starting in 2009.
On Wed, May 11, 2016 at 05:51:29PM -0400, Chad Foster wrote:
This is very helpful -- thanks much Doug. I've previously been using
batch files to set up my bolt-on script code to default shipping script
code, and it looks like that is also broken. I have since added a few
lines to MyExtensions.jss file which seems to call the code in the
right order, but I'm finding some unknown function calls, leading me to
think I'm firing the JSB files too much. Any tips for bolting add-on
script code to FS script code e.g., MS Excel?
On Wed, May 11, 2016 at 5:04 PM, Doug Lee
<[1]doug.lee@xxxxxxxxxxxxxxxx> wrote:
User scripts don't move; they still go in settings/<lng>. All the
rest of this, up to the Translation heading,
applies just to JAWS shared files.
Configs (jcf) and similar still go in settings\enu.
jss, jsh, jsm, qs, and qsm files go in a new Scripts folder, located
under JAWS\<version> alongside Settings.
jbs, jsd, and jkm files go under Scripts\<lng>.
Translation:
WARNING: My understanding of what follows, which constitutes the
rest of this message, is subject to error and
correction.
If you compile scripts with JAWS 16 or older, or with compatibility
mode in effect under JAWS 17, they pretty
much work as before.
If you compile using default settings under JAWS 17, some new rules
apply:
Any constant defined by any means in a jsm file whose value, not
name, matches something already translated
for shared JAWS scripts, will be translated automatically at run
time. This means that if you include an
English jsm with, say, a message called msgMyMessage whose value
happens to be "Yes," and the user runs your
scripts in French, and JAWS has a translation for "Yes" into French,
a sayString(msgMyMessage) will probably
say "Oui." If, on the other hand, you send out a French jsm file
where msgMyMessage's value is "Oui," it will
not translate because it is not going to match an English value in
the JAWS message catalog.
The same treatment applies to messages defined with the Messages
directive, regardless of whether the
definition occurs in a jsm file or not.
What I don't fully understand about translation:
If you compile scripts in compatibility mode, with an French jsm,
and then run them on a French JAWS
installation, I believe most things will work as expected. However,
I believe this arrangement may adversely
impact some messages routinely spoken by JAWS shared scripts while
this app is active. I don't have specifics
on this at this time.
On Wed, May 11, 2016 at 04:02:50PM -0400, Chad Foster wrote:
Does anyone have a quick synopsis of the script location changes to
JAWS
17? I've been Under water for the last several months and am just now
getting
around to migrating my script code over to JAWS17, and I'm noticing
there
is a significant amount of change. Any quick tips are appreciated.
Thank you,
Chad
__________???
View the list's information and change your settings at
[2]http://www.freelists.org/list/jawsscripts
--
Doug Lee, Senior Accessibility Programmer
SSB BART Group - Accessibility-on-Demand
mailto:[3]Doug.Lee@xxxxxxxxxxxxxxxx [4]http://www.ssbbartgroup.com
"While they were saying among themselves it cannot be done,
it was done." --Helen Keller
__________?
View the list's information and change your settings at
[5]http://www.freelists.org/list/jawsscripts
--
Chad Foster
Access Technology Solutions
Leveling The Playing Field Through Technology
[6]http://www.GO-ATS.net
References
1. mailto:doug.lee@xxxxxxxxxxxxxxxx
2. http://www.freelists.org/list/jawsscripts
3. mailto:Doug.Lee@xxxxxxxxxxxxxxxx
4. http://www.ssbbartgroup.com/
5. http://www.freelists.org/list/jawsscripts
6. http://www.GO-ATS.net/
--
Doug Lee, Senior Accessibility Programmer
SSB BART Group - Accessibility-on-Demand
mailto:Doug.Lee@xxxxxxxxxxxxxxxx http://www.ssbbartgroup.com
"While they were saying among themselves it cannot be done,
it was done." --Helen Keller
__________???
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts