Most posts will probably end up in this category one way or another, because I tend to write a lot about technology and tech-related topics. I work online and really enjoy gadgets and gizmos, so a lot of what I get involved in revolves around those subjects. Anything from regular expressions to iPods to The Magic Bullet is fair game.
There appears to be something dodgy going on with my paths. They aren’t resolving properly, which is causing internal links to be one or more levels (directory-speaking) out of whack.
This is really annoying… until I fix this I can’t really work on the commenting system, and I’m not launching the new Dented Reality website without the ability for people to comment on posts… no way!
Lisa Chan from Stanford emailed me, wanting to know if we could work together on building a search log analyzing system. I emailed her back with a stack of the details of stuff that I was planning and haven’t heard back… I wonder why not? Maybe she’s taken my ideas and is off building it without me?
UPDATE: I still haven’t heard from Lisa 😛
New tool being created to analyse the logs of a search interface and pull out information about the most searched for terms, things returning lots of (or no) results, plus information regarding best bets.
Just kidding, but I got some details back from Lisa C, and she appears to have some very specialised requirements for her system. I have suggested that it might be better if we work together to develop a “base system” which would include the complete logging functionality, and then she can customise and/or extend the reporting/analysis interface as required.
I think this approach should work quite well, allowing me to collaborate on a logging module, and to refine the database schema, then develop a generic, “useful-across-the-board” analysis interface, which should be capable of being extended easily. Metabase, here I come.
Work on my site is coming along. I have added in blosxom v1.1, which went pretty much without a hitch. I had to modify my template slightly, but that was more because of my dodgy custom handling, rather than anything to do with blosxom itself.
I’ve been spending some time on the projects section, getting the project pages up to scratch and re-formatted; it’s looking pretty good. I am taking a few of the old projects offline, because they don’t have any documentation, don’t work anymore, things like that 🙂
I’m not going to put a date on when the site will be live, but given the current progress, and the list of things to do still, I would estimate about 2 weeks. Here’s the current list;
So there we go. That’s what I’ll be working on in the near future. And for those interested, I will be creating a custom search system, which integrates Google‘s results for within my website (using XooMLe) with a selection of manual “Top Picks” or “Best Bets” which I have selected for certain terms. I have the rough idea planned out already, just need to implement it in code. I will probably make the code available for download once it’s complete as well, so keep an eye out for that 🙂
That’s all for now – time to get back to life.
Fortnightly articles/reports posted by Monsieur Guru Nielsen himself. Some of these are pretty good, personally I think some of them are just plain stupid.
An example of taking things too far: in the most recent alertbox, Nielsen extrapolates his calculated statement that the companies he studied which would “spend $3,042 per employee annually to cover time spent on the sixteen tasks we measured” to mean that if we improved intranets to the best ones they saw in their tests, we would “save the world economy $1.3 trillion per year”… come on dude, seriously. You so can’t make that assumption.
The plan with these helper scripts that I am writing is that blosxom will be able to operate in a “REST-like” environment. This means that directing a browser to a URL like /blogging/blogger.com/ should load the blog entries in that directory (if it is within a defined blog-tree).
It’s working so far, and I have added in the option of linking to ‘rss.xml’ within any directory in the blog-tree to get an RSS feed of that level/category/sub-blog. Sweeeet. Next up is to eliminate the permalinks needing to use the blosxom.pl script in the URL (i.e. so that archives don’t have to link to blosxom.pl at all).
I am re-writing a large proportion of the code which runs RESTxom, to make it more portable and reliable. Also trying to make sure that *everything* works properly, rather than getting any nasty surprises down the line!
Once this is done properly, then RESTments should be pretty simple(?) to add in.
I seem to have sorted out the main code for making blosxom at least pretend to be RESTy, now I am working on the archives system to clean that up. It is largely based on the main code, but needs to take into account the “forced” /archives/ directory when working out relative paths and stuff like that.
Once this is complete, I will then start working on creating some templates for the actual site (coverting my Visio wireframes into real XHTML!).
RESTments? REST-based comments for RESTxom
Am working on a commenting system for RESTxom which will store a parallel file for each entry called “<entry>.comments” and will act like a small flatfile database to store comments for each post, which will also, of course, have REST-friendly URLs.