Beating a Dead Horse

As everyone is well aware, Adobe recently released a beta of Photoshop CS3, complete with new icons. The new application icon is so stripped down and plain I had initially assumed it was a placeholder for something permanent in the final version — that this was merely a stopgap icon for the beta release. This is, it turns out, not the case. This is it. Put a fork in it. It's done.

Not only is this the final icon for Photoshop CS3, but Adobe has redesigned the entire CS3 application suite around the same concept. People all over the Mac web are weighing in on the matter, and they're generally sitting in one of two camps: They either love it or they hate it. Here are some links to the ongoing commentary:
John Nack
Veerle
Jason Santa Maria
Dave Shea

Personally, I'm on the fence. No, that's not actually completely accurate. Personally, I can see both sides, and in the end I think that the icon redesign sort of breaks even. I think we basically lose as much as we gain between form and functionality with these new icons. And I think that there is another approach that would have worked better than the one taken by Adobe on CS3.

The new CS3 suite icons are all based on the same idea. A colored square with a two-letter identifier that mimics the periodic table of elements. It's a nice concept in a way, especially considering its entire purpose seems to be to unite a vast and sprawling suite of applications. And I think on this level it works. Applications from the Adobe suite will be immediately recognizable as such in the Dock, and telling each application apart shouldn't be too terribly difficult. I even kind of like the sparse, minimal appearance of these new icons.


The Adobe CS3 Icon Set: Confused Yet?
(click image for larger view)

My first problem, though, is that they're not particularly iconic. They're basically text. Or, the thing that's used to identify each application is text. Conceptually, this bothers me a little. The Adobe suite of applications is, for all intents and purposes, visual in nature. It's made for processing imagery moreso than text. These are not text applications, but image editing applications. They're made for visual people working on visual projects. So using text as an identifier seems a strange — maybe even an inappropriate — approach. I can see it for something like the Microsoft Office suite, which does indeed use text-based icons. But for image editing apps it just seems wrong to not use something image-based.

My other complaint, from a practical standpoint, is that text is a much clumsier, more difficult way to identify an application than symbolism. It requires hard looking, reading, something more than a mere glance. Icons are, at their hearts, symbols, and symbols are intuitively easier to grasp than text. Which is the whole reason icons tend to be made from images rather than text in the first place. It's the reason almost everything on a GUI-based interface is a picture rather than (or in addition to) text. Can you imagine a folder on your Desktop that was a big square with the letters "Fo" on it? Imagine an entire OS described this way. I'd guess it'd get a bit trickier to navigate. (Actually, you don't have to imagine it. Just open up the Terminal. It's called the UNIX command-line. And we all know how popular that is with the design crowd.)


Adobe CS3 Apps in the Dock: Imagine an Entire OS Like This
(image stolen from Dave Shea)
(click image for larger view)

It seems to me that there is a better approach for Adobe — one that could unify the suite, while at the same time keeping in step with a more purely visual approach. We can see traces of it in the one exception to the rule with the new suite icons: Acrobat. Acrobat's icon uses the same sparse approach as the other applications — an application identifier on a colored square — but instead of using text as an identifier, it uses the well-known Acrobat icon image — that weird little loopy-loop we all know so well, and that we immediately associate with Acrobat — in the center of the colored square. Veerle (who likes the new icons) had this to say about it:

You might wonder why Acrobat Reader hasn't "Ar" as icon or "Pd" or something, just to take the same line with the rest of the products. The curvy triangle is so well known that it's obvious they kept using it for the icon. I think if the other applications had a similar icon over the years, they would have done the same. Since there are none they decided to use a two-letter mnemonic 'nickname' system as their primary identifier.

And therein lies both the problem and the solution. I think the best approach Adobe could take — both from a conceptual and a practical standpoint — would be to actually create memorable, iconic symbols for each of their applications. Thus far they have not done so, and choosing instead to represent their apps with plain two-letter text identifiers just seems a little cheap, lazy and ineffectual. Why doesn't Photoshop have such a memorable symbol associated with its product line after all these years? Or Illustrator? By now they really should. Maybe it's time to start working on these.

