<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>Lynn.Allan
wrote:<BR>> I'm unclear about the best name for the CrossWire executable to
use at<BR>> various points during the installation.<BR>> * The SWORD
Project?<BR>> * BibleCS?<BR>> * sword.exe?<BR><BR>DmSmith
wrote:<BR>> think that BibleCS is the internal project name and not a
name to be<BR>used outside of it's development. If that is the case, I am
inclined to<BR>not use it.<BR>> I am inclined to use sword.exe for the simple
reason that is what it is<BR>currently called.<BR>> I think that a name
presented to the user should be "The SWORD Project<BR>for Windows" as that is
what it is called on the website.<BR><BR>Troy G. wrote (back in Sep)<BR>>
Rename the install directory from 'The SWORD Project for Windows'
to<BR>'CrossWire/The SWORD Project'<BR><BR>Dm Smith wrote:<BR>> One question:
What should happen if 1.5.6 is currently installed?<BR><BR>My inclination is for
the installer to detect that 1.5.6 is installed, and have that be the default
installation folder ... in other words, to over-write if an older version is
installed. The end-user has the option to change that. Note that this applies to
both LcdBible and BibleCS so that resource sharing is facilitated (due to the
way that SWMgr::findConfig works).<BR><BR>The LcdBible installer is a
"Starter-Kit" that includes the World English Bible, but not the InstallManager.
I think that simplifies things and makes the installer "self contained" and
ready to run immediately after successful installation.<BR><BR>The
BibleCsInstaller doesn't include a Bible, and includes the InstallManager. My
impression is that an end-user is expected to use the InstallManager to actually
acquire one or more resources.<BR><BR>> * Assumes swmgr::findConfig only
looks in current directory and then<BR>> SWORD_PATH (not parent
directory)<BR><BR>DmSmith wrote:<BR>> I think we need to work on the
assumption that 1.5.8 development is<BR>finished.<BR>> If there are API
changes that would be good to make to accommodate a<BR>more flexible
co-existence of Sword products<BR>then that should be made in the next
release.<BR><BR>Ok.<BR>I've made a patch available to swmgr:findConfig that gets
away from the practice of mods.d and modules being in a subdirectory "under" the
application installation directory.<BR></FONT><A href=""><FONT
face="Times New Roman"
size=3>http://lcdbible.sf.net/misc/swmgr_findconfig_lda_060201d.patch</FONT></A><BR><BR><FONT
face="Times New Roman" size=3>Instead of:<BR>C:\Program Files\CrossWire\The
SWORD Project\mods.d<BR><BR>It would allow:<BR>C:\Program
Files\CrossWire\mods.d<BR>or<BR>C:\Program
Files\CrossWire\resources\mods.d</FONT><BR></FONT></DIV></BODY></HTML>