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 81: Line 81:
#** '''Support CalDAV''' - [[User:boxofsnoo|boxofsnoo]]
#** '''Support CalDAV''' - [[User:boxofsnoo|boxofsnoo]]
#** Support '''synching over bluetooth''' and wlan - [[User:asys3|asys3]]
#** Support '''synching over bluetooth''' and wlan - [[User:asys3|asys3]]
-
#** Support synching with OpenSync to allow syncing with widest range of other applications (including kdepim and evolution) - [[User:gcobb|gcobb]]
 
-
#** Support direct syncing with Outlook (over BT, USB, WiFi) -- it may be evil but it is by far the dominant requirement for anyone in business - [[User:gcobb|gcobb]]
 
#* Interaction with email program - allow to open a mail with a specific date attached - [[User:asys3|asys3]]
#* Interaction with email program - allow to open a mail with a specific date attached - [[User:asys3|asys3]]
#** Better yet, copy the mail body into the notes field of the event. - [[User:boxofsnoo|boxofsnoo]]
#** Better yet, copy the mail body into the notes field of the event. - [[User:boxofsnoo|boxofsnoo]]
-
#** And send and receive meeting requests (iCalendar format) by email, with Accept, Decline, Tentative responses - [[User:gcobb|gcobb]]
 
#* Monthly grid view
#* Monthly grid view
#** Multi-day events - [[User:boxofsnoo|boxofsnoo]]
#** Multi-day events - [[User:boxofsnoo|boxofsnoo]]
Line 100: Line 97:
#** An individual event's time/date can be adjusted so that the other occurences does not change (decoupling)
#** An individual event's time/date can be adjusted so that the other occurences does not change (decoupling)
#** An individual event can be renamed without changing the rest of the occurences (decoupling)
#** An individual event can be renamed without changing the rest of the occurences (decoupling)
-
#* Alarms should integrate with the alarm daemon (allow alarms to wake up device when off, etc.) --[[User:davidgro|davidgro]] 11:10, 10 February 2009 (UTC)
 
#* Types of repeating events - [[User:tor|tor]] (copied from an ITT posting about Palm repeating events)
#* Types of repeating events - [[User:tor|tor]] (copied from an ITT posting about Palm repeating events)
#** Daily until..
#** Daily until..
Line 112: Line 108:
#** Every N month(s) until date (or forever), e.g. the 4th Thursday of that month
#** Every N month(s) until date (or forever), e.g. the 4th Thursday of that month
#** Every N year(s), until date (or forever), e.g. November 27th every year
#** Every N year(s), until date (or forever), e.g. November 27th every year
-
#* Good support for timezones, including plane journeys that start and end in different timezones.  At least the back end and iCal import/export should handle them correctly, preserving timezone information if and when it exists.  ([[User:matthew_exon|matthew_exon]] - this stuff has caused me enough trouble I've resorted to writing [http://mat.exon.name/cgi/travel-calendar this] to work around it.)  Use cases:
 
-
#** I work in Sydney.  A colleague in San Francisco invites me (with an iCal file) to a weekly conference call at 09:00 every Wednesday, SF time.  When daylight savings switches in either SF or Sydney, the appointment adjusts accordingly, so that it's always 09:00 SF time. For bonus points, calendar gives me an extra warning whenever any timezone I have appointments in has an upcoming daylight savings change.  "Daylight savings starts in the USA on Sunday. The following appointments will be an hour earlier: (shows my American appointments)".  Then, a couple of weeks later, "Daylight savings ends in New South Wales on Sunday.  The following appointments will be an hour earlier: (also shows my American appointments)".
 
-
#** 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.
 
-
#*** 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 ===
Line 145: Line 122:
#* Allow generic and open format of Calendar data - so that it can be used by 3rd party apps as well
#* Allow generic and open format of Calendar data - so that it can be used by 3rd party apps as well
#** should be '''VCARD''' - look for best suitable VCARD definition - [[User:asys3|asys3]]
#** should be '''VCARD''' - look for best suitable VCARD definition - [[User:asys3|asys3]]
-
#** That would be vCard 3.0, specified in RFC 2425 and RFC 2426.  But this is for import/export, not for the application data - [[User:gcobb|gcobb]]
 