Acrobat Icon: Why Doesn't Photoshop Have a Symbol?
(click image for larger view)

Past Adobe icons were visual in nature, but suffered from a lack of readability in the Dock. They were pretty, but they looked too similar and their imagery made no sense whatsoever — form over function. But this new set will suffer from the same sort of unreadability. They're less visual, less image-based, but still very similar. And they'll now require yo u to read them and decipher their two-letter code. Still, they'll be somewhat easier to discern from one another (since the letters at least correspond to something in the real world, i.e. the application name, whereas the previous icons used images that were completely arbitrary and nonsensical) and a bit more unified as a group, though arguably less attractive — function over form. It's a tradeoff. But one that, again, we break even on with the new icon set. This new icon set offers no functional or aesthetic advantages over its older counterpart. Or what advantages it may offer are offset by disadvantages it spawns. Creating real symbols that speak somehow to the nature of the application — like they've done in some respects with Acrobat — for the rest of the suite would solve the problems of both form and function: Icons created from these symbols would be both more beautiful and more functional. You would think a big, giant, design-based software company would get this. But so far, they seem to have missed the boat.

I don't hate the new icons. I actually think they look kind of cool in a minimal sort of way. But they're just not particularly visually interesting, nor will they add much functionality over their predecessors. So I can't say I'm overly enamored with them either. For a major change to a major application suite — one that has a lot of folks up in arms — I have to say, I'm feeling quite... neutral on the matter. And that's a little disappointing in and of itself. I wish I were feeling excited.

Photoshop CS3 Does Video

Everyone's talking about Adobe's Photoshop CS3 Beta release. In a day and age when paid betas are all the rage among smaller developers, a big developer releasing a free (though time-limited) beta of a flagship program is exciting in and of itself. But this beta has legs. It's good stuff. I'll go over some of the more significant features that everyone's buzzing about. But I also want to spend a little time talking about some things that no one in the mainstream press seems particularly interested in, 'cause, you know, I'm funny like that. And 'cause there are some real gems, from my particular perspective.

The Installer
I wanted to briefly mention the installer for Photoshop CS3, because it's pretty nice, particularly in contrast to the Acrobat Reader installer. No, it's not an Apple Installer, but it does offer a great deal of control (and some features not available from Apple Installers), and from a systems perspective, this is wonderful. Most notably, the Photoshop CS3 installer (called Setup.app) contains an uninstaller. Awesome! Yes, it may be hard to believe, but there have been times I actually wanted to completely uninstall Photoshop, and I couldn't. Now I can.


Adobe Photoshop CS3 Beta: Uninstall or Reinstall
(click image for larger view)

The uninstaller even gives you the option to delete application preferences. Wow. That's pretty thorough.


Adobe Photoshop CS3 Beta: Uninstalling Components
(click image for larger view)

Secondly, the installer allows you to choose which Photoshop components get installed, or to reinstall or uninstall specific components of the suite. Don't use Camera RAW? Don't use Bridge? Fine. Don't install 'em. Change your mind? Fine. Go reinstall 'em.


Adobe Photoshop CS3 Beta: Reinstalling Components
(click image for larger view)

I can't believe I'm saying this, but Adobe has really gotten this installer right. If I can't have drag-'n'-drop or package installers, then this is what I want. The only problem is, I'm pretty sure it won't work with Apple Remote Desktop (but then it never did anyway). Otherwise, I'm pleased as punch.

One other thing to note about the beta installation: Adobe requires you to produce a valid Photoshop CS2, Creative Suite 2, Production Studio, Adobe Web Bundle, or Adobe Video Bundle serial number to use the beta for longer than the 2-day trial period. Supply this serial number and you'll be given a new serial number for the beta. The new serial number can be used to activate the software until the beta expires, ostensibly some time around the official release date. The software gets activated online via a connection to Adobe, and it keeps tabs on how many machines you've installed the beta on. The limit is two computers. I installed it on two machines, but then, after installing it on the third I received this alert when trying to activate the software:


