Editing Task:PIM

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 116: Line 116:
#** I've booked a flight from Auckland, New Zealand, to Los Angeles.  It leaves on Monday at 17:30 New Zealand time, and arrives at 11:45 the same day LA time.  Notice that it arrives before it leaves - the UI shouldn't barf at this!  I want to email this appointment to a friend as an iCal file so that he can pick me up at the airport.
#** I've booked a flight from Auckland, New Zealand, to Los Angeles.  It leaves on Monday at 17:30 New Zealand time, and arrives at 11:45 the same day LA time.  Notice that it arrives before it leaves - the UI shouldn't barf at this!  I want to email this appointment to a friend as an iCal file so that he can pick me up at the airport.
#** I work in London, but I'll be in New York for three days from next Tuesday.  I schedule an automatic timezone change for 13:00 that day.  There's a time difference of 5 hours, so next Tuesday is shown as having 29 hours, with the hours 08:00 to 13:00 appearing twice.  For the three days I'm in New York, the calendar shows New York time, for the days before and after London time.  That way I can, right now, add appointments in both London and New York, without having to calculate timezone offsets in my head every time.
#** I work in London, but I'll be in New York for three days from next Tuesday.  I schedule an automatic timezone change for 13:00 that day.  There's a time difference of 5 hours, so next Tuesday is shown as having 29 hours, with the hours 08:00 to 13:00 appearing twice.  For the three days I'm in New York, the calendar shows New York time, for the days before and after London time.  That way I can, right now, add appointments in both London and New York, without having to calculate timezone offsets in my head every time.
-
#*** Is it really necessary for Tuesday to be shown as having 29 hours? It would seem better just to have the UI allow you to change the time zone as required. Having 29 hours in the same day due to a transit raises many issues that might not be worth the development cost of dealing with (even dealing with daylight savings time adjustments correctly raises so many issues that most calendaring applications do not deal with it correctly, or even at all). Consider this:
 
-
#**** Taking a trip to just the other side of the date line may result in arriving the day before you leave. This cannot be dealt with using a longer or shorter day alone (although it could be dealt with by two duplicated short days, however the SYD-LAX case could also be dealt with by a single duplicated short day)
 
-
#**** In a multi-day view there should be some synchronisation between the times on the multi-day view. I have yet to see a published calendaring application that does this correctly for the daylight savings case. Doing so for a time zone change due to travel would result in a lot of extra blank space on the screen.
 
-
#**** How would you propose to deal with recurring appointments intersecting the transition? (This is a problem for daylight savings transitions too, but would be worse in this case).
 
-
#**** Having said all that this is not impossible. It could be mostly dealt with by including an internal (to the application) time zone that has additional adjustments (although going backwards a day could not be), but see below.
 
-
#**** Consider an East Coast business person with the trip set out below. You have four transitions in the one day (including the daylight savings to standard time transition in the morning). Reading the single day view is somewhat of a challenge because there are multiple duplicate time spans, and some of them do not occur on the hour, requiring additional horizontal lines to mark the time zone transition. The days before and after need multiple transition periods (in a multi-day view) where a gap is displayed in the day (so as to attempt to line up "correctly" with this day).
 
-
#***** On the day that daylight savings ends, start in New York City at 6:00am (ExT) on UA7660.
 
-
#***** Arrive in Chicago at 11:05am (CxT).
 
-
#***** Conduct a meeting at the airport from 12:00pm to 1:00pm. Yes, it is Sunday, but our business person is an orthodox Jew, so his Sabbath was the day before and conducting business on a Sunday seems a perfectly natural thing for him to do.
 
-
#***** Leave Chicago at 2:46pm on UA220.
 
-
#***** Arrive in Denver at 4:24pm (MxT).
 
-
#***** Conduct a meeting at the airport from 5:00pm to 5:30pm.
 
-
#***** Leave Denver at 6:05pm on UA498
 
-
#***** Arrive in LA at 7:32pm (PxT)
 
-
#***** (Amazingly, on this day, all the flights depart and arrive precisely on time).
 
=== Address Book ===
=== Address Book ===

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)