HI Jeremy!
Yes, it is necessary. If you want to extend the functionality of the
default.jss than you have to add your extension scripts to the
MyExtensions.jss as "use" clauses.To recompile the default.jss is very
dangerous. Using MyExtensions.jss you can extend JAWS on a very safe
way. So you can look at My Extensions.jss as the "extensibility gate" of
JAWS.
My MyExtensions.jss file include more than 50 use clauses and over
25,000 lines of code. I use it mainly to extend JAWS Script
functionality and to add some new reading capabilities originally
missing from JAWS like reading romanic numbers correctly, or reading
words written in foreign languages embedded in Hungarian texts (because
I'm Hungarian) correctly without changing speech synthetizer.
Chaba
2020. 04. 01. 3:18 keltezéssel, jeremy.richards7@xxxxxxxxx írta:
Hi all,__________�
While running a Google search to answer a scripting question, I came across
the info way below. In 2020, is using the JAWS MyExtensions.jss file still
necessary? It is used as a type of pseudo Default.jss file. The
MyExtenssions.jss file is used to protect the default JAWS files. In other
words, rather than modifying the main default.jss, one puts all scripts into
the MyExtensions.jss. Immediately below is the information I found. Is this
information still relevant in the year 2020?
"On Tue, Apr 15, 2014 at 03:51:00PM +0000, Homme, James wrote:
I just noticed that in the Shared folder, there is a jss file called
MyExtensions.jss, that you can use to put use statements for scripts that
you want to run globally. This keeps you from mucking around with the
default script file and breaking something. If you copy MyExtensions.jss
into the user directory and then compile it, and then create .jss files, and
put use statements in for them, when you update JAWS, there is less of a
chance for your global changes breaking, and less of a chance for you to
make errors that would break the default script set. You could use this file
to override functions or scripts and make behavior changes that you want to
test.
Thanks.
Jim
Here is Doug Lee's reply to the previous information:
Bit of a caveat with the MyExtensions approach: Events that already exist in
the JAWS shared-folder default.jss will only reach your code if the
default.jss event passes it on. You can check this for each event of
interest by looking in default.jss for calls to the event within itself. If
you are intercepting an event that is not in default.jss already, you should
get it.
Everything below this line is what you might call fine print on how this
works:
The JAWS 15 default.jss file contains Use statements for many jsb files.
Most appear before MyExtensions, but LiveResourceLookup, QuickSet, and
Depricated.jsb are loaded after MyExtensions.jsb. When an event is called,
such as the NewTextEvent, it is first sought in files loaded for the active
application, then in default.jss, then in the files loaded by Use statements
in default.jss and in any descendants. The first file after default.jss that
may answer an event call is the last file loaded with a Use line.
So, for NewTextEvent: default.jss gets the first crack after any
app-specific scripts get a chance. If the default.jss NewTextEvent calls the
next instance down the chain, the last Use line's jsb gets a shot - in this
case, Deprecated.jsb. For simplicity we'll skip the idea of Deprecated.jsb
and others containing their own Use lines... so the next file to have a
chance at the event, if not stopped by Deprecated.jsb, is QuickSet.jsb; then
LiveResourceLookup.jsb, then MyExtensions.jsb and whatever is loaded by it,
and then the rest of default.jss' Use files."
Original source:
[jawsscripts] Re: MyExtensions.jss With JAWS 15 - jawsscripts - FreeLists
https://t.ly/zy2lw
Thanks,
JR
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts