by ·4 Comments

Growl iconIt’s time again to circumvent Apple’s Mail Plugin policy and update the GrowlMail Bundle with the correct identifier string. Otherwise, after updating, Mail will tell you it has disabled the GrowlMail plugin and will move the bundle to ~/Library/Mail/Bundles (disabled).

To amend this, follow these steps:

  1. Quit Mail
  2. Move the GrowlMail.mailbundle Folder back into ~/Library/Mail/Bundles
  3. Enter the following two commands into your Terminal: 
    defaults write ~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "1C58722D-AFBD-464E-81BB-0E05C108BE06"
defaults write ~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "9049EF7D-5873-4F54-A447-51D722009310"
  4. Start Mail and enjoy Growl notifications for new eMail again!

by ·1 Comment
Foursquare Latest Checkins Widget Screenshot

Foursquare Latest Checkins Widget

I just released the first public version of my newest WordPress Plugin.

The Widget displays your latest Foursquare checkins in your sidebar. There are quite a few plugins out there that offer similar or even more features, but my motivation was, that I wanted the venue icons to show up as well. After a bit of research I found out, that the only way would be to use Foursquare’s API and not the private RSS feed most of the other developer used for easy integration.

Since I didn’t want to learn yet another API I just used Yahoo’s awesome YQL to get out the data I wanted. There is no caching impemented in the plugin at the moment, so it would be wise (anyway) to have some kind of page caching mechanism installed on your WordPress blog, otherwise it might slow down page loads, because of the sometimes relatively high latency of YQL calls.

Head over to the Foursquare Latest Checkins Plugin page to download.

Feel free to comment with feature requests, questions and criticism. I’ll try to answer it all!

by ·0 Comments

Firefox versus IE9I just stumbled upon this infographic by @paulrouget that explains the differences between Mozilla Firefox (4) and the just released Microsoft Internet Explorer 9. I have to say, that I was pretty excited about this new IE version, because I thought that maybe finally the headaches over IE compatibility will start to fade away. But after reading through all those information I am very disappointed. For instance they still didn’t implement simple CSS stuff like text-shadow? Seriously?! (And I’m not even talking about transitions, gradients or HTML5 history API)

Click here to see the graphic as an HTML document with clickable links to all the test sources.

When will Microsoft wake up and get their act together? Is there really any incentive in releasing a browser that lacks so far behind? Especially when they already acknowledged that their older products (IE7 & IE8) are lacking most of the modern web technologies and thus they needed to release IE9.

 

Thanks to @malde for sharing this in Google Reader!