I did not know about it either myself and I have been a minor script writer for quite a while as well. I haven't figured it all out as of yet but I have this failing where I don't like to lose. David Ferrin Always be yourself because the people that matter don't mind, and the ones that mind don't matter. ----- Original Message ----- From: "Paul Magill" <[email protected]> To: <[email protected]> Sent: Friday, April 27, 2012 9:13 AM Subject: Re: [JAWS-Users] information about adding to default script files
Hi David, Thank you, thank you for this info... I have been scripting for a long time, but did not know this facility had been introduced. Warm regards, Paul from Australia ----- Original Message ----- From: "David Ferrin" <[email protected]> I found this file under explore shared settings, the path is as follows: C:\Documents and Settings\All Users\Application Data\Freedom Scientific\JAWS\13.0\Settings\enu David Ferrin Many people think they are generous because they give out free advice. ----- Original Message ----- From: Eric Damery To: David Ferrin ([email protected]) Sent: Friday, April 27, 2012 6:02 AM Subject: Here is the information I promised about adding to default script files Hi David, In the event you are just adding to your defaults rather than modifying our scripts, this could be helpful avoiding problems in the future. Regards, Eric Safely Adding Default Scripts Starting with JAWS 12, the default script file makes use of MyExtensions.jsb. MyExtensions.jss includes standard headers, but contains only a couple of stub functions for source code. The purpose of the MyExtensions scripts is to include in the JAWS distribution a script source file that will never contain any Freedom Scientific source code, thus allowing the end user to safely add new custom scripts without the need to make any changes due to a JAWS update. For this reason, new scripts and functions added to MyExtensions and placed in the user settings folder is a safe way to add custom scripts to JAWS. You should be aware, however, that MyExtensions should not be used to overwrite existing scripts or functions. Default scripts and functions do not call down to MyExtensions, so any scripts or functions in MyExtensions that have the same name as those in default or application scripts will never run. Scripts or functions with unique names will run, which is why you can use MyExtensions for added scripts and functions. Because JAWS key map (JKM) files are layered, you can also assign key mappings to your added MyExtensions scripts in default.jkm in your user settings. You can use Keyboard Manager to locate your scripts in MyExtensions by looking under Default scripts and assign keys to your custom scripts. By adding your custom scripts to MyExtensions, and assigning keys in default, you can safely extend JAWS scripts to include your own custom scripts. If you have developed a library of custom functions in a JSB file, you can add it to MyExtensions through the Use statement and it will now be available to you. Just remember to use unique names for scripts or functions added through MyExtensions, and save your modified MyExtensions source and compiled files to your user settings, and you should be able to enjoy your own custom scripts added to JAWS without having to make changes due to JAWS updates. You can also copy your MyExtensions files to new versions of JAWS. Depending on the extent of your script coding, you may want to ensure that your scripts are up-to-date with the latest script innovations, but you won't need to modify your scripts simply because JAWS updated. For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/ For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/ For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/
