PocketBible for Windows Progress Update #9

Search words highlighted in the note viewer.

Note Editor

We reported extensively on the note editor in progress update #8. We spent a little more time on that task, in particular as it relates to when we save the changes you make to a note. First, we wanted to make sure that your edits get saved when you exit the app, so we provided a notification to the note editor that the app is about to exit so that it can save your work. (You probably think that just “happens” โ€” and it does โ€” but somewhere there’s a programmer who wrote the code to detect the fact that the app was closing and made sure that your work got saved.)

In addition we took more control over exactly when we sync an edited note to the server. When the note is open for editing, our other apps periodically sync to the server to make sure your changes get saved. This is potentially important on a mobile device where you might drift out of Internet coverage or the battery might die at any moment.

On the desktop, we can be a little more patient. We wait until you are done editing the note (say you switch to the viewer or the other editor), then we save all your changes to the server at that time. Of course locally we save your work every few seconds so that you don’t lose anything if the power goes out. But by waiting to sync with the server until you’re done editing, we make certain problems easier to solve when you have the note open on more than one device at a time.

Finally, when linking to a note from search results, we now highlight the searched-for word(s) in the note viewer. This may be a first for PocketBible. I don’t recall doing this in previous releases, though some of you with memories that extend back to the last century more clearly than mine do might remember it differently.

Note Search

Note searching is similar to book searching except there are no indexes and of course the text comes from a completely different place. The overall structure of the code is the same except for when you get down to actually looking for the word or words in the text. Book text comes from an LBK file which has a lot of indices to support searching, but notes come from a database with no indexing. We’re able to use exactly the same code until we get to that last step, where it branches depending on the source of the text being searched. As a result, a lot of the logic of searching was already done.

The display of note search results is similar to displaying book search results. What we didn’t realize going into this was that it is so similar that it can actually share the code. So the Note Search, Book Search, and Journal Search panels are just 3 instances of the same chunk of code (we call it an “object” rather than a “chunk-o-code”). So we spent some time throwing away some work we had done on separate panels for Note and Journal searches and adapted the existing book-searching code to account for notes.

Similarly, the Journal is just a collection of notes, so the work we do for regular note searches and note editing automatically applies to the Journal. So even though the Journal is an Advanced Feature Set feature, we’re doing the implementation now as we work through the general notes feature. (Other AFS features will likely be put of until work on the standard feature set is done.)

Note search showing note excerpts in results list and highlighted search words.

On the other platforms, when you do a search for a word in your notes, the search results will show an excerpt of your note, but it’s just the first couple of lines. You don’t see where the thing you’re searching for actually occurs in the note. In the Windows version, we’ve made it so that search words are highlighted in the note viewer and are also highlighted in the search results. And we’ve added a smart “excerpt” function so that if the word you’re searching for occurs later in your note than the first couple of lines, we’ll show you the portion of the note in which your word occurs.

Since the book search, note search, and journal search all turned out to be the same/similar code, when we added excerpts with highlighted search words for notes and Bibles, we were also able to add them for non-Bible books.

Study Panel

As a result of working on the note editor, we learned more about how to better handle layout of other panels. This is particularly related to the re-layout that happens when you resize the Study Panel or the entire PocketBible window. Previously we had been doing a lot of manual calculations to position buttons and text appropriately. It turns out there were some easy ways to allow that to happen more automatically.


We’re just wrapping up work on managing (add, rename, and deleting) categories. This gets tricky when you’re syncing all that data to other devices, so we’ve had to do a lot of testing of the entire synchronization path from Windows to the server and from the server to other devices.

Book Display

We happened to notice while doing our own devotional reading that the book pane was not getting refreshed when you change the start date of a devotional. So now it gets refreshed to update the dates you see in the text.