#* Synching
#* Synching
#** '''Support syncml''' to synchronize contacts to mobile phone and a server pim database (e.g. funambol, evolution) - [[User:asys3|asys3]]
#** '''Support syncml''' to synchronize contacts to mobile phone and a server pim database (e.g. funambol, evolution) - [[User:asys3|asys3]]
#** Support '''synching over bluetooth''' and wlan - [[User:asys3|asys3]]
#** Support '''synching over bluetooth''' and wlan - [[User:asys3|asys3]]
-
#** Support synching with OpenSync to allow syncing with widest range of other applications (including kdepim and evolution) - [[User:gcobb|gcobb]]
 
-
#** Support direct syncing with Outlook (over BT, USB, WiFi) -- it may be evil but it is by far the dominant requirement for anyone in business - [[User:gcobb|gcobb]]
 
-
#* Avoid the "first name / last name" thing.  Where am I supposed to put the middle name?  What about when my contact is a business name?  And it causes lots of confusion for Chinese names where the family name is the first name.  Better to just have a single "Name" field.
 
=== ToDo List ===
=== ToDo List ===
#* Items should have start date, deadline, priority, tags as well as description and completed (and completion date).  
#* Items should have start date, deadline, priority, tags as well as description and completed (and completion date).  
#* Should optionally be finger-friendly (especially relevant for to-do lists)
#* Should optionally be finger-friendly (especially relevant for to-do lists)
-
#* Subtasks/Projects - a 'hierarchical todo list', can include tick-box items, amount-completed for subtasks, and/or just headings (see [http://www.janerob.com/rob/prozect/ prozect])
+
#* Subtasks/Projects
#* Integration with sites like ToodleDo or RememberTheMilk.
#* Integration with sites like ToodleDo or RememberTheMilk.
#* Recurring tasks
#* Recurring tasks
Line 165: Line 138:
#* Multiple lists (home, work, hobbies) - basically a tag also.. but tied with calendar and addressbook and their separate groupings
#* Multiple lists (home, work, hobbies) - basically a tag also.. but tied with calendar and addressbook and their separate groupings
#* Should be viewable (and zoomable) by context or tag.  Zoom will take the current filtered/grouped level and elevate it to the top or root level, so that nothing else is visible.  Good for focusing on a project, or showing tasks only relevant to a context ("At Office", "Out shopping")
#* Should be viewable (and zoomable) by context or tag.  Zoom will take the current filtered/grouped level and elevate it to the top or root level, so that nothing else is visible.  Good for focusing on a project, or showing tasks only relevant to a context ("At Office", "Out shopping")
-
#* Synching
 
-
#** Support synching with OpenSync to allow syncing with widest range of other applications (including kdepim and evolution) - [[User:gcobb|gcobb]]
 
-
#** Support direct syncing with Outlook (over BT, USB, WiFi) -- it may be evil but it is by far the dominant requirement for anyone in business - [[User:gcobb|gcobb]]
 
=== Syncing ===
=== Syncing ===
Line 175: Line 145:
*Maybe central place in settings or in a dedicated sync application to do these settings. "Sync now!" only from applications. (Simpler this way?) [[User:ossi1967|ossi1967]] 12:53, 31 October 2008 (UTC)
*Maybe central place in settings or in a dedicated sync application to do these settings. "Sync now!" only from applications. (Simpler this way?) [[User:ossi1967|ossi1967]] 12:53, 31 October 2008 (UTC)
*Pay special attention to the way instant messaging Contacts are handled after a sync: Today it may happen that people from my XMPP roaster will end up as new contacts after a sync even though they already have a full entry (with phone number, postal address etc.) in the EDS database... The PIM framework needs a way to keep track of changes on both ends, instant messaging and sync interface, and at least try to re-apply roaster data to the correct contacts even after a full "overwrite from server"-sync. [[User:ossi1967|ossi1967]] 10:21, 24 November 2008 (UTC)
*Pay special attention to the way instant messaging Contacts are handled after a sync: Today it may happen that people from my XMPP roaster will end up as new contacts after a sync even though they already have a full entry (with phone number, postal address etc.) in the EDS database... The PIM framework needs a way to keep track of changes on both ends, instant messaging and sync interface, and at least try to re-apply roaster data to the correct contacts even after a full "overwrite from server"-sync. [[User:ossi1967|ossi1967]] 10:21, 24 November 2008 (UTC)
-
*Strongly recommend adopting OpenSync as the sync tool: it either already handles or intends to handle the issues above (which are really very tough) -- no point in duplicating work - [[User:gcobb|gcobb]]
 
