Archive | June, 2009

28 June 2009 ~ 0 Comments

Lightroom Tip #1 – Adjusting Time Zones

Halfway through our vacation in Asia, my wife realized we hadn’t reset the time zone in either of our cameras.  We caught it in time for Vietnam and all of our pictures were stamped correctly.  However we were left with hundreds of images taken in Hong Kong stamped with San Francisco’s time!  Fortunately, this is a snap in Lightroom.

First unfold the Metadata panel in the Library module, with the Default metadata set.

Second, locate the Capture Time (it’s about halfway down) and click the Edit Capture Time button.  The capture time is shown as <mixed> because I have multiple images selected.

The Edit Capture Time window appears:

Select the second option and select the appropriate time zone modifier.

If you’re traveling to the family reunion in Ohio, it’s a straightforward conversion from Pacific to Eastern (Eastern is 3 hours ahead).  When you’re traveling halfway around the world, it’s not quite as obvious.

So how did I arrive at +16?  To get from PST to HKT, you need to fast-forward 16 hours.

  • Pacific Standard Time (PST) is UTC-8
  • Hong Kong Time (HKT) is UTC+8.
  • -8 + ? = +8.
  • ? = 16.

I realize this dialog is doing double or triple duty, allowing you to modify the time in various ways although I don’t understand the inflection.  How many times do you want to modify the capture time to a specific time, especially in batch selection?

If you’re selecting the “Time Zone Adjust” option, where are the time zones?  Or even better, a map like when you choose your time zone in the Windows or OS X date/time settings?  Really, that’s what time zone selection is – a poor man’s “Where I am” and “Where I was”.

It’s probably safe to assume the original time was captured in the (incorrect) Lightroom time zone.  We have to make this assumption because the EXIF capture time is ambiguous, as it does not allow recording of the time zone.  There is no reasonable default for the corrected time.

Fixing time zone offset is one of those things I do rarely although when I need to do it, it’s VERY important to me.  Forcing me to do time zone math seems out of place in a streamlined environment like Lightroom.

Continue Reading

26 June 2009 ~ 2 Comments


When selecting paper on the copier at the office:

I know what’s in trays 1 and 2.  Nobody knows what’s in the final tray and I have a strict don’t-ask-don’t-tell policy with the copier after an altercation years ago, that we’re both working hard to forget.  A simple question mark wasn’t enough to convey the copier’s emotion, so two more were called in.  It could be Gremlins?  Or  Zombies?  More likely some advanced form of paper from the future.

Continue Reading

19 June 2009 ~ 0 Comments

Table-Embedded Bar Charts

I periodically visit Google Analytics as it has the interesting responsibility of presenting a massive amount of data in a consumable form.  Given the numbers in the screen capture below, I derive more value out of interpreting their design decisions than I do analyzing my “readership” ;)

You’ll find much discussion on the relative merits of pie charts (or lack thereof).  Keeping the discussion focused on this display, the pie chart and area required to display it consume nearly 50% of the available width.  It’s the main draw here – large and full of bright, vivid colors.  It’s labelled with the percentages (kinda what the wedges should already be tellin’ ya, amirite?), forcing you to map between the various colors and labels several inches away.

If relative comparison is important (it is important for platform support decisions), what if we embedded a bar chart inside the table?

This allows easy comparison between the browsers themselves though I’m unsure if, without first looking at a visit percentage, it would be clear the row color consumes 50% of the table cell.  It may also not be as aesthetically pleasing than the tidy compartmentalization on the first image.  There are benefits to this approach, some of which come simply from choosing to use a bar chart in lieu of a pie chart: better area utilization, avoids having to map swatches/browsers to slices, etc.

Continue Reading

06 June 2009 ~ 0 Comments


Here I am creating a new To Do item.  In the “Date Due” field, watch what happens when I type “Monday” and press ENTER.  Remember that today is Saturday, June 6, 2009.

M-o-n-d-a-y <enter> June 8, 2009 <enter> <committed>.

Would anyone have been surprised if instead, any one of the following occurred?

  • A popup chastised me for “Invalid format!”
  • A popup chastised me for “Invalid format! Please use DD/MM/YYYY!”
  • A date picker appeared, with the next months’ worth of Mondays highlighted, expressing its confusion over my ambiguity.
  • A confirmation dialog appeared asking me if I really meant July 8th, 2009.  Yes/No/Cancel?

Probably not.

Now I’m not saying this free-form entry field for dates is a usability needle-mover, just that I was pleasantly surprised that when I said Monday, Apple Mail assumed I meant the following Monday.  By the way, Outlook 2007 makes the same assumption in the Tasks view.

As designers and developers, we need to have this courage of our convictions to say “Yes, this is a reasonable interpretation of that input” (tested, backed by research, etc.!), giving our solutions the same social presence as that had by a helpful assistant.  This means making reasonable assumptions when told what to do, and not harassing our users with needless confirmation.  In 2009, with the availability and power of development frameworks, there’s no excuse for it.

Continue Reading

04 June 2009 ~ 0 Comments

Social Presence

In January of this year, Alan Cooper was interviewed over at Info Queue:

I wrote a book called “About Face” in 1995 and I wrote a book called “The Inmates Are Running the Asylum” in 1999 and both of these books were pluming this idea of how does software get constructed and how can it be designed well from the point of view of how it behaves in the world, as though it were a person with a social presence.

What I’m seeing more of these days is increasingly complex software with more verbose labeling and explanatory passages.  It’s not surprising given Cooper’s impact on design and that others like Luke Wroblewski in Web Form Design suggest something similar:

  • Think about how a form can be organized as a conversation instead of an interrogation.
  • Clear, conversational language can clear up potential ambiguity.

Take the advanced administrative interface for Netgear’s ReadyNAS Duo network storage device.

Previous iterations of interfaces like these would have made do with the terse, less expository text adjancent the combo box.  With the conversational tone and actionable quality of the additional text, boneheads like myself have all the information they need to know whether or not to enable this feature.  For interfaces like this used once in a blue moon, learning is irrelevant.  Infrequent use means that you re-learn the entire thing from scratch each time you use it and this text is a life saver.

What’s great about Netgear’s decision to bold the label is that advanced users can happily scan on by without reading the additional text.  I’m pleasantly surprised by this level of sophistication from a network hardware company.

Continue Reading