16 Replies to “PocketBible for Windows Progress Update #9”

  1. Thank you for the update! Sounding great! Canโ€™t wait to try it! Hoping for a beta invite!

  2. I Haven’t been following the update closely. Are you getting close to releasing a beta version?

    1. Gerry, we talked about the schedule in update #7. But to address your question, we are closer today to releasing a beta version than we were yesterday.

      1. LOL Craig! My ol’ boss Herman, who went to be with the Lord several years ago, when asked the same question would say, “Good news! We’re closer than ever to going LIVE with …”

      2. Gee, that sounds familiar — even in life ๐Ÿ™‚ I’m one day closer to “whatever” than I was yesterday. ๐Ÿ™‚

        All joking aside — I am seriously impressed by what I’m seeing in these images. I have both of the older versions of PocketBible for Windows on my desktop (and laptop) machines. I also purchased a resource recently that specifically cautioned it was not compatible with the desktop version.

        I’m very much impressed with where you are and how far you have come. Keep those cards and letters coming ๐Ÿ™‚

      3. Hi Craig. I have been using PB in its many forms for 20+ years. I have it on my desktop, ipad & iphone. I love the ipad & iphone versions, they are exceptional. However the desktop app is not so good. In fact i reverted to version 1 which is quite ancient but is so practical and easy to access multiple versions, dictionaries & commentaries all on one page. I hope version 3 is a vast improvement on ver 2.
        If you would like a critical appraisal of ver 3, i would be happy to give the beta a run

        1. Version 2 is not an upgrade to version 1, it is just a different version โ€” created for a whole new user interface paradigm that Microsoft said was the future but wasn’t. Version 1 continues to work fine but doesn’t have a way that we can add new features. Version 3 is not an upgrade to version 2, it is a whole new app based more on the code from version 1 and the user interface concepts of the macOS and iOS versions of PocketBible. We’ve posted lots of screenshots and at least some video of version 3 in action so hopefully it’s clear that it is an improvement already.

  3. Appreciate the updates and as an IT director, I like the inside look at how you’re developing the code!

      1. I think we unintentionally appeal to people with STEM brains. And brain stems, but that’s a different story.

  4. I sense, especially from this latest update, that you’re really starting to like Windows, even prefer Windows for how you’re able to get things working… ๐Ÿ˜‰
    There’s no use denying it, I can sense it in the very words onscreen ๐Ÿ™‚

    Given that this will be used with Windows touch-screens (as is mine) would it be possible to have the 3 dots area at the bottom of the screen a bit larger, so it’s easier for fingers to hit the correct area, and NOT the wrong area. They seem quite small compared to other icons that we will be touching.

    Also, the calendar icon (2nd up from the left bottom of screen, seems to be the wrong orientation to me. If that is an icon for schedules for reading etc, our calendars always flip over the top, not to the side. But it could be different on your side of the world. I suppose some diary’s go that way? It looks like a car battery icon actually. Maybe some little dots to simulate days of the weeks would work there.

    Love how the program is progressing. Can’t wait for beta testing days.

    1. Ken,

      I’ve actually never used this new app on a Windows machine. We do all of our development and testing on Macs running macOS.

      Once we get to where we can do significant testing on tablets, we may make size adjustments to some user interface elements or provide alternative, touch-friendly ways to access the same features without making the user interface overly chunky for mouse users.

      The Journal icon (2nd up from the bottom of the screen) is in the correct orientation. It is not a reading schedule button. As you can see from the last two screen shots in the article, reading progress and devotional navigation is done from the “Go To” pane (top button).

  5. Hi Craig,

    Thanks so much – I can’t wait. Been using the program for quite a while (yes, my trusty Palm Tungsten T3 is right next to me – still use it) and I can’t wait for this edition. Thanks for all the hard work1

  6. Hi Craig,
    It all looks good. But I was very disappointed to find out that my current Windows Desktop PocketBible version 1, did not allow highlighting and underlining for commentaries and books. After sinking so much money into PB and Laridian books, I sincerely hope you are fixing that problem in this new edition of PB. Thank you.

    1. Tina,

      You won’t be able to highlight non-Bibles in this version, but that’s something that is on our list to look into in a future release. Remember it’s not just a matter of updating the Windows app to support that feature, but rather implementing it in the Windows app, the Mac app, the iOS app, and the Android app. In addition, the synchronization service that runs on our server would have to be updated, along with the database schema (on the devices and on the server). There are portions that will be in common (I guess only between macOS and iOS), but because this is a very user-interface intensive feature, that has to be custom-implemented on each platform. And that’s just the general description of the problem. When you get down to the brass tacks, it’s a complex problem to do this in a way that works. That’s why we haven’t found a Bible app yet that syncs between multiple platforms and does this correctly. Most don’t even attempt it. But yeah, we’re thinking about it. ๐Ÿ™‚

Leave a Reply

Your email address will not be published. Required fields are marked *