Adobe Photoshop CS3 Beta: Too Many Activations
(click image for larger view)

This seems relatively fair to me. The only thing I find somewhat irksome is that we have a 20-seat volume license. So, to my way of thinking, our serial number should be good for 20 installs of the beta. Apparently Adobe feels differently. I also wish I could deactivate machines remotely, via this interface (like you can with iTunes music, for instance). But no, unfortunately I'll have to go over to the machines in question, log in and deactivate them locally. Oh well.

The Icon
The first thing I noticed after installing the Photoshop Beta was the strange, minimal application icon. I kind of like it, but it seems somewhat inappropriate to me that Photoshop — an image editing application that's always had pretty fancy icons — has such a plain one. I'm assuming that this is just the icon they'll use for the beta, and that a more sophisticated icon will come with the shipping version.


Adobe Photoshop CS3 Beta: Minimal Beta Icon
(click image for larger view)

The Hot New Features
One item of significance — in fact, according to the scuttlebutt, it's a big reason the beta was released — is that this is the first version of Photoshop to run natively on Apple's latest Intel hardware. Amazingly, this comes off as a footnote in most of the reviews, overshadowed by the fact that this also happens to be the first major revision of the photo-editing powerhouse to actually be packed with exciting, new and useful features. In fact, after trying it out, it's the first time I've been impressed with an Adobe release other than Lightroom in years. And it's Photoshop, man. Frickin' Photoshop!

One of the most discussed aspects of Photoshop CS3 is the interface, and it's certainly worth a mention here. It's been quite extensive ly overhauled, and yet still feels completely familiar. Everything is right where you'd expect it, but there are numerous productivity enhancements throughout the app. Little touches, really, like a toolbar that is one tool wide, giving you more room for viewing your image. Palettes are more logically (and attractively) presented and unified, instead of floating around all over the place. This seems to be the trend with a number of apps, and if AfterEffects 7 and Lightroom are any indication, Adobe is following it. This is a good thing. I truly hate moving windows and palettes around. And with today's big screens, there should be little need to.


Adobe Photoshop CS3 Beta: Nice Interface Refinements
(click image for larger view)

My one big beef is that there still seems to be no key command to switch between open documents. Almost every other application on the Mac nowadays uses "command- `" to switch between open docs. Yet Photoshop CS3 still not only fails to adhere to this standard, but apparently lacks the ability to switch between open docs with the keyboard at all. This seems like a strange oversight for such a significant interface overhaul. I also wish Adobe would use standard Apple key-commands for things like hiding the app ("command-h" on the Mac, generally) but at least the ability exists to do this from the keyboard, and it's configurable.

Finally, the Refine Edge tool is quite the talk of the town. And for good reason. Anyone who's ever tried to select a color range and then tried to tweak the selection has longed for this tool, which basically allows you to interactively refine the edges of your selections. And it's finally here!


Adobe Photoshop CS3 Beta: Refine Edge
(click image for larger view)

Video (Yes, Video!)
But there's another fantastic new addition to Photoshop CS3, and it's one no one's mentioned, maybe because no one's quite as weird as me: Animation. For years I've wished Photoshop — with it's powerful layering capabilities, selection tools and brushes — could be used as a 2D animation tool. I always wanted to be able to import and draw on video in Photoshop. You could always fake this with ImageReady, which came with basic Quicktime import/export functions and a pretty useful Animation palette, and which I've demoed in my class numerous times. But it was clunky and confusing. ImageReady was not well equipped to deal with large numbers of relatively large images — it became painfully slow — and it lacked WACOM touch-sensitivity and the full range of brushes found in Photoshop. Plus, it was just plain inconvenient to use ImageReady when Photoshop was sitting right there. Well, my wait is finally over. Photoshop CS3 now includes the very same Animation palette formerly found only in ImageReady. It's there, and it works exactly as it did in ImageReady. Only now we get all that Photoshop goodness and the familiar interface we all know and love (or at least are accustomed to). Hooray!


