Thursday, July 21, 2005

Building OS X Dashboard widgets

O'Reilly Network: Let's Build Another Dashboard Widget

OS X Dashboard widgets don't seem that complex. The development requirements remind me of HyperCard -- a bit more than DOS Batch file programming but nothing like writing Cocoa or Java apps. The sort of thing that will attract a lot of end-user creativity.

iMovie HD 5.x bugs

iMovie HD bugs

See also this Macintouch posting. I've just ordered my G5 iMac with a 400GB SATA drive nad I'm getting ready to use iMovie 5 (after some experiments with iMovie 2.x on an older G3 iBook -- that was an excellent version of iMovie, subsequent versions have been a bit discouraging), so this is of interest to me.

I hope to update a y2k web page of mine on this topic, but that may not happen until September. I found five years ago that the technology wasn't ready (at least for me), but we've come a long way since then.

Wednesday, July 20, 2005

Phil Bradley: Google Earth, Google Maps. Resources Utilities Information

Phil Bradley: Google Earth, Google Maps. Resources Utilities Information

Phil has done a great job rounding up information on Google Maps and Google Earth, including a link to Google Earth Hacks. I'll add the last to my bloglines.

Dashboard widget: miniBattery

miniBattery - Dashboard - Status

Tracks cycles too.

Footnotes for the web

Daring Fireball: About the Footnotes

I've long been interested in Footnotes for the web, I like the mouseover techniques some sites use, though I've had other ideas I've never gotten around to tracking down. This site has a good discussion of a basic but very reasonable approach.

Tuesday, July 19, 2005

Macintouch on color profiles (ColorSync)

iPhoto (Part 14)

This Macintouch discussion has a superb thread on Color Profiles. Alas, iPhoto does not hold up well.
Chris Murphy, co-author of "Real World Color Management, 2nd Edition"
The iPhoto 5.0-5.02 color problem, previously reported, is caused when iPhoto converts images from the embedded source profile to the display profile, then incorrectly embedding the Generic RGB profile. iPhoto 5.03 resolves the bogus tagging that was the main problem, but concerns remain. Here are the three behaviors to expect from iPhoto 5.03:

1. Untagged images. iPhoto assumes the currently set display profile for images that do not contain an embedded ICC profile (including images containing only EXIF data indicating the image color space is RGB). It then converts from that space to Generic RGB and saves the edited image with that profile embedded.

2. Images tagged with "table-based" profiles. iPhoto uses the embedded profile as source, converts the image into some as yet undetermined intermediate space for performing the requested edits (red eye, crop, enhance) and then converts again to the original source space. The closest thing to this intermediate space I've found is sRGB. Thus the image data is altered, but the original profile remains embedded. Color appearance of the original is preserved only insofar as colors exist in this "sRGB" like intermediate space, and if they don't color appearance is not fully preserved. Subsequent edits result in additional conversions.

Needless to say neither of these are high quality options. In the first case, anyone working with untagged images isn't particularly quality conscious in the first place, so they're unlikely to be hurt by the first behavior. The second behavior, on the other hand, will occur when any kind of table based ICC profile is embedded in the image, including matrix based profiles using table-based tone reproduction curves. Examples include some display profiles, and essentially all digital camera, scanner and printer profiles. Apple should perform conversions through a wider gamut color space than they are currently using, and it should be a one time "normalizing" event to avoid additional and unnecessary conversions.

3. Images tagged with simple matrix and gamma based profiles are not converted. Thus, iPhoto is now a good citizen when it comes to normalized workflows. Examples of such RGB spaces are Adobe RGB (1998), ECI RGB, and ProPhoto RGB. I don't include sRGB in this list because there is a simplified sRGB which causes behavior 3, and the more common, correct, and accurate one with flare which uses a table based tone response tag which causes behavior 2.

In most cases, the conversions aren't a problem, but if you're working with color-critical images either ensure they are tagged with one of the aforementioned profiles or avoid editing images in iPhoto 5.0-5.0.3. The clincher for quality conscious users is that iPhoto 5 doesn't do normalizing, so the conversion into one of these well behaved editing spaces, e.g. ProPhoto RGB, must be done in another application anyway.

The plus for professionals who already use Adobe RGB (1998), ECI RGB, or ProPhoto RGB will not need to be concerned about iPhoto 5 doing something senseless like performing ill advised color conversions on such images when doing something as simple as cropping.

Yech!! I've used sRGB in my workflow, it worked well with iPhoto 4. I wonder if I should switch to AdobeRGB for a while?

Firefox is getting buggier?

Mozilla - Home of the Firefox web browser and Thunderbird e-mail client

I'm having problems with recent point releases of Firefox. PDF integration is problematic at times, and lately the "save link as" context menu option doesn't work in some web sites. I suspect some of the security fixes are causing things to break, even as most developer resources focus on 1.1. At this rate I'll be keen to switch to the first beta of 1.1!