Re: JAWS Script Exchange, script installer question?

Excellent! Thanks a million.

----- Original Message ----- From: "Jamal Mazrui" <empower@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Thursday, October 11, 2007 2:14 PM
Subject: Re: JAWS Script Exchange, script installer question?


JSX creates a file called temp.iss in the JSX program folder (c:\jsx by
default).  It then calls the Inno Setup command-line compiler with that
file as a parameter to create the installer executable.  If you load
temp.iss into an editor, you can manually change some settings, such as
AppName and AppVerName.  Then open temp.iss via Windows Explorer to load
it into the Inno Setup IDE.  Press Control+F9 to recompile the installer
executable.

Jamal
On Thu, 11 Oct 2007, Bryan Garaventa wrote:

Date: Thu, 11 Oct 2007 12:27:02 -0700
From: Bryan Garaventa <bgaraventa11@xxxxxxxxxxxxxx>
Reply-To: programmingblind@xxxxxxxxxxxxx
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: JAWS Script Exchange, script installer question?

Wow, that's impressive. It works great.

One last question though, is it possible to modify the default title of the
installer, so that it reflects the name of the product being installed?

thanks,

Bryan
----- Original Message -----
From: "Jamal Mazrui" <empower@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Wednesday, October 10, 2007 9:47 AM
Subject: Re: JAWS Script Exchange, script installer question?


> Everything in the zip archive gets unzipped into the user script folder > or
> subfolders of it.  The .NET COM callable wrapper should be separately
> added to the zip archive (by means other than JSX), since it needs to > be > in the same folder as jfw.exe. The sample custom.iss file shows how to > do
> this using the JFWDir variable that the Inno Setup script gets after
> running JSX. Unfortunately, this is complex, so you will probably need > to
> learn about Inno Setup as well, e.g., from the isetup.txt documentation
> file in the JSX folder.
>
> Jamal
> On Wed, 10 Oct 2007, Bryan Garaventa wrote:
>
>> Date: Wed, 10 Oct 2007 09:31:25 -0700
>> From: Bryan Garaventa <bgaraventa11@xxxxxxxxxxxxxx>
>> Reply-To: programmingblind@xxxxxxxxxxxxx
>> To: programmingblind@xxxxxxxxxxxxx
>> Subject: Re: JAWS Script Exchange, script installer question?
>>
>> Thanks, I'll give it a go. This is the first time I've ever used the >> app,
>> so
>> I'll have to trial and error a bit. One thing though, about creating >> the
>> zip
>> file...
>> I'll need to include my dll with RegAsm.exe within the install >> process.
>> I've
>> read the bit in the documentation about the special configuration >> using
>> an
>> ISS file, but I admit to being a novice, so much isn't very clear to >> me
>> as
>> yet.
>> Should I include the dll and RegAsm.exe within the same zip folder as >> the
>> scripts, or should there be a subfolder for this?
>> Thanks for the help,
>>
>> Bryan
>>
>>
>> ----- Original Message -----
>> From: "Jamal Mazrui" <empower@xxxxxxxxx>
>> To: <programmingblind@xxxxxxxxxxxxx>
>> Sent: Wednesday, October 10, 2007 7:31 AM
>> Subject: Re: JAWS Script Exchange, script installer question?
>>
>>
>> > Make sure you have the current JSX (May 31, 2007), and check the
>> > "Merge" section of the documentation.  There are two possible
>> > approaches
>> > to do what you want.  One is to select the Merge radio button in the
>> > JSX
>> > Installer dialog and check Guide Installation in the Packager >> > dialog. >> > Then, default.jss in the .zip archive should get merged with the >> > user's
>> > default.jss and recompiled.  In this case, the new default.jss would
>> > get
>> > appended to the end of the existing one.
>> >
>> > A second approach is to name your script file anything you like, not
>> > necessarily default.jss.  On the first line of the file, put the
>> > following text:
>> > Merge "Default.jss"
>> >
>> > Suppose your file is called def.jss. Then JSX will add the >> > following
>> > line to the bottom of the existing default.jss:
>> > use "def.jsb"
>> >
>> > Jamal
>> > On Tue, 9 Oct 2007, Bryan
>> > Garaventa wrote:
>> >
>> >> Date: Tue, 9 Oct 2007 23:13:22 -0700
>> >> From: Bryan Garaventa <bgaraventa11@xxxxxxxxxxxxxx>
>> >> Reply-To: programmingblind@xxxxxxxxxxxxx
>> >> To: programmingblind@xxxxxxxxxxxxx
>> >> Subject: JAWS Script Exchange, script installer question?
>> >>
>> >> I can see in the doc how to designate an app.exe, and reference a >> >> name
>> >> within the configNames.ini to associate the scripts being installed
>> >> during a merge, but how can you merge into Default.jsb?
>> >>
>> >> I'm building an app that needs to be globally accessible, so I'll >> >> need
>> >> to
>> >> merge the script jsb and jkm files into the default script set.
>> >> Preferably, using the Use "module.jsb" syntax to do so for >> >> simplicity.
>> >>
>> >> Is there a way to do this using the script installer?
>> >>
>> >>
>> > __________
>> > View the list's information and change your settings at
>> > http://www.freelists.org/list/programmingblind
>> >
>>
>> __________
>> View the list's information and change your settings at
>> http://www.freelists.org/list/programmingblind
>>
> __________
> View the list's information and change your settings at
> http://www.freelists.org/list/programmingblind
>

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

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


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

Other related posts: