January 3rd, 2012
|07:26 am - Calendars and graphic design|
It's not about the artwork - though this year the calendar features the first twelve of "The Seventy Maxims of Maximally Effective Mercenaries" from Howard Tayler's Schlock Mercenary comic, rather than pictures of horses as has been the case the last several years.
This is about the numbers. Or the size and color of them. This calendar reminds me one from a few years ago. Both have small numbers for the dates. That's great if you're up close and need space to write lots of stuff for that date. It's not so great from a distance where you simply want to see the numeric date.
The next year, after the tiny type a while back, I found a calendar I liked with nice big date numbers. But they were various, muted, nearly (if not) pastel colors which also made them harder to read from a distance. And the colors were random. It wasn't "Holidays are red" or "Mondays are blue, Tuesdays are orange,..." Thus no useful information was added but the decoration made the thing less useful than it should have been.
It strikes me as odd that these problems exist. A calendar isn't a new or terrible complex thing. They've been around for a long, long time. One would expect readability from common uses (halfway across a small room doesn't seem to be asking too much) would be one of those well and truly solved problems. Evidently it is not.
 Computing some dates, such as Easter, can be complicated, however.
Current Mood: disappointed
|Date:||January 3rd, 2012 03:48 pm (UTC)|| |
I wrote our business calendar maintenance application at work, so we can set up holidays when we don't want trades to go through, etc.
I remember one year when Microsoft Outlook set up Memorial Day as the 4th Monday in May instead of the last Monday in May, I got some laughs out of that. Me > Microsoft, yay.
Sadly the complex math behind holidays based on lunar cycles (like Good Friday) proved too unreliable. We just use a lookup table for those.
Once upon a time, I was building a clock that was a peripheral to another system. It needed to handle DST, all that kind of thing. It also needed to flag company holidays. That was easy enough - except for one holiday, Good Friday. I looked at what it took to compute it, then sat down with a desk calendar with the rules described in the back and manually computed it for the next 100 years, then made a lookup table.