Adobe Photoshop CS3 Beta: Holy Shit! Animation!
(click image for larger view)

There are a few new video-specific features too, though you might not know it from the coverage. There's a "Video and Film" Workspace, for one, which highlights all video-related menubar items and brings forth video-related palettes, including the Animation palette.


Adobe Photoshop CS3 Beta: Video and Film Workspace Highlights
(click image for larger view)

And now, since Photoshop CS3 does video, it only seems appropriate that it should have the ability to preview that video to a monitor, which in fact it now does.


Adobe Photoshop CS3 Beta: Video Preview
(click image for larger view)

All these new video capabilities were a huge surprise to me. And a hugely pleasant one. There was a time when I got pretty excited about new Adobe releases, but it was a long time ago. It's great to see Adobe, once again, release a really compelling version of Photoshop. I'm amazed at how much thought and care they've given "the little things," from the interface to the installer to, of all things, video. And yet they've still managed to keep all the good bits. This version has something for everyone. I, for one, am truly impressed.

UPDATE:
Looks like I was wrong. The new Photoshop CS3 icon featured in the beta is here to stay. Not only that, lots of people are buzzing about it. Personally, my favorite comment on the "issue" so far (I haven't had time to read them all — Help! I'm on dialup!) is one from John Nack:

[Not dismissing your opinion at all, but isn't it nice that in this world, at the end of 2006, it's computer iconography that constitutes our nightmares? We are very lucky to have literacy, intelligence, and leisure enough to give a damn about this stuff. -

-J.]

Totally agree. Still, I've decided to add my voice to the already huge compendium of opinion on the matter.

Backing Up with RsyncX

In an earlier post I talked generally about my backup procedure for large amounts of data. In the post I discussed using RsyncX to back up staff Work drives over a network, as well as my own personal Work drive data, to a spare hard drive. Today I'd like to get a bit more specific.

Installing RsyncX

I do not use, nor do I recommend the version of rsync that ships with Mac OS X 10.4. I've found it, in my own personal tests, to be extremely unreliable, and unreliability is the last thing you want in a backup program. Instead I use — and have been using without issue for years now — RsyncX. RsyncX is a GUI wrapper for a custom-built version of the rsync command that's made to properly deal with HFS+ resource forks. So the first thing you need to do is get RsyncX, which you can do here. To install RsyncX, simply run the installer. This will place the resource-fork-aware version of rsync in /usr/local/bin/. If all you want to do is run rsync from the RsyncX GUI, then you're done, but if you want to run it non-interactively from the command-line — which ultimately we do — you should put the newly installed rsync command in the standard location, which is /usr/bin/.¹ Before you do this, it's always a good idea to make a backup of the OS X version. So:

sudo cp /usr/bin/rsync /usr/bin/rsync-ORIG

sudo cp /usr/local/bin/rsync /usr/bin/rsync

Ah! Much better! Okay. We're ready to roll with local backups.²

Local Backups

Creating local backups with rsync is pretty straightforward. The RsyncX version of the command acts almost exactly like the standard *NIX version, except that it has an option to preserve HFS+ resource forks. This option must be provided if you're interested in preserving said resource forks. Let's take a look at a simple rsync command:

/usr/bin/rsync -a -vv /Volumes/Work/ /Volumes/Backup --eahfs

This command will backup the contents of the Work volume to another volume called Backup. The -a flag stands for "archive" and will simply backup everything that's changed while leaving files that may have been deleted from the source. It's usually what you want. The -vv flag specifies "verbosity" and will print what rsync is doing to standard output. The level of verbosity is variable, so "-v" will give you only basic information, "-vvvv" will give you everything it can. I like "-vv." That's just the right amount of info for me. The next two entries are the source and target directories, Work and Backup. The --eahfs flag is used to tell rsync that you want to preserve resource forks. It only exists in the RsyncX version. Finally, pay close attention to the trailing slash in your source and target paths. The source path contains a trailing slash — meaning we want the command to act on the drive's contents, not the drive itself — whereas the target path contains no trailing slash. Without the trailing slash on the source, a folder called "Work" will be created inside the WorkBackup drive. This trailing slash behavior is standard in *NIX, but it's important to be aware of when writing rsync commands.

