Version: (using KDE 4.1.4) OS: Linux Installed from: Gentoo Packages KTimeTracker (and KArm before that) is already quite good and I use it every day now! The export function could benefit from a couple of enhancement IMHO. When the 'history' is being exported, it would be really useful that the subtask have a reference to their parent taskname. Right now, only the name of the subtask shows, which makes it harder to extract more detailed information... Thanks for your support Jp
Full ack that it can be improved. In fact, there are so many possible improvements that I am struggling, no so few. What do we want, something like this: ; 2009-01-02; 2009-01-03; working; ; 5:30 ; 4:40 programming; working; 2:00 ; 2:00 C++; programming ; 0:30 ; 2:00 this should do it, shouldn't it?
Many thanks for looking into this! I guess the best format would be XML(!) with some simple xlst (a default one for a csv-like output and perhaps some custom ones could be added?)! What you're proposing would be good for a small number of tasks, but it would harder to use the output if some task are 'deep'. Perhaps, using a different separator for subtasks names vs the other columns would make it easier to use the output? ; 2009-01-02; 2009-01-03; working ; 5:30 ; 4:40 programming // working ; 2:00 ; 2:00 C++ // programming ; 0:30 ; 2:00 What do you think? Thanks again for looking into this! Jp
And if we export XML, who shall read it? I want to export CSV so you can read the file in any spreadsheet program. Plus, I see the scaling issue rather in the xml format.
Yes, CSV is still more convenient, as close to 100% of computers have either M$-Office or Ooo installed, but you need to be an expert to read XML, and even more expert to transform it. However, the subtask tree must be exported as well (as it was in Karm!), the reference to parent task can be derived from the order. XML could come as an additional option, besides CSV, but not as a replacement.
I will not implement the XML export, if you want, please assign this task to you.