Install ImageAPI before upgrading to ImageCache 2.x!!
I'm finally comfortable enough with my Image* namespace to have official releases of the 2.x series of ImageField and ImageCache + ImageAPI...
I'd like to extend thanks to everyone who has filed issues and submitted patches, especially Drewish and Quicksketch.
Now that my 2.x's are out I can start on the 6.x ports. ImageAPI already has a working port in HEAD, but needs some bug fixes ported from 5.x-1.x. There is a patch for ImageCache pending in it's queue and it should be a trivial port.
Writing simpletests for imagecache_create_url and file_create_url today, I had to change a few of Drupal's persistent variables, namely clean_url and file_downloads. I was kind of frustrated by the need to save the old values, set the values I needed for the test case, run the test, then restore the old variables.
I have a love hate relationship with microformats. The apostles who think they're the end all be all of the semantic web drive me insane. 'Semantic Web' aside, microformats are a powerful approache to reusable design. Consistent markup with the appropriate JS or CSS can make for great reusable UI widgets.
ImageMagick support has been a release blocker on this module for me. My attempts at using the Imagick extension failed, and I finally broke down and wrote the imageapi_imagemagick module, and it needs testing.
If you have a working imagecache 2.x installation or use imagecache 1.x with imagemagick I would appreciate some testing. I suggest using imagecache HEAD with the imageAPI 1.0 RC 2.
What is GeoLocation module?
For OSCMS, over a year ago, I wrote a module called geolocation as an example CCK field. It has languished in CVS for quite a while, I finally set up a project for it today, and I'm looking for a co-maintainer.
I stuck myself in the Hack Shack, where I should probably keep myself as jaded as I've been lately. Ate me some tasty Bagels and got to help a few folks out... I even gave a presentation on workflow in Drupal 5 (Yes I occasionally show for my sessions.).
I sorta had a good time at DrupalCon 2008. If it weren't for the overpriced convention center, marketing sermons slyly disguised as sessions, stale presentations that I've seen a few times now, and inflated attendant pricing, I would say it was awesome. I don't think I'll be attending another DrupalCon unless it's an excuse to expense a trip to Europe.
I have a client whose sysadmin is adamant about using Lighttpd as a webserver, whose site also uses imagecache.
There are some major differences in Lighttpd's rewrite system compared to Apache's rewrite system. The difference that is most important is the lack of the file exists check provided by the -f flag to apache's rewrite conditions.
Crell published some interesting benchmarks in 'Benchmarking magic'. He mentions the overhead of loading and parsing in PHP being a big bottle neck in the comments. My current project uses a few classes that kind of clutter the .module and aren't always used. Having PHP magic functions on the mind I immediately started thinking about __autoload and Drupal.