Thanks Doug. I didn't know about -d flag and it might have been helpful
sometimes in the past.
I knew about scompile program, but I probably didn't use it well enough
because the program I made works under Win XP but doesn't work under Windows
7 and I needed to manually compile the scripts to make them work under Win 7
also. This is why I asked if there is a more elegant way... an API.
I didn't coded the paths, but I used environment variables, however I
probably used wrong environment variables that made by chance under XP, and
don't work under Win 7, by lack of chance. :-)
--Octavian
----- Original Message -----
From: "Doug Lee" <doug.lee@xxxxxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Wednesday, August 19, 2015 11:43 AM
Subject: [jawsscripts] Re: JAWS API
I believe you're asking for a way to automate the generation of script
code. There's no API for that, but you could (as you said) generate
jss text yourself and then compile. The SCompile utility would be the
way to go for compiling under those conditions. There are two ways to
use it:
scompile myfile.jss
scompile -d myfile.jss
In the first example, all files including myfile.jss must be in the
active JAWS version's settings/enu folder, and the jsb file generated
goes there as well. This works much like the regular Script Manager,
getting default files from the shared folder as needed without you
having to put them anywhere yourself.
In the second example, myfile.jss and all files required for
compilation must be in the current folder active when you run the
command. This includes all files Included by myfile.jss, all files
included by those files, all files Included by those, etc. It also
includes the jsd files for all files Used by myfile.jss or by anything
recursively as for Includes. Finally, it also includes builtin.jsd and
default.jsd from the shared folder. (I may not have this precisely
correct by now as I haven't messed with using SCompile that way for
quite a while.)
So usually, unless you have special circumstances, you'd want to use
SCompile without the -d flag I think.
The SCompile utility for a JAWS version is in its program folder;
e.g., C:\Program Files\Freedom Scientific\JAWS\16.0\SCompile.exe.
You'll have to use a path when running it most likely, since it won't
be on the PATH.
On Wed, Aug 19, 2015 at 08:18:52AM +0300, Octavian Rasnita wrote:
Hello,
Is there an API for JAWS that allows adding scripts and functions in the
.jss file for a specified program, or in default.jss, adding hotkeys for
specified scripts, and doing other script settings that can be done
manually using the Script Manager, Keyboard Manager etc?
Or the single way is to edit the script files directly and then compile
them?
--Octavian
__________???
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
--
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
//www.freelists.org/list/jawsscripts
