[jawsscripts] Re: Another public beta of JAWS Script Exchange 2.0

Thanks for your feedback, Bryan, as I want to finalize this version of
JSX.  It should treat default.jss as you intend if it contains a dummy
function with a particular naming convention for this purpose, which I
recall adoptingg from Doug Lee.  If JSX finds the following line in a .jss
merge target:

Void Function _Filler()

it assumes the .jss is a container file with Use statements above that
dummy function, and nothing significant afterward.  If that does not work,
let me know.

Jamal
On Sat, 21 Feb 2009, Bryan Garaventa wrote:

> Date: Sat, 21 Feb 2009 21:35:14 -0800
> From: Bryan Garaventa <bgaraventa11@xxxxxxxxxxxxxx>
> Reply-To: jawsscripts@xxxxxxxxxxxxx
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Another public beta of JAWS Script Exchange 2.0
>
> Hi Jamal, I was finally able to try out the new version, and it's working
> much better than it used to. Excellent!
>
> Only one thing though, is there any way to make the string parser detect
> pre-existing use statements within the default.jss file as well? For
> instance, I use a lot of internal use statements for projects I develop at
> different times, and I always use the use statement to reference these
> script sets during development. Plus some of my scripts depend on the
> addition of the use statement, such as the online chat page scripts at
> http://gutterstar.net/dynamic_live_chat.php
> So the static use of specific use statements within the installer can't
> always be relied upon to keep these custom use statements as well.
>
> I'm unfamiliar with the programming language used for this purpose within
> the installer, but would it be possible to parse the string content line by
> line for default.jss, and save or copy all of the statements beginning with
> Use for inclusion within the new Default.jss output file? Please forgive my
> ignorance if this is more complicated than I understand. This really is a
> great product, and you've done a great job.
>
>  Best wishes,
>
> Bryan
>
> ----- Original Message -----
> From: "Jamal Mazrui" <empower@xxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Monday, February 16, 2009 8:23 AM
> Subject: [jawsscripts] Another public beta of JAWS Script Exchange 2.0
>
>
> > http://EmpowermentZone.com/jsxsetup.exe
> >
> > This version enhances merge support, and bundles optional script sets.
> > The JSX installer engine now recognizes an existing container.jss file
> > that it previously created, a script file containing a set of Use
> > statements followed by a dummy function to satisfy the JAWS script
> > compiler.  A merge operation incorporates the components referenced in
> > such a file.
> >
> > At the end of the installation process for the complete JSX application
> > (using the above URL), three script sets are offerred.  These options are
> > unchecked by default.  You can check one ore more of them to install their
> > zip archives with JSX.. i.e.,
> >
> > BX, the Jaws toolbox by Doug Lee (BSD license)
> >
> > HomerKit, the Homer script library and editor interface by Jamal Mazrui
> > (LGPL license)
> >
> > Visual Studio scripts by contributors from the blind programming community
> > (public domain)
> >
> > Jamal
> >
> > __________
> > Visit and contribute to The JAWS Script Repository http://jawsscripts.com
> >
> > View the list's information and change your settings at
> > http://www.freelists.org/list/jawsscripts
> >
> >
> > _______________________________________
> > No viruses found in this incoming message
> > Scanned by iolo AntiVirus 1.5.6.3
> > http://www.iolo.com
> >
>
> __________ 
> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>
> View the list's information and change your settings at
> http://www.freelists.org/list/jawsscripts
>
__________ 
Visit and contribute to The JAWS Script Repository http://jawsscripts.com

View the list's information and change your settings at 
http://www.freelists.org/list/jawsscripts

Other related posts: