I’ve modified the layout and backend engine of QuickBlog further – all date data is now stored in a common UNIX timestamp format, rather than the silly proprietary setup that I assume was done to make searching by date easier. (It took three more lines of code, and a bit of retooling of MySQL, of course)

I’m looking to add more functionality beyond what already lies – David Grant made it pretty extensible with everything, and I’ll most likely first append a secondary field for ‘modified’ date.

Initially, QuickBlog would write out your time of access, then overwrite it with the last edit, (Basically, it just said ‘what time is it? Ok, that’s when this is entered.’, rather than check for this information’s existance beforehand.) I’ve already modified it internally to support the ability of understanding this arbitrary modification time – now to just decide how I want to implement it.

There’s been rather little buzz regarding personalized locale support. I highly doubt I’ll be doing this, as I barely speak English, everything’s fairly hard-coded in structure, and it’s just as easy for anyone else to do a search in the code; I want to keep it as lean and functional as possible, much as David’s initial intention. I’ll most likely rewrite the RSS feeds to be proper, displaying the title, and approximately three lines of data, instead of just the title.

[Edit: I might? I dood it. I’ve now got seperate fields for entry and modification time. Oh, and I’ve dumped all tables from different bits together, and, uh, rewrote most of it. I rewrote the RSS too.]