That's pretty much it for simple local backups. There are numerous other options to choose from, and you can find out about them by reading the rsync man page.

Network Backups

One of the great things about rsync is its ability to perform operations over a network. This is a big reason I use it at work to back up staff machines. The rsync command can perform network backups over a variety of protocols, most notably SSH. It also can reduce the network traffic these backups require by only copying the changes to files, rather than whole changed files, as well as using compression for network data transfers.

The version of rsync used by the host machine and the client machine must match exactly. So before we proceed, copy rsync to its default location on your client machine. You may want to back up the Mac OS X version on your client as well. If you have root on both machines you can do this remotely on the command line:

ssh -t root@mac01.systemsboy.com 'cp /usr/bin/rsync /usr/bin/rsync-ORIG'

scp /usr/bin/rsync root@mac01.systemsboy.com:/usr/bin/

Backing up over the network isn't too much different or harder than backing up locally. There are just a few more flags you need to supply. But the basic idea is the same. Here's an example:

/usr/bin/rsync -az -vv -e SSH mac01.systemsboy.com:/Volumes/Work/ /Volumes/Backups/mac01 --eahfs

This is pretty similar to our local command. The -a flag is still there, and we've added the -z flag as well, which specifies to use compression for the data (to ease network traffic). We now also have an -e flag which tells rsync that we're running over a network, and an SSH option that specifies the protocol to use for this network connection. Next we have the source, as usual, but this time our source is a computer on our network, which we specify just like we would with any SSH connection — hostname:/Path/To/Volume. Finally, we have the --eahfs flag for preserving resource forks. The easiest thing to do here is to run this as root (either directly or with sudo), which will allow you to sync data owned by users other than yourself.

Unattended Network Backups

Running backups over the network can also be

completely automated and can run transparently in the background even on systems where no user is logged in to the Mac OS X GUI. Doing this over SSH, of course, requires an SSH connection that does not interactively prompt for a password. This can be accomplished by establishing authorized key pairs between host and client. The best resource I've found for learning how to do this is Mike Bombich's page on the subject. He does a better job explaining it than I ever could, so I'll just direct you there for setting up SSH authentication keys. Incidentally, that article is written with rsync in mind, so there are lots of good rsync resources there as well. Go read it now, if you haven't already. Then come back here and I'll tell you what I do.

I'd like to note, at this point, that enabling SSH authentication keys, root accounts and unattended SSH access is a minor security risk. Bombich discusses this on his page to some extent, and I want to reiterate it here. Suffice to say, I would only use this procedure on a trusted, firewalled (or at least NATed) network. Please bear this in mind if you proceed with the following steps. If you're uncomfortable with any of this, or don't fully understand the implications, skip it and stick with local backups, or just run rsync over the network by hand and provide passwords as needed. But this is what I do on our network. It works, and it's not terribly insecure.

Okay, once you have authentication keys set up, you should be able to log into your client machine from your server, as root, without being prompted for a password. If you can't, reread the Bombich article and try again until you get it working. Otherwise, unattended backups will fail. Got it? Great!

I enable the root account on both the host and client systems, which can be done with the NetInfo Manger application in /Applications/Utilities/. I do this because I'm backing up data that is not owned by my admin account, and using root gives me the unfettered access I need. Depending on your situation, this may or may not be necessary. For the following steps, though, it will simplify things immensely if you are root:

su - root

Now, as root, we can run our rsync command, minus the verbosity, since we'll be doing this unattended, and if the keys are set up properly, we should never be prompted for a password:

/usr/bin/rsync -az -e SSH mac01.systemsboy.com:/Volumes/Work/ /Volumes/Backups/mac01 --eahfs

