June 20
The past week has been quite productive. I was able to work an XML database and class easily into a few test classes for a library file. Thursday night I had (another) programming dream, woke up Friday, and realized the dummy install structure I had for the package wasn’t secure at all on any live Geeklog install (the tests and databases were all in the public_html folder, while they would need to be outside the webroot to be safe). The configuration structure and GUI I had set up didn’t allow them to be easily moved outside.
Speaking of configuration, in the next week I’m considering looking into creating an install script for the package. Right now, the user only needs to open 3 files and configure 6 paths… but given the extremely fickle and securely delicate structure of the package, it will probably save people a lot of head-scratching if a script puts things together for them, especially if they aren’t Geeklog developers.
My main goal for the next week is to begin the assault on lib-common. I’ve spent some time poking around and trying to understand what’s happening and why, but without too much luck. My mentor mentioned that this was one area he would like to see tested, however (for obvious reasons: it appears to be the core of the CMS). Once I understand what’s happening in it, Geeklog won’t hold many mysteries for me, and I’ll be ready to write the much-needed documentation for this test package. In addition, any serious design flaws in the package right now should be exposed while working through lib-common – which will save me the trouble of reorganizing the package later, restructuring paths and calls, and rewriting documentation.
