codahale.com٭blog

Coda Hale lives in Berkeley, CA, where he writes about Ruby on Rails, usability, web design and development, and the occasional bit about bicycles.

Reasons to wear a helmet #32,732

Craig’s List SF: Bike accident near Haight and Fillmore - Looking for Witnesses

I was out Saurday morning having a ride through the park and was on my way home. I usually head down Oak and then turn right on Scott. I remember being on Oak crossing Divisadero but that’s the last thing I remember until waking up in the SF General trauma unit a few hours later.

A good samaritan called 911, which probably saved my life. He or she also called my partner by playing cell phone speed dial roulette. My patner’s being there during the ordeal brought me a huge amount of comfort.

The man or woman who saw this person broken and bleeding on the street had the courage not only to call 911 but also to call their loved ones to let them know what had just happened. People have a tendency to stop and gawk during misfortune, and it’s heartening to know that there are people who will stop, who will take responsibility, and who will help a total stranger.

There’s also something incredibly sad about a person separated from their memories. I’ve had the good fortune to avoid serious head injuries (thank you, Bell), but several of my friends have been basically born anew in emergency rooms, with hours-long disconnects in their life. It’s a very scary thought: one quick thump to the hippocampus and you, as a person with a continuous personality, cease to exist for a few hours.

I sincerely hope this person finds out both what happened to them and who helped them out. Mysterious good samaritan, the next pint’s on me.

Comments Off

BloglinesReader v0.1

I’m pleased to announce the first release of BloglinesReader, a new WordPress plugin. It allows you to display your Bloglines feeds on your WordPress blog, formatted exactly how you want them. It also caches that data, so it doesn’t take forever to display your page (and both your bandwidth quota and the Bloglines servers stay safe).

Check it out: BloglinesReader v0.1

A lot of credit goes to my friend, Peter Dolan, who worked on this plugin first and talked me down from making it Ajax-y (”Why does it need Ajax?” “Well… umm… man, just check out Dojo!” “Yeah, but why does it need Ajax?”). He’d be the one making this plugin, but he’s got a day job.

3 comments »

Microsoft vs. The Menu

From Coding Horror, On The Death Of The Main Menu:

UI innovations in Office tend to be rapidly adopted by Microsoft across their entire product line. Not only there, but in third party applications and even other operating systems. Remember the toolbar? That was unknown until it debuted in Word in the early 90’s**. Now it’s ubiquitous. The “ribbon” is a similar paradigm shift. Eventually we’ll all be using these tabbed palettes with nary a drop-down menu in sight. I expect the traditional WIMP main menu to go the way of the dodo soon after the release of Vista and Office 12 in 2006.

But is this a good thing? As others have noted, the impetus behind this UI development is feature creep. Also, it does have a vestigial menu, to which all file-oriented commands have been relagated (which I think supports my contention that Microsoft simply forgot where Apple’s menus were). At this point, that strikes me more as an “Etc.” category than a well-thought-out design choice. Users will still have to think about whether or not a particular command is “file-oriented” or not.

I’d prefer an all-or-nothing approach: add a “File” tab, and make a permanent 32×32 Save button on the left of the ribbon strip.

One of the things that has always prevented developers from implementing Office features in non-Office products has been Microsoft’s reluctance to share. If developers wanted Office XP-esque menus, they had to implement that functionality themselves. The most Microsoft provided you with was the CoolBar, upon which Internet Explorer 5 was based. Hopefully Microsoft realizes that UI widgets have a network utility, and will release a .NET library for the Ribbon, but I’m not holding my breath.

Comments Off

Office 12 & the Ribbon: What’s wrong with modality?

Screenshots of Office 12 have surfaced, and while it’s been in need of some serious refactoring, I’m not entirely convinced.

Screenshot of Word 12

Yes, I know–it’s all beta, bound to change, etc. etc. But look at this Word 12 window and answer me this: how do I save the changes I just made? It took me a while to find it, but it’s the tiny little button on the right of the tiny little File menu in the upper-left-hand side. Do people really need a 40×40 pixel button for Apply Heading 3, but not for Save?

More importantly, Jensen Harris says:

Something we’ve known from usability tests for several years now is that most people don’t click on an unlabeled 16×16 icon. Sure, Bold and Italic and Center and a few others get a lot of clicks, but the curve falls off after the first 8 or so. As a result, we try to label every command in the Ribbon. We are also upgrading the overall iconography of the product (something that’s not reflected in the screenshots you’re seeing), but even a big, beautiful icon can’t help you find a command as well as that icon + the word “Margins.”

Okay, so users will be able to fiddle with margins easily, but the Save button remains an enigmatic little floppy disk next to the minuscule File menu? Odd priorities. I’d prefer a Fitt’s-compatible toolbar button, because most people haven’t internalized the keyboard commands, and the visibility bantustan that is the new File menu doesn’t seem like a good place to hide a click target most people will use often.

I’m heartened to see that the monstrosity of toolbars has been reduced somewhat, but I’m still suspicious that a mere context menu away lies a vast sea of inscrutable toolbars, featuring such useful items as a goddamn web browser. The tabbish-looking bits up top strike me as an odd setup, especially since they’re not grammatically parallel. We get two nice action verbs–Write and Insert–and then we hit a spate of nouns–Page Layout, References (?), and Mailings (?)–after which a nice verb–Review–and back for a noun–Developer. Are these things I’m doing, things I’m working with, or things I am?

I had two impressions regarding the ribbon. First, the Insert tab is a huge win. I love the idea of being able to see what changes you’re about to make to a document, and the addition of thumbnails provides an easily-scannable Gestalt; the user stays in the realm of visual changes, and doesn’t have to alternate between parsing jargon (”Insert AutoText,” or “Table AutoFormat”) and checking the document’s layout. The addition of useful templates (or “Themes,” or whatever the hell they’re called) will mean that most people will become capable of elegantly formatting a document.

My second impression was that in their effort to make Office 12 “modeless” Microsoft has erased the difference between browsing possible actions and performing them: when a user selects the Font dropdown in Word, the document automatically begins changing the font based on their mouseover actions. That strikes me as problematic for two reasons. First, without any visual indicator of whether or not a change is committed (besides, I suppose, seeing if the document changes when you mouse over it), you’ll find people becoming very cautious about making changes (e.g., not selecting a font until they know exactly which font they want) or attempting to “undo” the preview (e.g., re-selecting the old font, or hitting Undo with the Font dropdown engaged).

The reason for this is that the dropdown widget does not have clearly defined modes. When one clicks on a dropdown, how does one get out of the dropdown? Click somewhere else? Press escape? Unlike, say, an edit box, a dropdown’s modal status is ambiguous, and there are no clearly understood mores for its behavior. The alternative, however, does not entail a return to the dialog box hell that Microsoft has been building for the past decade.

I have two suggestions for how to make the dropdowns less confusing. First, move the previewing functionality into the dropdown control. The thumbnails in the dropdown can be rendered thumbnails of potential changes, further improving the “menu of choices” paradigm that Microsoft has refined. For example, the font dropdown could display a chunk of the selected text in the typeface for that entry. For larger changes, a mouseover popup hint could be displayed with a larger thumbnail of what that change would look like. Finally, the mode of the dropdown controls needs to be clarified for the user. A small close or cancel button, like Apple’s small, gray “X” in-field buttons, would provide the user with a clear action to drop out of the dropdown mode.

Hopefully, Microsoft has pulled back some of its previous boo-boos, and focused more on making the ordinary easy and the extraordinary possible. And for the love of all that is holy, don’t make it a web browser, too.

Comments Off

Live searching done right…ish

From Library clips:

Basically it is a search box for your site, that auto-suggests search terms as you type…these suggested search terms are actually subject terms based on a thesaurus or lexicon that you have programmed into your LookAhead site search tool.
If you don’t have a controlled vocabulary to import into the tool, they also have a service called Lex-It which will generate a lexicon for you (obviously not as effective as human indexing or thesaurus construction).

Check it out.

It’s exactly what I was talking about. Only really, really clunky. Really clunky.

So who’s the WordPress wiseguy who’s going to one-up this for free?

Comments Off