Your message may have been cut short for some reason... I think the .ini stuff is built into the NSIS DLLs; I don't recall manipulating them myself in that installer, though I definitely could be forgetting something. I'm pretty sure the Nullsoft function reference lists some functions for ini file access though. On Sat, Jan 10, 2015 at 05:20:48PM -0500, Jonathan C Cohn wrote: Doug, Thanks for the encouragement, I had started looking at the source directory of the BX installer last week. I did not yet find how you manipulate INI files, which is my first concern at this moment. I know that JAWS and VBS can do this, but it appeared that the VBS code I found in the BX installer was only to merge use statements into the default.jss files a much more complex routine set than INI files , but as a long time perl programmer, > On Jan 10, 2015, at 13:47, Doug Lee <doug.lee@xxxxxxxxxxxxxxxx> wrote: > > Belated reply as I've been remiss at monitoring this list for a while: > > Ideas and code can be gleaned from BX by unpacking the BX installer > with 7Zip or a compatible program and looking in the src/installer > folder. > > I don't register DLLs or handle binary/non-binary choices in my > installers though. > > On Mon, Dec 29, 2014 at 02:39:20PM -0600, Jim Snowbarger wrote: > 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 > > -- > Doug Lee, Senior Accessibility Programmer > SSB BART Group - Accessibility-on-Demand > mailto:doug.lee@xxxxxxxxxxxxxxxx http://www.ssbbartgroup.com > "While they were saying among themselves it cannot be done, > it was done." --Helen Keller > __________??? > > 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 -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:doug.lee@xxxxxxxxxxxxxxxx http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts