Previously I’ve used query strings parameters within asset requests so that they act as a ‘cache bust’ parameter, these have usually been the source control revision number and is built into the release process. But I’ve never taken the step of force an expiry date on content that can be cached and the solution in the post is a lot more fine grained than my previous solutions. Something to consider for the future.

So using the XML language file as a base I quickly knocked one together.

…when I was releasing the JavaScript Image Cropper UI I really noticed how much this theme had begun to bug me, mostly for it’s lack of definition and space. It’s a tweaked version of a great Wordpress theme, it has served me well, but I feel it’s time for a change. So I have created a design from scratch…

So here it is in all it’s glory and on a new server to boot, as since the launch of the Image Cropper UI and the resulting traffic the old server has been up and down like a yo-yo. Luckily plans were already in place for the new server and the build was completed late last week.

It took me slightly longer than I initially predicted to get from the mock-ups to the final full Wordpress theme, mainly because I found they way wordpress themes are implemented a little ugly and not the nicest things to deal with initially.

Anyway it’s all in place now and I still like it, although I may have to tweak the comments presentation a little. Here’s a quick list of the major changes:

• Complete new design, giving more space & easier to read content
• Fluid layout, within reason
• Added ability to subscribe to comments
• Added robust code syntax highlighting for posts & comments
• Added ability to use textile for formatting comments
• Added pagination to comments, for posts with lots of comments this is a great benefit
• Utilised Wordpress custom fields for code pages, this provides a consistent and cleaner look to my code project pages.

I hope you all like it.

IgniteImage.com is a website for my web design company Ignite Image, which specialises in creating stylish, modern, accessible, functional, professional, exciting and standards compliant websites for bands and musicians. I’m extremely proud of both the aims and objectives of this website and company and the website itself.

We are a small team of four at the moment; there is me, responsible for design & development, another excellent developer, a designer & marketeer and an artists relationship manager.

All four of us are closely involved in the independent music scene, with us all being active musicians and regular gig attendants; on a personal note almost every one of my closest friends are members of active bands. Being us so closely involved with unsigned and independent artists as well as being web developers we have had constant requests to create stylish and functional websites for our friends, on a shoe-string of course.

This has given us lots of experience in the common requirements and problems faced by independent artists wanting to create their first online presence and we want to share this knowledge and expertise with other artists outside our circle of musician associates.

We aim to offer the most competitive pricing and feature set without compromising on quality to artists and musicians who wish to create an exciting and modern web site for themselves.

So why not head over to Ignite Image now to learn more, if you think we could help you out or you just want to learn more then don’t hesitate to contact us.

I also tided the Formatter up a bit by adding much needed comments to explain the functionality it provides in the context of the HTML Runner.

Finally added a new section to the code page to list known bugs/issues as this is very much a work in progress with very little testing performed I’m sure more will crop up.

Currently there is one issue, also raised by Glen, when the test case/suite is in a different directory to the class definition it is testing and the class definition been tested contains relative includes/requires. Glen also supplied some ideas on how to address this issue but unfortunately I have not had time to look at this, I will hopefully have time to at least begin to replicate the problem within the codebase.

If you find any bugs/issues with the HTML Runner then please either use the comments or the contact form to report the issue until I sort out a better bug reporting solution.

I’ve been playing around with the xUnit family of testing frameworks in PHP, Coldfusion and JavaScript and really like the way they handle testing. However having been spoilt slightly by CFCUnit and JSUnit with their HTML GUIs I found the text runner in PHPUnit to be lacking for my needs.

So taking inspiration from the interface of CFCUnit I created the PHPUnit2 HTML Runner.

• Fixed spelling mistake that caused PHP notice to be thrown when constants file has no common block.
• Fixed bug whereby absolute paths for constants file would throw “file not found” exception.
• Fixed bug in exception handling which would cause Mach-II to die.

View the Application Constants Mach-II PHP code page for the download and instructions on it’s implementation.

So today I spent a couple of hours re-writing it from scratch to bring it inline with the latest version of Martins. View the Application Constants Mach-II PHP code page for the download and instructions on it’s implementation.

As a little side note I hope that the code section of my site will allow me to release other little useful things like this I have kicking around. I’ve got at least one more Mach-II PHP plugin that I’m going to try and tidy up and release sometime soon.