<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28">
<TITLE>Re: idea: World Clock</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Speaking as someone who travels (a _lot_) widespread and configurable<BR>
support for time zones would be a very attractive feature. For example, if<BR>
there's a portion of the status bar (or equivalent) that's<BR>
user-configurable, being able to throw a second widget or gadget or whatever<BR>
in there to display the time in a second timezone would be a nice feature.<BR>
<BR>
(OT: R. Buckminster Fuller had the habit of wearing three watches when he<BR>
was on lecture tours or otherwise traveling: one for where he'd been, one<BR>
for where he was going, and one for the time at his home...)<BR>
<BR>
Multiple timezone support on Microsoft's current mobile OS's is horrific:<BR>
you basically have to dig down through the settings to get to a pop-up menu<BR>
item which, monolithically, transmutes everything on the system to an<BR>
alternate timezone, at which point you can back all the way out and enter<BR>
your appointment, say, in the zone you want. Then you have to deep-dive<BR>
through the settings again to change it back. There's no supplied world<BR>
clock application. Outlook desktop support is laughable as well, in<BR>
different ways.<BR>
<BR>
ACCESS' Garnet OS (nee "Palm OS") is much better--you can create<BR>
appointments in their native timezones, and there's a world clock<BR>
included--but still not quite as good as it could be.<BR>
<BR>
On 1/29/07 10:27 AM, "Andrew Turner" <ajturner@highearthorbit.com> wrote:<BR>
><BR>
> Well, what if you just entered the phone number - based on the country<BR>
> code & region/area code, the time is displayed at that location.<BR>
<BR>
That's a nice idea.<BR>
<BR>
> Or when you go to your address book and show a user, it shows the time<BR>
> for that person.<BR>
<BR>
Also a good idea, but it should be configurable (as should contact display<BR>
in general, ideally). With limited screen real estate, you may not be able<BR>
to (or want to) display all of a fully populated contact record, so<BR>
configuring the display, ideally on a per-record basis, is a plus...<BR>
<BR>
> And while you mention it - re: Alarms, the *best* interface feature<BR>
> for an alarm I've ever seen is on my current mobile. After you set the<BR>
> alarm, it confirms by saying, "Alarm will ring in 8h 40m". That is<BR>
> such a comfortable feeling to confirm the alarm is set right (that<BR>
> it's not for PM by saying 20h ;)<BR>
<BR>
See, that's an excellent idea. If you can get confirmation of something in<BR>
an indirect or secondary way, that's a really good validation of the<BR>
input...<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>