Revision as of 16:53, 24 January 2010

Ktimetracker

ktimetracker running on the N810

This page is for people who want to participate in the ktimetracker community. So, for (future) ktimetracker developers.

IDE

Please use qtcreator. Why? Quite easy: The description how to set up kdevelop with KDE is over 200 lines long. For eclipse it is 97 and for QtCreator it is 13. So, 13 lines to read instead of 222.

Architecture

ktimetracker is linked to main. Main creates mainwindow, this calls timetrackerpart, this calls timetrackerwidget, this calls taskview, this contains a karmstorage.

karmstorage stores and loads the events and tasks. taskview displays them. timetrackerwidget displays one or more taskviews in tabs. timetrackerpart can be integrated into a mainwindow or a kontact plugin. mainwindow adds the menu.

ktimetracker benchmark

The help menu

The help menu is stupidly overloaded and I cannot do anything about it because it is somewhere hidden in the library code. Would love to simplify it. "Help" does not need subitems - you want help.

The KPart Mess

ktimetracker is an application displaying a kpart. On the one hand, this makes it easy to be integrated as kontact plugin. But on the other hand, I have the feeling, ktimetracker can no long be debugged so easily. Here are the reasons why dedicated applications are better:

can be designed graphically in qtcreator
can be edited in qtcreator having all advantages like code completion
can be debugged step-by-step from qtcreator
toolbar magic can be done
with a kpart, you will have to do make install to get the kpart installed(?)

@@ Line 1: / Line 1: @@
+{|style="text-align:center"
+|[[Image:Snapshot-ktimetracker-n810.png|thumb|265px|Ktimetracker]]|| '''ktimetracker running on the N810'''
+|}
 This page is for people who want to participate in the ktimetracker community. So, for (future) ktimetracker developers.