It seems like what's actually needed is the ability to assign
multiple timezones to the same calendar canvas. Monday I'm in PST,
Tuesday after 3PM I'm in EST. Otherwise, separate timezones for start
and end times of a flight could result in a flight arriving before it
departs on the calendar (which persists in a single timezone).
This is another use case for a Floating calendar which is agnostic to timezone.
Mimi
Thanks Bear!
Got a good laugh (as always with Joel on Software) but the user
scenario he describes is really worth checking and pondering.
This idea of different TZ for the start and end date was actually
mentioned last year by Arel (one of our summer intern) for precisely
this scenario (plane scheduling). It's a very valid and common need
(well, may be not flying West-East across the international day
change line but just flying coast to coast in the US will be a pain
to enter in any calendar...).
I also like the way he drives the Print requirement.
Cheers,
- Philippe
Mike Taylor wrote:
http://www.joelonsoftware.com/items/2006/02/08.html
---
Bear
Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org
[EMAIL PROTECTED]
http://code-bear.com
PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
------------------------------------------------------------------------
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
