I’m happy to report that, after a few months hiatus, development on Scripto is progressing rapidly. Ken has been hard at work designing some impressive user interfaces, while I’ve been debugging the library, writing test cases, and preparing the application for user testing and, eventually, public release. Our GitHub repository now follows a conventional software directory structure, complete with UI examples and unit tests. (I’ll let Ken discuss the UI examples he designed in a separate post.)
The unit tests are a new addition to Scripto, and they’ve already proven their worth by pointing out bugs and stabilizing the code. I’ve decided to use the SimpleTest testing framework because of its easy setup and implementation. By running the tests on your Scripto installation, you ensure that your custom CMS adapter returns expected results, the MediaWiki API client is running correctly, and Scripto is properly bridging your CMS and MediaWiki. Peace of mind, for the developer and end user alike, is the goal here.
Soon I’ll plug Scripto into The Papers of the War Department (PWD) website for what will be the first large-scale test of the software. The PWD database has no native application programming interface, so I’ll need to write one, most likely using SimpleAPI, a personal project of mine that provides the underlying architecture for an API. Once that’s done I’ll write a PWD adapter for Scripto, install MediaWiki, and integrate a Scripto UI into the existing PWD website.
Remember that the end-user should be unconcerned about these technical details. All they’ll see is a web page containing a document image viewer and transcription form. Once we build plugins, modules, and extensions for the most common CMSs, anyone will be able to install and use Scripto!
I’m excited about the upcoming, initial phase in testing. We’ll keep you updated on the progress right here.