BPBible Portable 0.3.1 Development Test 1

1. Oh... I thought that we could for Development Tests as well. Ah well, I'd better go on the safe side. Development Test 2 is on the way and removes the logo (done), as well as removing debug prompts that I missed during publish (done, and hopefully the sort of mistake you only make once!), automatically detecting and adding The SWORD Project Portable's module paths (done) and detecting if the SWORD Project is installed on the local machine, and using its modules too (in progress).
2. I don't understand what you mean. BPBible Portable is a complete package; BPBible is included in it. The only thing needed for use (other than the Gospel Harmony viewer, which includes two harmonies) is SWORD modules. Go to The Crosswire module repositry to download them, use the SWORD Projet's Install manager, or wait for my brother Ben to finish the BPBible Module Manager... hopefully you won't need to wait too long!

 
P.S. - I see 42 downloads on the downloads page - has anyone else got any comments/questions?
Edit: I've finished DT2, but need to go... I might upload it tomorrow.

I'll check it with SWORD Project Portable. In all honesty, I haven't actually tested it properly - I just did the theory. All three of the machines I've been using have The SWORD Project for Windows installed with lots of modules, and that's now automatically added (it finds it in the registry and adds it as of Development Test 2). What's the directory structure like in \PortableApps\SWORDProjectPortable\Data\settings?

As for the custom theme, what theme is it? I use it under Windows 2000 and XP, and Ben (the main developer) uses Royale Noir when he's logged in on the XP machine. If it's not looking proper, could you please post a screenshot? Then we can try to work out whether it's BPBible, wxWidgets, or Windows that's causing the problem.

• In App\AppInfo:
  • In appinfo.ini, the home page should be PortableApps.com\BPBiblePortable, or \DevelopmentTest.
    Changed to PortableApps.com\BPBiblePortable ... I just reckoned that as that didn't exist, and as it was a semi-official BPBible package, I'd do it there.
  • In the appinfo.ini most other developers don't put there name in their unless you worked on the base app because you are PortableApps.com, but I see nothing wrong with it.
    Changed to Publisher=PortableApps.com & Contributors
  • In the appinfo.ini, the display version should be 0.2, and I don't think putting the dev test number is necessary right now, but as long as you remember to change it between releases, it's fine.
  • Your appicon.ico should have 16, 32, and 48 pixel sizes in both XP and 256 color format. You can use IcoFX if you're no good with modifying icons.
    Did I/you miss something? I checked (with IcoFX, my standard icon editing package) and it is in [48,32,16]x[XP,256] format.
• In Other\Source
  • In Readme.txt, remove the version number from the first line, and change the website to a PortableApps.com one.
    Changed... I'm not sure where that one came from!
    The copyright is changed to

    Copyright (C) 2004-2008 John T. Haller of PortableApps.com
    Copyright (C) 2008 Chris Morgan of PortableApps.com
    

    in all of these places... all except this one I had already done, having looked at the Jooleem package. I missed this one on my first pass

  • In the source, you can remove the prefixes on the copyright, just write Copyright (C) XXXX-YYYY Firstname Lastname, and then yours below.
    See above.
  • In the source, the LegalCopyright should be 'PortableApps.com & Contributors'.
    See above.
  • In the source, the VER is for the launcher version (Currently around 1.5.7.0 globally).
    I found it to be 1.5.9.0... I beat you to this one too! I'd already made that change, having seen you comment on it for a few other apps.
  • Remove all the unneeded lines:
    

    ;BrandingText "PortableApps.com - Your Digital Life, Anywhere™"
    ;MiscButtonText "" "" "" "Continue"
    ;InstallButtonText "Continue"
    
    ;=== Pages
    ;!define MUI_LICENSEPAGE_RADIOBUTTONS
    ;!insertmacro MUI_PAGE_LICENSE "EULA.rtf"
    ;!insertmacro MUI_PAGE_INSTFILES
    

    
    Done.

  • Update your NewAdvSplash plugin, and change the second last line (third last because you have a blank line) to newadvsplash::stop /WAIT
    I don't have a blank last line... I'd already removed that too! Done.
  • In the source, line 272, change 200 to 0 as we're dropping splash fades.
    I'd been wondering about that one, but forgot to check back.
  • Change the copyright on the source of the installer back to just John, because you're only editing a few lines specific to the name of the installer, etc. Change the website to just PortableApps.com, too.
    Done. (See above, too)
• In the root directory:
  • In the help.html, add the 'Portable App Issues' from the Jooleem Portable help file. Add a link back to the 'future' BPBible homepage.
    I'm not sure whether you noticed, but I'd commented out that section. What's the point of having a heap of links that don't work, and won't until it's official? At the moment, I've left it commented out.
    I presume you mean bpbible.com? I think that for the moment it's best to leave it as bpbible.googlecode.com, as that's what is working.

Thanks for your report!

