KTimeTracker: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
= IDE = | = IDE = | ||
Please use qtcreator. Why? Quite easy: The [http://techbase.kde.org/Getting_Started/Set_up_KDE_4_for_development#Development_tasks 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. | Please use qtcreator. Why? Quite easy: The [http://techbase.kde.org/Getting_Started/Set_up_KDE_4_for_development#Development_tasks 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 = | = ktimetracker benchmark = | ||
Revision as of 13:44, 13 September 2009
This site is 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 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.
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.