Re: JAWS Scripts - Are they interpreted or compiled?

Matthew Horspool

Hi Mario,

Ah, yes, I see. It's been quite a while since I've done any significant tinkering under the hood. I do know that some restructuring of settings went on not so long ago but I don't know the details. You could probably work them out, though, just by having a browse through your user settings folder and, if that fails, the shared settings folder.

Is this the extent of your trouble or are there more serious issues going on? I would say it should be OK to continue this thread on list as there may be others with this problem, but if a mod feels differently I will go with that.




-----Original Message-----
From: [] On Behalf Of Mario
Sent: 28 November 2018 13:47
Subject: Re: JAWS Scripts - Are they interpreted or compiled?


in regard to #2, that's what I want to understand. I am trying to figure out how to implement the scripting method I developed for previous versions of JAWS since version 11. now with 2018 and probably above, it seems FS has changed how things are done in scripting. can someone help if I email you offlist to explain further?




-------- Original Message --------

From: Matthew Horspool [mailto:mhorspool@...]

Sent: Wed, Nov 28, 2018 3:03 AM EST


Subject: JAWS Scripts - Are they interpreted or compiled?




A few points to answer here:


    1.  To compile a script: as others have said, CTRL+S is the magic keystroke. However, you need to be in the script manager to do this! To get to the Script Manager, press JAWSKey+0. If you do this from within the application for which the script was written and a JSS file for that application is present in the user's settings directory, the correct file should be loaded automatically. Simply ALT+F4 out of the Script Manager after you receive the compiler success message.

    2.  Usually, the JSB (JAWS Script Binary) ends up in the same place as the JSS (JAWS Script Source). The same does not always apply, however, for JSD (JAWS Script Documentation), JSH (JAWS Script Header), JSM (JAWS Script Messages), JKM (JAWS Key Map), JCF (JAWS Configuration File), JDF (JAWS Dictionary File) and so on. This is because a file only ends up in the user's settings directory if it is changed from the default or otherwise put there. Usually a new JSB is created because the JSS has been modified, so both files end up in the user directory even when modifying stock scripts. However, if you are only modifying existing scripts and the documentation, keymap, etc has not required an update, the JSD file may never make it across.

    3.  Save without compile is useful if something has gone wrong in your code which is causing the compiler to throw an error and you can't figure out what. In such a case, you may wish to sleep on the problem and come back to it next day.








-----Original Message-----

From: <> On Behalf Of Isaac

Sent: 28 November 2018 07:10


Subject: Re: JAWS Scripts - Are they interpreted or compiled?




So, why would you save with out compiling?


----- Original Message -----


From: "ratshtron"



To: <<>>


Sent: Tuesday, November 27, 2018 5:44 PM


Subject: Re: JAWS Scripts - Are they interpreted or compiled?






to compile a jaws script, you must have the


script file loaded and you simply save the script


with any changes with ctrl plus s. to save


without compiling you use ctrl plus w. hope this helps.






Legend has it that on Tuesday 11/27/2018 05:21 PM, Brian Vogel said:




If anyone can point me to the instructions with


regard to compiling JAWS scripts I would


appreciate it.  I have never found the


scripting documentation that I know of to be particularly useful.--




Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763 Â




   Explanations exist; they have existed for


all time; there is always a well-known solution


to every human problem - neat, plausible, andd wrong.




         ~ H.L. Mencken, AKA The Sage of Baltimore




























Join to automatically receive all group messages.