Tumblog archive for July

Julien Phalip has put together a fantastic article on how he tackled the problem of different users wanting different date formats.

Using his simple code samples, you could give the user many different choices for date format - yyyy-mm-dd, dd-mm-yy, mm-dd-yyyy, or others. The best part is that these formats are then picked up not only for displaying dates to users, but for any date entry that user has to do on your site.

This looks like a neat piece of JavaScript that will check the browser your visitor is using, and provide a discrete popup message if there is a newer version available.

It isn't a hard push into installing something other than Internet Explorer, but it will alert them if they're using a browser older than IE7, FireFox 2, Safari 3 or Opera 9.25. This is a beautiful way of encouraging users to use recent versions of their browser, which makes life easier for them (better security) and you (more reliable JavaScript implementation).

According to a survey done of 460 Australian organisations with over a hundred employees, 59% don't reply within 1 week.

Granted, this survey has been done by a company who specialise in responding to your companies incoming email so it's likely to be a little biased - but my personal experiences certainly reflect their findings.

There is nothing worse than e-mailing a company (either directly or via their website) and not receiving a response. Being an internet-minded person I expect a response within a day or two, which I don't think is overly unreasonable - if they do not wish to respond to e-mails, they should not list an e-mail address on their website.

This is an area that small business seems to excel at - when there's only one or two people at the helm they pride themselves on answering customer queries in a quick and useful manner. Unfortunately the same can't be said for larger companies.

This looks like a very useful application for managing Javascript & CSS files in Django projects. It can combine and compress JS & CSS files either manually (via command line) or automatically (when a user hits your site and one of the files has been changed).

A few sites I'm working on currently include multiple JS files to do their job, this should let me minimise that.

It's just a pity the source code is only available via bzr - since just about every other Django application uses svn it's often nice to keep the status quo. It also removes the ability for other application authors to refer to it via svn:externals. Oh well.

Django, my web development framework of choice, has reached Alpha 1.0. There's a bunch of Backwards Incompatible Changes to the API which will require changes to your projects, but the codebase should be pretty stable from here to 1.0.

The biggest changes to this from the last official release are 'Unicode everywhere', a new and more powerful admin module powered by newforms, an updated database ORM that's more efficient, and automatic escaping in templates to help reduce the risk of cross-site scripting attacks.

1.0 should be released with a party at DjangoConf 2008 on September 2nd - I look forward to it (Although I won't be at DjangoConf, unfortunately).

Great work to everybody involved!

A collection of interface design solutions from all over the web, where users can mark patterns they like, and learn from other's design solutions.

Not only is this a beautiful site, but the screenshots they've provided are going to provide some great inspiration for future projects.

CompanionJS is a javascript debugger for Internet Explorer, somewhat similar to FireBug for Firefox. Looks like it'll be a useful tool for finding & fixing JS bugs in IE prior to deploying projects, as like most web developers IE isn't exactly my browser of choice.