> Pardon me, but this is another one of my soapbox topics: yes, you can use
> GMT, but the timezone offset is anything but trivial. It changes
true. but if about 4 specific conversion APIs are implemented (and
implemented correctly) then it does become pretty straightforward and
simple.
> However, IMO a poor universal-time implementation (with limited DST
> support, among other things) is more troublesome then no GMT at all.
i sure agree with that!!!
> (Also, note the difficulties involved with setting up an appointment book
> to properly use universal- and local-time. Should appointments stick to
> the same universal time, or should they refer to local time? If I'm
> setting up an appointment to meet somebody at Noon on the other coast,
> then local time is appropriate. But it's a different matter if I need to
> call the boss at 2:00 PM, his time.)
look at Microsoft Outlook's calendar view. they've got a reasonable
solution, which is to show two timebars on the left (or right, if Bidi is
turned on, of course) -- one for your primary time zone, and one for your
secondary time zone, which you can quickly and easily set to whatever time
zone you wish. then you see both, side by side, and and can easily schedule
the meeting or appointment at the correct time.
a Palm device has limited screen real estate, so that may be a poor design
for a handheld device, but the point is that it's not an insurmountable
problem.
