Vi Help Sheet (Liquidicity)

Today I found one of the nicest Vi Help Sheets I’ve seen in a long while. I came by this via Smashing Magazine and just had to include it on here. Most people who know me know I’m one of those odd developers would still does the bulk of their development work using VIm as I find the speed it offers unparalleled. Continue reading Vi Help Sheet (Liquidicity)

Fun with CSS3 and Webkit

The power of CSS3 and Webkit really impresses me, especially when I see people creating fantastic things like a StarWars AT-AT which looks like it’s moving without using flash.

http://anthonycalzadilla.com/css3-ATAT/index.html

After the announcement of the new Apple iPad last week, and the fact it will not support flash there is still hope for rich interactive content with CSS3 and Webkit.

NOTE: Only webkit browsers (Chrome and Safari) can view the animation correctly.

Initial thoughts on Doctrine

I started to use Doctrine this year, and I have to say that I think I prefer it over Propel now on how you construct queries. The syntax is a little cleaner as well in my opinion. Here is an example of both syntaxes to retrieve a set of articles from a database which match a few criteria.

Propel:

$criteria = new Criteria('article a');
$criteria->add('a.status', 'active');
$criteria->add('a.type', 'news');
$criteria->addDescendingOrderByColumn('a.id');

Doctrine:

$query = new Doctrine_Query::create()
       ->from('article a')
       ->where('a.status = ?', 'active')
       ->andWhere('a.type = ?', 'news')
       ->addOrderBy('a.id DESC');

I also find the Doctrine way or building the query easier to read compared to the Propel one.

Once I’ve worked with Doctrine some more, and built some more complex queries I’ll add some more thoughts.

Adobe® BrowserLab

Last night I was introduced to a very nice cross-browser tool produced by Adobe called Adobe® BrowserLab. This tool allows you to test your website in multiple browsers on multiple OS’s without the need for virtual machines, Adobe does that for you.

https://browserlab.adobe.com/index.html

The way it works is to take a screenshot of your chosen URL in several different browsers and then allow you to compare each image, and see how your pages differ from one browser to another. This allows you to spot any possible bugs or errors. It does not allow you to test the interactiveness of your code though as it only provides static screen shots. Though it is still a very cool idea.