This command can be run either directly from cron on a periodic basis, or it can be placed in a cron-run script. For instance, I have a script that pipes verbose output to a log of all rsync activity for each staff machine I back up. This is handy to check for errors and whatnot, every so often, or if there's ever a problem. Also, my rsync commands are getting a bit unwieldy (as they tend to do) for direct inclusion in a crontab, so having the scripts keeps my crontab clean and readable. Here's a variant, for instance, that directs the output of rsync to a text file, and that uses an exclude flag to prevent certain folders from being backed up:

/usr/bin/rsync -az -vv -e SSH --exclude "Archive" mac01.systemsboy.com:/Volumes/Work/ /Volumes/Backups/mac01 --eahfs > ~/Log/mac01-backup-log.txt

This exclusion flag will prevent backup of anything called "Archive" on the top level of mac01's Work drive. Exclusion in rsync is relative to the source directory being synced. For instance, if I wanted to exclude a folder called "Do Not Backup" inside the "Archive" folder on mac01's Work drive, my rsync command would look like this:

/usr/bin/rsync -az -vv -e SSH --exclude "Archive/Do Not Backup" mac01.systemsboy.com:/Volumes/Work/ /Volumes/Backups/mac01 --eahfs > ~/Log/mac01-backup-log.txt

Mirroring

The above uses of rsync, as I mentioned before, will not delete files from the target that have been deleted from the source. They will only propagate changes that have occurred on the existing files, but will leave deleted files alone. They are semi-non-destuctive in this way, and this is often useful and desirable. Eventually, though, rsync backups will begin to consume a great deal of space, and after a while you may begin to run out. My solution to this is to periodically mirror my sources and targets, which can be easily accomplished with the --delete option. This option will delete any file from the target not found on the source. It does this after all other syncing is complete, so it's fairly safe to use, but it will require enough drive space to do a full sync before it does its thing. Here's our network command from above, only this time using the --delete flag:

/usr/bin/rsync -az -vv -e SSH --exclude "Archive/Do Not Backup" mac01.systemsboy.com:/Volumes/Work//Volumes/Backups/mac01 --delete --eahfs > ~/Log/mac01-backup-log.txt

Typically, I run the straight rsync command every other day or so (though I could probably get away with running it daily). I create the mirror at the end of each month to clear space. I back up about a half dozen machines this way, all from two simple shell scripts (daily and weekly) called by cron.

Conclusion

I realize that this is not a perfect backup solution. But it's pretty good for our needs, given what we can afford. And so far it hasn't failed me yet in four years. That's not a bad track record. Ideally, we'd have more drives and we'd stagger backups in such a way that we always had at least a few days backup available for retrieval. We'd also probably have some sort of backup to a more archival medium, like tape, for more permanent or semi-permanent backups. We'd also probably keep a copy of all this in some offsite, fireproof lock box. I know, I know. But we don't. And we won't. And thank god, 'cause what a pain in the

ass that must be. It'd be a full time job all its own, and not a very fun one. What this solution does offer is a cheap, decent, short-term backup procedure for emergency recovery of catastrophic data loss. Hard drive fails? No trouble. We've got you covered.

Hopefully, though, this all becomes a thing of the past when Leopard's Time Machine debuts. Won't that be the shit?

1. According to the RsyncX documentation, you should not need to do this, because the RsyncX installer changes the command path to its custom location. But if you'll be running the command over the network or as root, you'll either have to change that command path for the root account and on every client, or network backups will fail. It's much easier to simply put the modified version in the default location on each machine.

2. Updates to Mac OS X will almost always overwrite this custom version of rsync. So it's important to remember to replace it whenever you update the system software.

Icons Icons Icons!

Not long ago a fabulous post on doodling appeared at one of the blogs I frequent on a regular basis, Subtraction. Khoi Vihn, the site's author, posted some absolutely lovely doodles he'd made, and I was instantly transported to my note-taking, doodle-drawing grad school days. It was kind of magical, and I really liked that idea for a blog post. And while I've decided I'm way too lazy and busy at the moment to scan my doodles, I did feel TASB could use a splash of the creative. I am, in addition to being a SysAdmin, a visual artist, after all.