On the Development Test page Zach suggested that it should be Development Test 1 as it's a new version. I've changed it to 0.2.0.2 Development Test 1.

Thanks Zach!

(This is mainly going from memory, as I'm on a school Windows 98 machine with a "No USB disks" policy. I'm going to see if I can get that changed, as three of the five machines have working USB ports.)

When uninstalling modules, you need to remove the right things; in Data\resources\mods.d\, there is {modname}.conf.This is the "catalog", if you like. The actual content is in Data\resources\modules. In that folder is the module type (e.g. genbooks, lexdict) and inside that is the compression type; some are GZipped, some are raw. Inside those folders are the folders that you need to delete; e.g. "esv", "isbe"

The path statement - do you mean the environment variable %PATH%, or do you mean the SWORD paths? If it is the latter, I presume that you mean that it is C:\Program Files\Crosswire\The SWORD Project; that is currently stuck there in case you have a local installation of The SWORD Project for Windows, making it automatically use those resources too. I may be trying testing for paths in the launcher, as a bug in the SWORD API seems to cause trouble if the DataPath (the first spot it searches, I think that it appears at the bottom of the Set SWORD Paths dialogue (I'm Australian...) box) doesn't exist.

By the "cross references" window, do you mean the popup box? It will disappear if you move away from it, or if click on it and then back on the normal window. If you have pressed the "Anchor" button, then it should be turning into an ordinary window, with an x button in the top right corner. If this isn't what you mean or what it's doing, could you please post a screenshot?

What is the error message saying problems loading? Is it the "errors have occured... see {path}\bpbible.exe.log for more details" window? If it is, could you please post its contents (it is stored in App\bpbible)?

By the tabs and GUI not respecting the font change, I imagine that you mean the one in the File menu (if not, please elaborate). The font change dialogue (I'm Australian!) only applies to the content of the HTML widget (Other books, Bible, Commentary and Dictionary content bits). The other fonts are controlled by the operating system's settings.

One last questing: what exactly do you mean by blowing away the program? Do you just mean making it not work properly? Or is it something else?

Thanks for your report, Frank! It's nice to get some feedback.

The SWORD paths reference is to the location of a local installation of The SWORD Porject (if found in the registry), or to C:\Program Files\Crosswire\The SWORD Project, the default location. I'm going to get it to check in the next version, and remove it if it doesn't exist.

Cross-references: if you click on the reference, it takes you to that location, in the same window. If you want it in a new window, hover over it and then click on the anchor button in the popup. As for support for going backwards and forwards, this is actually supported, it's just not very visible. Right click on the toolbar (the one with the verse location bar and other buttons) and enable the History toolbar, or go Options -> History to show the history pane. I hope that this stuff will be made more visible in the future.

My break has just finished, so I'll answer your other points later.

I'm back now. Ben's answered most of the rest - thanks.

As Ben says, there is not currently a releases mailing list for BPBible, but if you like I can email you when I post a new Development Test. If you like, post your email address, or just send me an email at chris.morganiser, on Google's gmail.com server.

As for searching through Strong's Hebrew and Greek dictionaries, the only way currently to do that sort of thing is to search a module like the KJV (which has the Strong's numbers included) for God, and then to move over the Hebrew/Greek word's hyperlink, which will make a popup come up, or to click on it, which will open it in the Dictionaries pane.

And for your module installation/ininstallation, just wait for Ben's Book Banisher Manager Hopefully you won't have to wait too long. I think that that's one of three or four things that make BPBible not ready for "prime time" as a PortableApp:

• Book manager (so that users can install books easily; ease of use is one of the main things that PortableApps are about)
• Search in Unicode langauges (currently throws errors, but it's a feature which is critical in making it multilingual)
• Internationalisation/Localisation (I'll spell them with an s rather than a z! }:)) - PortableApps are meant to be released in English, German, Spanish, French, Italian, and as many other languages as possible, I think.
• Search in Dictionaries, Commentaries, Generic Books and Harmonies. (Just a nice feature)

BPBible did not touch the registry.

BPBible does not touch the registry.

BPBible will not touch the registry.

End of story.

Thanks for testing it!

(PS: benpmorgan doesn't like the registry. I don't either. And also, BPBible needs to work under Linux too, and we would like it to work under Mac OS X, but don't yet have a Mac test machine. It probably doesn't work under Mac.)

Hi,

Thanks for testing it, JeffNeedle.

Look in the SWORD Modules repository.
Inside Cult / Unorthodox / Questionable Material, you can download the JST (Joseph Smith Translation).
Download the Raw ZIP, and drag it onto the BPBible window (new feature in BPBible 0.3). It'll install it (it's a GenBook/other book). Probably choose the X:\PortableApps\BPBiblePortable\Data\resources directory.
You won't be able to search in it yet; only Bibles support searching, yet.

I hope to see some feedback!