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 could be a [further] potential cause of friction. Better that the believer in the household restricts modules and the application shortcuts to their %userprofile%. We should follow Windows best practice for the installation location methodology. --David Chris Morgan-10 wrote: > > On Fri, Dec 19, 2008 at 10:12 AM, Ben Morgan <benpmor...@gmail.com> 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 subdirectory of the BPBible installation directory. >> > > To fill out about BPBible's current default module directories, the > Windows > installer searches for BibleCS and puts it into the list; this way it's > more > compatible with it :-) > > To see the code as it currently is, look > here<http://code.google.com/p/bpbible/source/browse/trunk/installer/bpbible.iss.template?r=424#65>at > lines 65-81. First, it looks in the registry at > HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App > Paths\sword.exe. This is put there by BibleCS when it runs. If it finds > it, then that is one of its paths. > Also, it adds {app}\resources as a path, where {app} is the install path > specified by the user; by default then then this'll usually be C:\Program > Files\BPBible\resources. > > End result: the default resource paths for BPBible give no writeable paths > to Vista. Uh oh. Especially because of this, I think that > $ALLUSERSPROFILE\Sword and/or $PUBLIC\Sword sounds a good idea. Another > opinion from me: Why would $APPDATA be preferred over $ALLUSERPROFILE? > Normally I would expect all users to want to have about the same set of > modules; however, when I think about it, I'm also not sure whether users > would want other users to be able to delete their modules... not that any > of > this really matters much to me - all I really do for BPBible is the > installer (switching to a decent NSIS based one soon) and BPBible Portable > :-) > Also, in my experience, $SWORD_PATH is not normally set, whereas > HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App > Paths\sword.exe is. Draw out from that what you will ;-) > > > God bless, > > Chris Morgan <chris.morgani...@gmail.com> > > > I don't need a quote in my signature. > > _______________________________________________ > 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 > -- View this message in context: http://www.nabble.com/New-website---installation-instructions-tp21083038p21091638.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ 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
