The Windows install for modules looks for where BibleCS is installed and
unzips the module there.
BibleDesktop supports this (as I think other frontends would support
this if our installer sets SWORD_HOME).
I don't want to confuse the majority of our current Windows users which
either use BibleCS or BibleDesktop. The instructions should say to use
the built-in app installer, or otherwise download the Windows package
and install it.
-Troy.
Peter von Kaehne wrote:
Ouch, what a can of worms I opened here with a question I thought being
totally uncontentious. :-)
Can I summarise the discussion for the purposes of my webpage:
1) Users should not install modules themselves
2) Users should not install modules themselves
..
10) Users _really_ should *not* install modules themselves
11) If they must, despite the clear warning, there are certain places,
the engine will look for and some are better than others.
And after that confusion reigns at least for me.
My preference would be to give a single place which is always the same -
at least for any particular incarnation of Windows. And while I think
all of you agree on that, it appears this is not exactly the case in
terms of our applications.
Which programmes can install modules from within their module installer
from a local location , say My Documents? If all can do so then I will
not give _any_ explanation where to unzip. It is just not worth it, I
think.
Peter
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
