I think that the only keyboard/mouse combination I would change mine for right now is this one . Wireless and natural, me likes!

I can’t really do without a natural keyboard now (I have one at work as well as home after some persuasion). Microsoft mice are also more comfortable than Logitech for me. The only way up is wireless, I guess. For now, however, I think I shall stick with my wired versions… Wireless is so tempting though!

dCron is coming on well. It will now auto-refresh the job list when you edit the dCron.rc file to add or remove jobs. This is a little buggy at the moment, in that it sometimes tries to read the changes before the file is fully saved and so crashes with an IO error. A possible fix for this is to catch the crash and defer the update until the next time that dCron checks for jobs to execute.

A very useful writeup on positioning in CSS has been posted at Stopdesign. It details how nested positioned elements relate to on another. I hadn’t really thought about this before, but it has cleared up a few poitioning problems I’ve had for a while.

I didn’t realise that elements that are positioned become the point of reference for positioned elements inside them, taking over from the browser window. Not knowing this lead to some headaches when I was doing the current design of dx13, however I was able to work around the problems. Knowing this positioning mechanism should prove useful in future projects. Hmm, ideas…

<div style=“display: inline;">

That was something I had to work with yesterday. Even worse, a lot of the inlines were set in a separate script. It was a very confusing time, as my divs just were not doing what they are supposed to do. So I changed them to span tags and it all became much simpler =)

The W3C HTML validator’s helpful, understandable error messages are only notable by their absence. Good news then, the next version of the validator is going to feature much improved messages that are designed to help the user. I’m now starting to be able to internally ’translate’ the errors the current validator spews out into understandable errors with my code. Even for those of us familiar with the validator and its esoteric errors, missing out this internal translation step will be a great timesaver. For new users, it will be more of a god send. It certainly would have been good for me to have had nice understandable error output a few years ago…