[sword-devel] The SWORD Project for Windows 1.5.9 installers testing
dmsmith555 at yahoo.com
Fri Oct 6 06:27:20 MST 2006
> Some observations (none major ... good work):
> * nit ... Crosswire license mentions copyright 1994-2005 ... should
> this be 2006? (the Help About for sword.exe itself has 2006)
> * SWORD_PATH environment variable over-written ... should permission
> be asked to do this if one already exists (makes installer more
I bet right now the only ones who know anything about SWORD_PATH are
developers. If this is not the case, then I can see changing the
behavior in the next release.
> * Running of InstallManager during installation is kind of unexpected
> ... the checkbox is to run Sword
Actually the current behavior of 1.5.6 is to run the InstallManager but
not follow it with biblecs. I improved it slightly by having it call
biblecs after installmanager.
I think it is more confusing to just run biblecs without running the
The text for the option is provided and internationalized by NSIS. If I
were to overwrite it, it would not be internationalized.
The behavior I would like to see is that biblecs notices whether it has
any Bibles installed and offer to run InstallManager or just run it. I
would suggest the timing of it be after the screen is drawn. That way
the user can see that they are in the application and then they know
that they are running a service of biblecs. One of the problems with
this approach is that biblecs does not see new Bibles added by
InstallManager until a restart of biblecs.
This would be something to take up for the next release.
> * InstallManager Help should have "About" menu-item with version
> * Don't care for the initial layout (but maybe this is the way it has
> always been?)
> - Actual Bible content is the smallest window.
> - Emphasis on Strongs number ... new user may find lower right
> window to be unclear ... bunch of numbers
> * Large files (ideally) ought to be shared rather than in
> Crosswire\The SWORD Project
> ... icudt36.dll=8.5mb, InstallManager.exe=3.80mb
locales.d/ would be another
We have made steps in that direction with the addition of looking in
../library and using ./sword.conf for the location of shared modules.
The problem with ../library is that it did not work 100%. However,
./sword.conf does work well. More work can be done here, but not in time
for a release.
I know we have been very long in preparing a release and probably could
have solved it by now :)
> * During uninstall with remove modules ... files removed, but
> directory paths left ...
> - didn't use InstallManager?
It uses InstallManager. That's what popped up the dialog.
> - Left userprefs.conf
The uninstaller leaves files the installer did not install. This is a
typical behavior of many installers.
> * nit ... Could installer remember the InstallerLanguage (or is this
> nsis limitation)
This is a good idea. For the next release.
> * sword.exe Help About ... typo? Thanx??? to God for His GREAT MERCY
> and LOVE
> - not an installer issue
> Registry cleanup: seems complete
> ----- Original Message -----
> From: "Troy A. Griffitts" <scribe at crosswire.org>
> To: <sword-devel at crosswire.org>
> Sent: Saturday, September 23, 2006 3:06 PM
> Subject: [sword-devel] The SWORD Project for Windows 1.5.9 installers
>> DM Smith has packaged up our latest binaries into installation
>> It would be great if we could get some reports on the installation
>> process before we release to the general public.
>> Software Only
>> Starter Pack (Software + KJV, Strongs, Robinsons, Personal
>> sword-devel mailing list: sword-devel at crosswire.org
>> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel