StickyBrain and Yojimbo: CoreData is the key difference

StickyBrain 4.1 beta brings serious features to the table - The Unofficial Apple Weblog (TUAW)

My main question when comparing the two will be which uses a more accessible data store. Yojimbo uses OS X CoreData, StickyBrain uses its own database store. Point and game to Yojimbo.

No more single vendor data stores. CoreData is something we can get at.

Aperture: good news

Two pieces of good Aperture nows.

First, Version 1.11 is out. I hadn't expected it for a month yet. Given the history of this product a 1.11 release weeks after the 1.1 release is a sign that Apple is serious about squashing the quality issues.

Second, Gruber has a believable story on why the 1.0 release was so awful and why it's likely Apple will get on top of the problem.

Automator does something useful? iPhoto browser

macosxhints - 10.4: System-wide iPhoto browser

Mail.app imap disaster - retracted?

This was transiently scary.

My wife's email is setup on two computers. Both use IMAP.

On the iBook, running OS X 10.3.9, her Mac OS X - Mail (Mail.app) IMAP account is set to view messages and delete permanently when deleted on the iBook. Since 'store sent on server' and 'store draft on server' don't work with our ISP's IMAP implementation, every message she sends defaults cc to herself. BTW, if you drag a message from a local store to the inbox it vanishes forever. God knows where it goes.

On the iMac, running 10.4.6, her Mail.app IMAP account is similary configured. The idea is she drags messages from her inbox when she's done with them to a local folder on the iMac. The messages are thus removed from the IMAP server.

She can thus work her email from two machines, but archives it at one machine.

Except today, after doing some IMAP work, every archival message on the iMac displayed the same error message -- basically saying that only the header was stored locally, the message itself was on the IMAP server and I needed to reconnect. Except, of course, it wasn't.

I quit Mail.app and went for a walk. When I returned I tried again. All of the messages were back again.

Weird.

PS. I've never done much with Mail.app. Today, when configuring my wife's email, I started using Smart Folders. The ability to create and chain these Boolean queries (iTunes can chain queries, Mail.app can chain queries, iPhoto cannot) is very impressive. Thanks to Spotlight they update instantly. I'm setting up her email to work rather like Gmail, but Mail.app is missing Gmail's ability to attach tags to messages. On the other hand Mail.app has a far superior query language and powerful rules, which can include AppleScript extensions. Mail. app may not be rock solid, but it is certainly very powerful.

My RAW image workflow

Once I decided to keep wait for Aperture 1.11 or later, I decided to see what I could do with iPhoto's 6.02's RAW capability (OS 10.4.6).

Actually, pretty well. I'm pleased. Not only that, but my new workflow is more efficient than my old one. Background details are in this post. Here's what I do:

1. All images are shot RAW. I set white balance to auto and ignore it. With those CR2 RAW files (12 bits of color) I can fix the color balance later.

2. I import all images into my 'intake' iPhoto Library. (I use iPhoto Library Manager to switch libraries, but if you option-click launch iPhoto it will ask for the Library location.)

3. Edit in iPhoto, cropping, adjust color balance, sharpness, etc. (I plan to buy Noise Ninja, that will change my workflow, more later).

4. Export as JPG (this drops color bits to 8, so it's important that the white balance has been fixed.

5. Rename using a A Better Finder Rename (this is not necessary for most.)

6. Import into my main Library, add comments, etc.

7. Put Intake Library images in the trash. Next time I use it I'll empty the trash.

I get significantly better results than I've been getting with in-camera JPG, and this workflow is really quick.

Update 5/3/06: Alas, I've come across a very annoying bug. I set iPhoto to save edited raw as TIFF 16bit/channel. When I did this and exported JPG the metadata was missing. GRRRRRRRRRR. I've turned off the 'save edited RAW as TIFF' option.

USB speakers review

Playlist's review of USB speakers is well done. I ended up liking the description of the Creative TravelSound Notebook 500, but the price is over $80. For that much I'd like to see them first. I like using iPod speakers powered by the USB cord -- less to carry!

(Note these are not USB speakers, they are USB powered! I need them for my iPod, so I don't want to waste money on an unused D/A converter.)

Worst OS X bug: Public and Shared folders

I like OS X, but there are some bad bugs. This one is the worst I know of in 10.4.6 -- because it's not even recognized and it disables major functionality (Caveat - maybe something's broken in my system):

Shared Folders and Public Folders

Use Shared folders and Public folders to share information with other users of your computer.

The Shared folder is located in the Users folder (where your home folder is located). The Shared folder is set up with read and write permissions so that all users can open files in and copy files to this folder.

The Public folder is located in your home folder. It is set up with read only permissions that allow others to see and copy its contents. The Public folder also contains a Drop Box folder where other users can copy files but cannot see the Drop Box folder contents.

Frequently, if not always, when I drag folders into my Shared Folder or Public Folder they retain the permissions they had on my desktop. That means others can't read or write them. These folders should have a 'rewrite on drop' behavior that would set permissions. On my system they don't. I have to set them by hand.

I run as a non-admin user. It's the only way to go, running as admin is asking for bad trouble. I wonder if admin users don't see this bug.