[jawsscripts] Re: Scripts Installers
- From: "Jim Snowbarger" <snowman@xxxxxxxxxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Mon, 29 Dec 2014 14:39:20 -0600
Yep, that is the problem I am running into. There seems to be a need to dig
pretty deep into other obscure mechanisms in order to simply package a set of
jaws scritps. I certainly do feel a need for a simpler approach.
I think one might want to go back as far as XP. I hear from people all the
time who are sticking with it for as long as they can get bye with it. All
later Windows versions seem to present us with UI quirks that folks would
rather not hassle with if they had a choice.
And, it would be good if such an installer gave you the option to include
binaries, and to only recompile the jss files that are provided.
One last thing is the ability to register a DLL.
Since I speak English, my opinion would be that english only would suffice for
now.
I have some questions about localization, coming under separate thread.
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Sean Farrow
Sent: Monday, December 29, 2014 2:36 AM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Scripts Installers
Hi,
The other alternative is WiX from:
Http://www.wixtoolset.org/
This is an xml-based msi (Windows installer) creation tool.
The problems with the nsis installers currently are that it doesn't support
compiling scripts on the fly, finds two many directories as I recall and
doesn't support additional languages.
I looked in to the effort required in creating something with WiX a while back,
we would need to create some form of packager as this does get pretty involved,
essentially copying xml fragments for each jaws version.
If I were to reserect this effort in the new year, what would be the minimum
operating system people would want? Also would people want multiple languages,
or would just English suffice for now? Would people be interested in this being
an open-source project on say GitHub? Also would a web-based packaging service
be appropriate or would people want to package locally?
Thoughts appreciated.
Kind regards
Sean.
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Scott Huey
Sent: 29 December 2014 03:17
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Scripts Installers
I dunno, NSIS may be the best choice there is. It's comparable all the way back
to windows xp, is open source, and supports a form of modular component plugin
functionality which could (theoretically) enable code for finding required JAWS
versioning details. It's also a package installer, and can support custom front
end design to produce something clean up front. Maybe the biggest boon would be
to just design a packagER (emphasis on the E-R there) for use with NSIS to wrap
the arbitrary JAWS script sets into the installer to make it easy to do.
> On Dec 28, 2014, at 8:59 PM, Jim Snowbarger <Snowman@xxxxxxxxxxxxxxxx> wrote:
>
> Hi guys, Hope your having a nice holiday.
> So, where do we stand on general purpose jaws script installers these days?
> I have the idea that JSX is out of date, and that it will not be
> further maintained.
> I have NSIS, but it is pretty complicated, and probably more than one
> would need.
> Is there one that will handle all the myriad OS's and jaws versions?
> Any recommendations?
>
>
>
> __________
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
__________
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
__________
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
__________�
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
Other related posts:
