I believe Bryan and Jeffrey have the correct interpretation.
On Sep 7, 2006, at 5:32 PM, Bryan Stearns wrote:
I think this problem could be interpreted differently: the invite
specified a specific time and timezone (say, 22:00Z), but we stored
the event using a floating timezone (22:00 floating). As I
interpret the design intention, we should instead have preserved
the event's timezone as GMT (causing it to appear in the 2:00PM
spot, but labeled "10:00 PM GMT"). (I think this design could be
improved upon: we could decide that GMT is less friendly, and
convert events to the local system's timezone on import if their
timezone is GMT, whether the timezone preference is on or off.)
...Bryan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
