with your vanilla NSImageView…

referring to an image file within an Xcode project…

Holy Cow! An Acorn file? Does that mean I can use Acorn files directly in Interface Builder 3? Does that mean you’ve written an NSCustomImageRep that understands the Acorn file format? Does that mean I can use Acorn files directly in my Cocoa projects? And that means I no longer have to keep exporting these bloody files as pngs so I can use them in Cocoa, right? Will this give rixstep some ammunition to go apeshit insane about?

Yes! Yes!! Yes!!! Yes!!!! Yes!!!!! Almost certainly.

Not only does Gus Mueller generously provide details about the Acorn file format, he has even released the source code to his Acorn Quicklook plugin. This gives me everything I need to convince NSImage to load Acorn files.

You might well be asking yourself why. I was getting annoyed with having to constantly keep exporting original Acorn images as pngs or TIFFs so I could use them in Xcode. I’m prototyping a new application that uses a lot of custom UI elements. These elements are made up of one or more pngs, some of which needed a lot of tweaking and attention to detail to get right. Acorn is perfect for UI work (although it needs more than 2000% zoom! cough) but having to export as png (or another format that Cocoa understands natively) and manage two sets of images (original Acorn, exported png) was turning into a pain.

I’ve taken Gus’ QuickLook code and wrapped a small NSCustomImageRep around it. Very small. I’ve repackaged it up as a Framework so you can refer to it from an Interface Builder 3 plugin. This gives you the ability to do this:

[NSImage imageNamed:@"IAmAnAcornFile"];

You should be able to use Acorn files anywhere an NSImage is used. Just embed your Acorn files in your XCode project resources and refer to them by name in your NIBs or in code.

I’ve put the code on my public googlecode.com subversion repository.

I’m currently on the fence about whether it is a good idea or not to ship your application with Acorn images. It certainly makes sense to me to use them during the interface design stage of application development. Once the user interface churn settles down I should be able to finalize the images and convert them to pngs or whatever (keeping the originals of course).

A best of both worlds solution might be to make a little command line tool that can convert Acorn files:

#!/usr/bin/python
from AcornImage import *
# Everything else is an exercise for the reader.

And then automatically convert from Acorn to whatever during the Xcode build process. I might investigate this technique at a later date. But for now – have at it.

The software that comes with the SpaceNavigator is functional, but like a lot of hardware related software is rough around the edges. You can provide customised settings for specific applications or use global settings. You can set up macros to fire when either of the SpaceNavigator’s two buttons are pressed. Understandibly the SpaceNavigator will not appear to applications as a standard input device, so 3Dconnexion provide an API to allow 3rd party developers to use the device. This opens up a host of opportunities for 3rd party developers. The Space Navigator could be used in third-party applications as a jog wheel, kind of like the Griffin Powermate and also as a 2D scroll wheel at the same time.

This leads me onto Acorn, Acorn is Gus Mueller’s newest application. It is an awesome 2D image editor, with a healthy list of features. I consider it to be a “Photoshop for the rest of us”, and has quickly become my image editor of choice. Like Gus’ VoodooPad, Acorn also supports a plug-in architecture. This allow developers to extend the applications in ways Gus wouldn’t have dreamt of (although considering Gus wrote FlyGesture I’m sure he has some pretty funky dreams). I’ve created a plug-in for Acorn that uses the SpaceNavigator API to zoom and scroll around the image you’re editing. Rotating the SpaceNavigator causes the image to rotate (using the CoreImage affine transformation filter). This just touches the surface of the cool things you can do with the SpaceNavigator and an application that supports plug-ins.

Now for the money shots, two movies of the plug-in in action:

Source code for the plug-in is on my Google public repository link, I’ve also written a Cocoa wrapper for the 3Dconnextion API (required by the Acorn plug-in): link. My Cocoa wrapper provides a much simpler interface to the device, and also provides more functionality (such as emulating a scroll wheel). I’ll be working on the wrapper more in the future.

All this code is a work in progress and you will probably need to massage the Xcode project to get it to compile. You’ll also need the 3Dconnexion API (and of course a SpaceController).

And hey look – I’m blogging again!

Update: I got daringfireballed, so I’ve moved the movies onto youtube – quality sucks, but now the server seems responsive again. Links to source code fixed.

Update: Movies now on Amazon S3. Youtube quality sucks so much. (videos still on Youtube here and here).