-
*Easy, single-button sync with paired mobile phone - [[User:gcobb|gcobb]]
 
== User Interface Considerations ==
== User Interface Considerations ==
Line 190: Line 158:
I made a quick & dirty demo with the bookmarks. You can try it yourself by downloading and importing [http://naranek.wippiespace.com/n800/Calendar-final-2.html this file] to bookmarks:  
I made a quick & dirty demo with the bookmarks. You can try it yourself by downloading and importing [http://naranek.wippiespace.com/n800/Calendar-final-2.html this file] to bookmarks:  
I have only filled one day and made paths that lead to it from week, month and year routes so you get the idea. The numbers are there mostly to keep the items in order. This would need a nicer way of going back in the structure, and browsing long lists up and down, but it's just quick & dirty prototyping anyway. [[User:naranek|naranek]] [[Special:Contributions/80.221.22.253|80.221.22.253]] 10:14, 1 November 2008 (UTC)
I have only filled one day and made paths that lead to it from week, month and year routes so you get the idea. The numbers are there mostly to keep the items in order. This would need a nicer way of going back in the structure, and browsing long lists up and down, but it's just quick & dirty prototyping anyway. [[User:naranek|naranek]] [[Special:Contributions/80.221.22.253|80.221.22.253]] 10:14, 1 November 2008 (UTC)
-
 
-
A team of UI designers from University of Michigan are [http://www.internettablettalk.com/forums/showthread.php?t=25257 sharing] mock-ups and a Flash page describing the interface of a fictious application called Maemo Organizer. It'd be great if they could collaborate with one of the projects hereunder or developers interested in an organizer/PIM application. If you are currently designing such application consider to look at these mock-ups and the Flash page for inspiration --[[User:allnameswereout|allnameswereout]] 13:31, 2 December 2008 (UTC)
 
== Technical Design Considerations ==
== Technical Design Considerations ==
Line 211: Line 177:
http://www.pimlico-project.org/dates.html
http://www.pimlico-project.org/dates.html
==== Good ====
==== Good ====
-
*Synchronisation via syncevolution is possible and works well
 
-
 
==== Bad ====
==== Bad ====
*Seems like its no longer actively developed for Maemo
*Seems like its no longer actively developed for Maemo
*Dreadful interface. Not intuitive.
*Dreadful interface. Not intuitive.
-
*Seems to switch appointments to other times randomly after tipping on an entry with the stylus.
 
-
*No alarms.
 
----
----
Line 271: Line 233:
* No options for non-shaded/combined weekends
* No options for non-shaded/combined weekends
* Slows down to a crawl when there are a lot of events in the database.
* Slows down to a crawl when there are a lot of events in the database.
-
* Editing repeating event changes all occurrences, and delete removes current or current and all future, no other options
+
* Editing repeating event changes all occurences and delete removes current or current and all future, no other options
-
* When entering a new event, end date(+time) does not automatically update when start date(+time) changes
+
* When entering an new event, end date(+time) does not automatically update when start date(+time) changes
-
* When entering a new event it takes much more work to change time and date than for example on Date Book on PalmOS (check GarnetVM)
+
* When entering an new event it takes much more work to change time and date that for example on Date Book on PalmOS (check GarnetVM)
* No snooze function on the alarm
* No snooze function on the alarm
-
* No quick way to turn off the alarm when your tablets display is locked.
+
* No quick way to turn off the alarm when your tablet's display is locked.
----
----
Line 315: Line 277:
==== Bad ====
==== Bad ====
-
* <s>Grid views missing</s>
+
* Grid views missing
-
::This seems to be fixed in last version ([[User:kup|kup]])
+
* Can't deselect an online calendar from sync - all or nothing
* Can't deselect an online calendar from sync - all or nothing
* Can't enter tasks into subcalendars
* Can't enter tasks into subcalendars
* Tied only to Google calendar
* Tied only to Google calendar
* No iCal import
* No iCal import
-
* Only What is synced from Google calendar, missing Where and Description
+
 
----
----
Line 332: Line 293:
https://garage.maemo.org/projects/kdepimpi/
https://garage.maemo.org/projects/kdepimpi/
* For more information please see: http://www.internettablettalk.com/forums/showthread.php?t=15566
* For more information please see: http://www.internettablettalk.com/forums/showthread.php?t=15566
-
* The definitive home for the KDEMPIMPI project can be found at http://sourceforge.net/projects/kdepimpi/
 
-
==== Good ====
 
-
* kdepimpi is a mature, very stable, working application under X11, Windows, and the Sharp Zaurus (OpenZaurus, ARM architecture)
 
-
* the [http://www.oesf.org/forum/index.php?showtopic=25009&st=15&p=177780&#entry177780 .deb packaged version of kdepimpi compiled for OESF] installs and runs very, very well on the N810 (models with soft keyboards will probably not work as the package is not Hildonized). The [http://www.zdez.org/libqt3-3.3.deb libqt3] package is required.
 
-
* the package currently meets about 90% of the [[#Desired_Features|Desired Features]]
 
-
* the current port of kopi (the calendar/to-do list) is usable on a daily basis for simple uses <s>for people very familiar with the program on other platforms and is a good proof-of-concept</s>
 
-
* the kopi calendar can be synchronized with a google calendar, via the PreSycn preferences setting to use "wget" to download the ICS version of the google calendar, and through [http://gcaldaemon.sourceforge.net/ GCALDaemon] to upload the calendar back to google.
 
-
* <s>the source code and overall package status are of enough quality that even someone with my ([mailto:z2n@merctech.com z2n]) limited development expertise was able to do the basic port to Maemo. I estimate that a fully Hildonized port to Maemo would not be difficult for a skilled developer.</s>
 
-
==== Bad ====
 
-
* <s>the Maemo port far from complete and is not currently usable for novices...the GUI is lacking menus and icons, making navigation difficult at best</s>
 
-
* <s>only the kopi (calendar/to-do) application has been ported</s>
 
-
* the installation procedure is not ready for general use (requires <tt>dpkg -i --force-depends</tt>, manual <tt>ldconfig</tt>, etc.)
 
-
* <s>the current installation doesn't provide desktop launcher (menu entries)</s>
 
-
* Does not work with a soft keyboard for n800 users
 
-
* The battery seems to run down quickly if kdepimpi is left running
 
-
* Most of the dialogs are too large for the screen so controls are off the bottom of the screen.
 
-
* The menu takes up screen space because the app is not hildonized.
 
-
* There is no full screen mode.
 
-
* Cannot type anything requiring the "Fn" key (or "Chr" key) into the edit boxes.
 
----
----
Line 386: Line 328:
*Command line only, need to edit config files
*Command line only, need to edit config files
*No direct syncing (desktop to tablet)
*No direct syncing (desktop to tablet)
-
*No sync of GPE calendar entries
 
----
----
Line 400: Line 341:
* exports to iCal
* exports to iCal
==== Bad ====
==== Bad ====
-
* Agenda can have a single appointment repeated
+
* Agenda can have a single apointment repeated
* tightly integrated with his ToDo app so that it fires up ToDo if that's not running when you create a new appointment
* tightly integrated with his ToDo app so that it fires up ToDo if that's not running when you create a new appointment
* not finger friendly - buttons too small
* not finger friendly - buttons too small
* updates take a long time, with little user feedback
* updates take a long time, with little user feedback
-
 
-
----
 
-
 
-
=== Seqretary ===
 
-
http://www.kawseq.com/products/seqretary
 
-
==== Good ====
 
-
*Actively being developed
 
-
*Designed for Maemo on Nokia Internet Tablets
 
-
*Calendaring, scheduling and alarms
 
-
*Voice recording suitable for making notes and taking dictation
 
-
 
-
==== Bad ====
 
-
*Still under development
 
-
*Contact management, task management, and synchronisation not yet implemented
 
-
 
-
----
 
== Other links ==
== Other links ==

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)