So how does the user input get saved dynamically to the database? It already happens in a similar way with post tags. Users enter them on the fly and they’re processed and the user interface is updated without needing a postback or page refresh.

The hard part was figuring how to tap into the existing AJAX / PHP functions from my child theme. After some deep, deep digging, I found the interactions in the WordPress core.
« Continue »

Here’s a confession: this part of the plugin is only half-baked. It’s a work in progress.

Users can select Books, Chapters, Verses using the Javascript tool. But what about quick entries? Surely a good user interface maximizes keystrokes and minimizes mouse clicks, right?

Well, I tried. The issue is how many permutations of entry types I’d have to deal with — let alone the abbreviations and commonplace names of books that I’d need to check for.

For instance, how many ways can you cite a scripture reference?

• B
• B C
• B C:V
• B C-C
• B C:V-V
• B C:V, V
• B C:V – C:V
• B C:V – B C:V

B = Book, C = Chapter, V = Verse. And this obviously doesn’t account for other styles of notation (such as using a period (.) instead of a semi-colon (:) ).

« Continue »

The Bible’s BIG. 32341 elements in the XML file, to be exact.

The WordPress custom metabox spaces are pretty small. I started out wanting to put this in the side panel on the Admin screen. How do I fit that many elements into a 300px width and not have the page go miles and miles deep?

Javascript was the easy solution — but not so-easy was figuring out what UI tools I could use within the JS. I started with tables, bot those became clunky and inconsisted very quickly. Plus, they broke horribly. I wanted it so that if the user shrunk their window < 800px wide then they'd still be able to have the tool degrade gracefully (and maybe even still work). Tables were shooting off the edges and messing up the spacing. Fluid web design != tables; and in this case, it didn't even = div tags. I did it with unordered lists (ul) and list-items (li) carefully controlled by the CSS. « Continue »

So the CSS was the eas(ier) part. Then came the Javascript. It had to be snappy and non-clunky.

I started out trying to parse the XML with my own logic. Not a good idea. I used the JQuery framework to get it working. Here’s the resulting JS code snippets with commentary:

« Continue »

To start, I looked for data objects that already existed for the bible on the internet. I looked at using existing APIs for popular online Bible services, but didn’t find any that offered the backend database support I’d need for relational tables in MySQL.

I googled “NRSV xml” and found some good stuff, including a file that’s no doubt a copyright violation and might be taken down at any time.

(If starting over, I’d use the SBL GNT or a KJV version that’s now public domain)

« Continue »