Re: JAWS Scripts - Are they interpreted or compiled?
Yes. Usually it is a match on the program executable. In some cases they used to match on DLLs, e.g. Internet Explorer settings were under browseui rather than iexplore. I'm not sure why this is or how to achieve it in custom scripts.
In JAWS 5.0 they introduced a file called ConfigNames.ini. This maps executable names to more human readable config basenames, which is why Internet Explorer is now under Internet Explorer. A later addition to that file allowed JAWS to load different configs based on the version of the file it found. This is how, I suspect, JAWS knows to load Word Classic vs Word 365 even though the EXE in both cases is winword.exe.
Hope this helps,
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Brian Vogel
Sent: 28 November 2018 15:14
Subject: Re: JAWS Scripts - Are they interpreted or compiled?
On Wed, Nov 28, 2018 at 09:00 AM, JM Casey wrote:
Even with my limited knowledge I do know that your statement about a script loading when a program starts up is correct. I had always wondered what the mechanism was for JAWS to be able to associate a script with a program, and based on
what I saw yesterday your statement regarding a match between the JSS file prefix and the EXE file prefix makes perfect sense. I'm sure someone else can verify.
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, and wrong.
~ H.L. Mencken, AKA The Sage of Baltimore