On Dec 19, 2008, at 11:37 PM, Tonny Kohar wrote:
Hi,
On Sat, Dec 20, 2008 at 6:00 AM, DM Smith
wrote:
Tonny Kohar wrote:
Hi,
On Sat, Dec 20, 2008 at 2:41 AM, Tonny Kohar
wrote:
Hi,
On Fri, Dec 19, 2008 at 9:06 PM, DM Smith
wrote:
Both MacSword and JSword will set the instal
This discussion has gone a bit beyond to where I expected it to go.
Couple of things:
1) I asserted that the Windows selfextracting Zips are broken. Having
listened to Troy's explanation and checked again + thought matters
through, I would like to withdraw that assertion.
The current self extrac
DM Smith wrote:
I didn't know about the alternate languages for Windows. No one has
reported a problem yet. My hope is that Windows uses "Application
Data" regardless of language, as this folder is created by the OS.
Here in Finland it's not uncommon to see systems which have both
"C:\Prog
>> $HOME/Library/Application Support/sword
>> $APPDATA/sword
>> $ALLUSERSPROFILE/sword
>
> Please use Sword and not sword. It matters for the first one as that is what
> MacSword and BibleDesktop use on the Mac. On windows it doesn't matter, as
> windows is case insensitive, but BibleDesktop and on
Eeli Kaikkonen wrote:
> Greg Hellings wrote:
>>
>> Personally I see the joy in this, but it also strikes me as somewhat
>> anti-Windows.
>
> If this really is the case for most of the users, this whole
> conversation has been meaningless - the applications should store the
> modules in app-specif
Greg Hellings wrote:
Personally I see the joy in this, but it also strikes me as somewhat
anti-Windows. When I'm in a Unix-like environment, I expect that my
vi, vim and gvim will all read the same ~/.exrc (I think that's the
name of it), then vim and gvim will read ~/.vimrc and then gvim will
Hi,
On Sat, Dec 20, 2008 at 6:00 AM, DM Smith wrote:
> Tonny Kohar wrote:
>>
>> Hi,
>>
>> On Sat, Dec 20, 2008 at 2:41 AM, Tonny Kohar
>> wrote:
>>
>>>
>>> Hi,
>>>
>>>
>>> On Fri, Dec 19, 2008 at 9:06 PM, DM Smith wrote:
>>>
Both MacSword and JSword will set the install location to
>>
Troy A. Griffitts wrote:
OK, so would this be a fair assessment of the requests on the table?
To the C++ Engine add searching in:
$HOME/Library/Application Support/sword
$APPDATA/sword
$ALLUSERSPROFILE/sword
Change the C++ Engine to 'augment' the installed module list with any
works found on
On Fri, Dec 19, 2008 at 4:19 PM, Eeli Kaikkonen
wrote:
> 2. The end user should have the final word after the initial phase. We
> should think what happens when the user installs the first application, then
> installs some modules with that, then installs another application, installs
> modules wi
Tonny Kohar wrote:
Hi,
On Sat, Dec 20, 2008 at 2:41 AM, Tonny Kohar wrote:
Hi,
On Fri, Dec 19, 2008 at 9:06 PM, DM Smith wrote:
Both MacSword and JSword will set the install location to
~/Library/Application Support/Sword.
Just quick questions, is that Mac OSX location (~/L
Troy A. Griffitts wrote:
OK, so would this be a fair assessment of the requests on the table?
To the C++ Engine add searching in:
$HOME/Library/Application Support/sword
$APPDATA/sword
$ALLUSERSPROFILE/sword
Change the C++ Engine to 'augment' the installed module list with any
works found on
Am 19.12.2008 um 20:51 schrieb Tonny Kohar:
Hi,
On Sat, Dec 20, 2008 at 2:41 AM, Tonny Kohar
wrote:
Hi,
On Fri, Dec 19, 2008 at 9:06 PM, DM Smith
wrote:
Both MacSword and JSword will set the install location to
~/Library/Application Support/Sword.
Just quick questions, is that Mac
Troy A. Griffitts wrote:
OK, so would this be a fair assessment of the requests on the table?
To the C++ Engine add searching in:
$HOME/Library/Application Support/sword
$APPDATA/sword
$ALLUSERSPROFILE/sword
Please use Sword and not sword. It matters for the first one as that is
what MacSwor
Barry Drake wrote:
> Hi Troy
>
> Just wondering: the use of a 'pending' directory into which the new
> module is unpacked following opening of a Windows module installer .exe
> is very much BibleCS only.
It is actually quite weird and totally unexpected. Why was this chosen?
> It migh
Hi,
On Sat, Dec 20, 2008 at 2:41 AM, Tonny Kohar wrote:
> Hi,
>
>
> On Fri, Dec 19, 2008 at 9:06 PM, DM Smith wrote:
>>
>> Both MacSword and JSword will set the install location to
>> ~/Library/Application Support/Sword.
>
> Just quick questions, is that Mac OSX location (~/Library/Application
>
Hi Troy
Troy A. Griffitts wrote:
OK, so would this be a fair assessment of the requests on the table?
Just wondering: the use of a 'pending' directory into which the new
module is unpacked following opening of a Windows module installer .exe
is very much BibleCS only. It might be n
Hi Troy
Troy A. Griffitts wrote:
OK, so would this be a fair assessment of the requests on the table?
Just wondering: the use of a 'pending' directory into which the new
module is unpacked following opening of a Windows module installer .exe
is very much BibleCS only. It might be n
Hi,
On Fri, Dec 19, 2008 at 9:06 PM, DM Smith wrote:
>
> Both MacSword and JSword will set the install location to
> ~/Library/Application Support/Sword.
Just quick questions, is that Mac OSX location (~/Library/Application
Support/Sword) is mapped into env variable which is accesssible/able
to
OK, so would this be a fair assessment of the requests on the table?
To the C++ Engine add searching in:
$HOME/Library/Application Support/sword
$APPDATA/sword
$ALLUSERSPROFILE/sword
Change the C++ Engine to 'augment' the installed module list with any
works found on any path, instead of the p
On Dec 19, 2008, at 3:08 AM, Troy A. Griffitts wrote:
Just a few comments.
... snip..
One of them is probably what BibleCS does right now-- putting
modules in ./ This does not allow another application to find the
installed module set. I THOUGHT (DM can comment on this) that we
set
On Dec 19, 2008, at 2:08 AM, Greg Hellings wrote:
On Fri, Dec 19, 2008 at 12:55 AM, Matthew Talbert > wrote:
SWORD plays fine on Windows if you point SWORD_PATH to where the
modules are installed. Handling whether they are writable by the
user
is a system administration issue, and should be
On Dec 19, 2008, at 1:43 AM, Greg Hellings wrote:
On Fri, Dec 19, 2008 at 12:37 AM, Matthew Talbert > wrote:
Having spent a good part of the day trouble-shooting issues all
related to this, I can say with certainty that SWORD does not play
well on Windows at the present.
SWORD plays fine on W
On Dec 19, 2008, at 12:44 AM, Troy A. Griffitts wrote:
The appropriate response to where modules are officially found on
any OS by the SWORD engine (should also be with JSword as well) is:
Perhaps, I should have read through the full thread before
responding
http://crosswire.org
Everyone,
Please consider the situations for shared machines, such as a Windows PC
shared in a home where one of the family is a believer and another isn't.
e.g. Christian married (prior to his/her conversion) to a non-Christian.
In this case having the application modules in shared directories
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 Bi
> 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
GS can do this, if the module is unzipped. Just thinking ab
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* inst
> I am pointing out how the SWORD engine looks for it's configuration. Has
> anyone complaingin actually read the doc I pointed to?
Yes, and the code, several times today.
> of looking for configuration data allow for ANY imaginable configuration
> which has been suggested. There is no need to a
Just a few comments.
I'm not telling people to do things the WRONG way.
I am pointing out how the SWORD engine looks for it's configuration.
Has anyone complaingin actually read the doc I pointed to? This complex
method of looking for configuration data allow for ANY imaginable
configuration
> There's nothing wrong with a "." at the beginning of a file or
> variable name. It simply hides the folder from regular user view,
> which is how it should be. The data in there is not intended for
> direct user interactions. If people want to see hidden folders/files,
> they can enable it.
N
On Fri, Dec 19, 2008 at 12:55 AM, Matthew Talbert wrote:
>> SWORD plays fine on Windows if you point SWORD_PATH to where the
>> modules are installed. Handling whether they are writable by the user
>> is a system administration issue, and should be left that way. The
>> only time when a user won
On Fri, Dec 19, 2008 at 10:12 AM, Ben Morgan wrote:
> BPBible allows the user to install any of the formats (raw, windows or mac)
> by dragging onto the application or selecting them in a file picker. It
> currently has a configurable list of paths - by default this just includes
> the resources
> SWORD plays fine on Windows if you point SWORD_PATH to where the
> modules are installed. Handling whether they are writable by the user
> is a system administration issue, and should be left that way. The
> only time when a user won't have write access to the Program Files
> folder is when the
On Fri, Dec 19, 2008 at 12:37 AM, Matthew Talbert wrote:
> Having spent a good part of the day trouble-shooting issues all
> related to this, I can say with certainty that SWORD does not play
> well on Windows at the present.
SWORD plays fine on Windows if you point SWORD_PATH to where the
module
> they should be in a different place. I personally don't think modules
> should go under the AppData folder under windows. I don't think module data
> is user data at all. It is not, for example, user specific email, or
> anything like that. It is an integral part of the application and not us
Hi,
On Fri, Dec 19, 2008 at 11:39 AM, DM Smith wrote:
>
> On Dec 18, 2008, at 8:00 PM, Peter von Kaehne wrote:
>
>>> Which places do your applications expect modules in? Please list all!
>>> What are suitable places for direct install when someone wants to bypass
>>> the module install manager? A
I agree it probably isn't user data (though it is comparable with, say,
extensions under Firefox); the reason it is put there is that most users
don't have permissions in program files (especially under Vista). That's why
%PUBLIC% under Vista is probably better. Don't think Public is pre-vista,
tho
On Thu, Dec 18, 2008 at 11:44 PM, Troy A. Griffitts
wrote:
> Our engine has a number of ways which it can be configured and these all
> work on all platforms. We don't remove support for some ways of
> configuration on certain platforms-- including $HOME/.sword. If you have
> something there, th
Our engine has a number of ways which it can be configured and these all
work on all platforms. We don't remove support for some ways of
configuration on certain platforms-- including $HOME/.sword. If you
have something there, then it will do the appropriate SWORD thing (in
the case of $HOME/
On Fri, Dec 19, 2008 at 10:19 AM, Matthew Talbert wrote:
> > 2) $APPDATA\Sword (preferred location)
> > 3) $HOME\.sword (this needs to be deprecated under windows in favour of
> the above - and it needs engine support added to look for the above)
>
> GS uses this now, but would use 2) if engine su
> 2) $APPDATA\Sword (preferred location)
> 3) $HOME\.sword (this needs to be deprecated under windows in favour of the
> above - and it needs engine support added to look for the above)
GS uses this now, but would use 2) if engine support was added.
> 4) $ALLUSERSPROFILE\Sword
GS uses ALLUSERSP
BPBible allows the user to install any of the formats (raw, windows or mac)
by dragging onto the application or selecting them in a file picker. It
currently has a configurable list of paths - by default this just includes
the resources subdirectory of the BPBible installation directory. A little
m
On Dec 18, 2008, at 8:00 PM, Peter von Kaehne wrote:
Which places do your applications expect modules in? Please list all!
What are suitable places for direct install when someone wants to
bypass
the module install manager? Are there any problems with that?
Some feedback is highly appreciat
Hi,
On Fri, Dec 19, 2008 at 8:00 AM, Peter von Kaehne wrote:
> Peter von Kaehne wrote:
>> Despite my silence on the matter I am still working on the SWORD website
>>
>> One of the pages where I would appreciate some collective input is
>>
>> www.crosswire.org/sword/newpage/library?section=Instal
Peter von Kaehne wrote:
> Despite my silence on the matter I am still working on the SWORD website
>
> One of the pages where I would appreciate some collective input is
>
> www.crosswire.org/sword/newpage/library?section=Install
>
> This is the old installation page taken into my pages without
45 matches
Mail list logo
