gtg team mailing list archive

[Lionel Dricot <ploum@xxxxxxxxx>]

Our proposed task model is nearly implemented (but still not really
usable) in the following branch :
https://code.edge.launchpad.net/~gtg/gtg/subtask_model

But my first test on this are not really a success.

Example :

Let's have the following tasks in the browser :
Main
->subtask 1
->subtask 2
-->subsubtask 2.1

When opening Main, we should see :

-> subtask 1
-> subtask 2.1
 |-> subtask 2

(so you can see immediatly that you should concentrate on 1 and 2.1)


Problem 1 : I'm not sure it's really intuitive. It looks like it's buggy
because the representation of editor and tree look the same (even if
they are completely different)


Problem 2 : Let's say that Main is a subtask of MegaMain. What should
opening MegaMain looks like ?

->subtask 1
 |-> Main
-> subtask 2.1
 |-> subtask 2
   |-> Main 

???? Two times "Main" ? Not really pretty but why not...

Problem 3 : having such a representation makes it very very fragile when
the user edit it by hand. I realize that even if we can find a one-way
logic to describe a task structure, there's nearly no chance that a user
understand it.


If need advice on this. This stuff represent one full week of work but
we should remain realistic and maybe it was an error.

Lionel