Since this site is primarily about systems, it seemed appropriate to focus on an art form specifically related to the computer. And since I dabble in icon creation, and have worked up quite a collection over the years, I've decided to post a little sampler, and talk about my process. Just for a wee change of pace. Just for fun.

This is the first icon I ever made. I labored on this thing for days, trying to get that shiny, translucent, jelly bean look so prevalent on the Mac. Yes. It totally sucks major ass.


My First Icon: It Sucks Major Ass
(click image for larger view)

I quickly outgrew the glossy, candy-coated style — especially once I realized that I sucked at, and didn't enjoy making them — and started developing my own. I have two basic styles. The first one to emerge was a very flat, geometric style. My process is not very elegant, but I've used it for some time now and it works so I stick with it. Basically all the drawing is done in Illustrator. When I get a version I like I simply copy and place it into a 533x533 pixel Photoshop document. Typically, some color correction is required after the transfer. Mainly, the blacks get washed out, so I have a Photoshop action that selects the black range and drops it down to zero. Then the image gets resized to 128x128 pixels. Finally I use IconFactory's IconBuilder 5.1 plug-in (no longer current) for Photoshop to export the image to the icon format. Typically, here I just do a "QuickBuild" (which, unfortunately seems to be missing from later versions of IconBuilder). I don't really worry about creating multiple versions of my icons for different icon sizes and views. I just try to make icons that scale reasonably well. This is for fun after all. I'm not a pro, nor do I aspire to be.


Geometric Icons: Not Quite as Sucky
(click image for larger view)

The second style, and the one I generally prefer to work in nowadays, is more hand-drawn and cartoonish. Still somewhat flat, with some shading but no gradients and far less geometry than the above. These are all done using my trusty WACOM tablet, which I simply adore. Working this way allows me much greater expressiveness through line weight and shape, and through the individuality of my own particular drawing style. Plus it's just way more fun, though it can be a lot more work to get everything looking just right.


Hand-Drawn Icons: My Personal Faves
(click image for larger view)

A lot of these icons were intended as drive icons. I have a few different computers I work on regularly, and I tend to file-share between them a lot. Each has a SysApps partition and Work partition. Labeling each SysApps and Work drive on each system, while being aesthetically pleasing, also has the added advantage of making it very easy to distinguish which SysApps or Work drive I'm accessing at a glance when file-sharing. It's both practical and pretty. (Well, I think so anyway.)


Marx Brothers Icons: I Got Paid!
(click image for larger view)

Recently someone took notice of some of the icons I'd used in he lab and commissioned me to make him a custom set based on the Marx Brothers, he being a big Marx brothers fan and all. We worked together to figure out what he would like, and he gave me all kinds of resources and suggestions for the project, but I had a lot of freedom. It was the first and only job I've ever had like that. The first time I've ever had to create something visual for someone other than myself, but he was very cool to work with, I liked the challenge, and it was a really fun process. Basically I worked on it in my spare time, and I'd show him progress sketches every so often. He'd give me feedback and I'd go work on them some more and show him the results when things got good. The thing I liked best about the project was this outside feedback. It really kept me from being lazy. And in the end the icons were far more polished than I think they ever would have been had I just been working on them alone. I'm kind if a loner in a lot of ways, both professionally and personally. Not a big collaborator. But every now and then it's great to have some outside eyes. Some second opinions.

Which, now that I think about it, may be the whole reason to have a blog.

Scripts Part 6: Archiver

A hint on MacOSXHints yesterday discussed using tar to create backups in Mac OS X. The poster was frustrated with the OS X-bundled version of the zip command, and confused by the way the Finder creates .zip files. Indeed, the Finder does not use the zip command to create its .zip files, and indeed it is confusing. And, more importantly, the zip command does not preserve all-impotant Mac OS X resource forks.

After reading this hint I was reminded of a script I wrote a while back based on yet another MacOSXHints hint that uses ditto to create Finder-like .zip archives. So it seemed like a good time to post the script here and add it to the waning ScriptSharing series.

So here it is: my Archive script. It will both archive and expand folders or files using ditto, and it places these archives on the Desktop.

Archiver Script
See the code