Re: State of KPlato?
Dag Andersen <[email protected]>
| Newsgroups | gmane.comp.kde.kplato |
|---|---|
| Message-ID | <[email protected]> |
On Tirsdag 26 oktober 2004 21:54, Raphael Langerhorst wrote: > Hi all, > > What is the current state of KPlato? Is it desired to improve it? Well, I think so :) > .... Hmm.. just skimmed through the KPlato docs... it seems some > people have already thought about what should be implemented, how > far is it? In short, you can currently do: - Define tasks (incl. summarytasks, milestones), resources, calendars. - Assign calendars to resources. - Allocate resources to tasks. - Link tasks. - Have the project calculated. - Presentation mainly in ganttchart using KDGantt. There is also a network diagram and a resourceview, but they are rudimentary and mostly for testing. Doesn't sound to bad, eh? Well, what's not so good, missing? - The dialogs are not good (understatement). - Command history only partially implemented. - There are some holes in the calculation. - Calendar stuff not complete. - No resource leveling. - more... I'm currently working on link handling in KDGantt, mainly implementing linktypes (FinishStart, FinishFinish, StartStart). When that's done (today, I hope), I'm planning: - Implement task linking from KDGantt in kplato. (most code finished) - Have a look at the project calculations again. - Go through the dialogs and see if I can patch up the worst things. - Implement missing command history. - hmmmm > > And what about ... for example Mr. Project? Don't know how far they have come. No room to run gnome on my computer :( (By the way, there is also TaskJuggler) > > Any thoughts on the subject? The dialog approach to data entering is not always optimal. I've been thinking of implementing most of the dialog stuff in a 'structured editor' based on QListView. I've found that to be (almost) impossible, so personally I decided to postpone that until Qt4, which AFAICS offers more flexibility in this respect. > Raphael -- Mvh, Dag Andersen