[kplato] Application Class Structure

[Thomas Zander]

On Sunday 24 June 2001 22:36, John D Lamb wrote:
> Thomas Zander wrote:
>> > Could you ellaborate on what are predecessors and successors?
> > It looked to me like these are just interface methods to the
> > hierarchy of projects/tasks/subtasks. So I am wondring why there
> > are so many functions for this, a
> >     QList<Node*> getParents();
> >     QList<Node*> getChildren();
> > would suffice.
>
> These are not related to the tree structure at all, but to the directed
> graph of
> dependencies among the tasks. getParent and getChildren are probably
> better names for the
> tree structure.

I'm sorry, but I must be missing somehting again :(

The tree structure consists of nodes, nodes are everything from projects to 
tasks. Probably resources would fit in there as well.
Then what is the 'directed graph of dependencies among the tasks' ? you plan
to keep seperate?

-- 
Thomas Zander