Task:PIM - Revision history

amigadave: wikify link

amigadave — Tue, 13 Apr 2010 13:18:38 GMT

wikify link

← Older revision		Revision as of 13:18, 13 April 2010
Line 336:		Line 336:
	* kdepimpi is a mature, very stable, working application under X11, Windows, and the Sharp Zaurus (OpenZaurus, ARM architecture)		* 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 [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 [~~http://wiki.maemo.org/Task:PIM~~#Desired_Features Desired Features]	+	* 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 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.		* 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.

69.248.69.237: /* Good */

69.248.69.237 — Sat, 17 Oct 2009 22:08:24 GMT

Good

← Older revision		Revision as of 22:08, 17 October 2009
Line 338:		Line 338:
	* the package currently meets about 90% of the [http://wiki.maemo.org/Task:PIM#Desired_Features Desired Features]		* the package currently meets about 90% of the [http://wiki.maemo.org/Task:PIM#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 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>		* <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>

tor: Typo: apointed->appointed

tor — Tue, 06 Oct 2009 13:50:07 GMT

Typo: apointed->appointed

← Older revision		Revision as of 13:50, 6 October 2009
Line 399:		Line 399:
	* exports to iCal		* exports to iCal
	==== Bad ====		==== Bad ====
-	* Agenda can have a single ~~apointment~~ repeated	+	* Agenda can have a single appointment 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

davep1: Added Seqretary

davep1 — Thu, 03 Sep 2009 19:18:13 GMT

Added Seqretary

← Older revision		Revision as of 19:18, 3 September 2009
Line 403:		Line 403:
	* 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 ==

12.167.75.11: /* Bad */

12.167.75.11 — Wed, 02 Sep 2009 20:15:48 GMT

Bad

← Older revision		Revision as of 20:15, 2 September 2009
Line 321:		Line 321:
	* 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
	----		----

69.12.250.150: /* Bad */

69.12.250.150 — Tue, 21 Apr 2009 16:39:19 GMT

Bad

← Older revision		Revision as of 16:39, 21 April 2009
Line 217:		Line 217:
	*Dreadful interface. Not intuitive.		*Dreadful interface. Not intuitive.
	*Seems to switch appointments to other times randomly after tipping on an entry with the stylus.		*Seems to switch appointments to other times randomly after tipping on an entry with the stylus.
		+	*No alarms.

	----		----

122.106.167.45: /* Calendar */

122.106.167.45 — Sat, 18 Apr 2009 22:16:29 GMT

Calendar

← Older revision		Revision as of 22:16, 18 April 2009
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 ===

jukey: /* Good */

jukey — Thu, 02 Apr 2009 15:17:21 GMT

Good

← Older revision		Revision as of 15:17, 2 April 2009
Line 196:		Line 196:
	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

jukey: /* Bad */

jukey — Thu, 02 Apr 2009 15:16:44 GMT

Bad

← Older revision		Revision as of 15:16, 2 April 2009
Line 199:		Line 199:
	*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.

	----		----

jukey: /* Bad */

jukey — Thu, 02 Apr 2009 15:15:24 GMT

Bad

← Older revision		Revision as of 15:15, 2 April 2009
Line 366:		Line 366:
	*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
	----		----