Bug 81910 - hierarchical todo list in the "What's next" view
Summary: hierarchical todo list in the "What's next" view
Status: CONFIRMED
Alias: None
Product: korganizer
Classification: Applications
Component: todoview (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 66219 92365 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-05-20 16:13 UTC by Tomas Pospisek
Modified: 2008-11-13 18:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Hierchial Todo display (version 1) (5.03 KB, patch)
2004-12-25 05:54 UTC, Anton Markov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Pospisek 2004-05-20 16:13:23 UTC
Version:            (using KDE KDE 3.2.2)
Installed from:    Debian testing/unstable Packages

I am always creating hierarchical todos, such as:

customers
  customer_X
    send invoice
  customer_Y
    send invoice
  customer_Z
    send invoice
    fix bug
...

Now if I have a look at the "What's next" view I get a list possibly like this:

send invoice
fix bug
customer_Z
send invoice
customers
send invoice
customer_X
customer_Y

... in no aparent order and with no aparent releation between those
entries. Like that such a view is not really very useful.

I suggest to either:

* make todo display in "What's new" hierarchical as follows:
   
  customers
    customer_X
      send invoice
    customer_Y
      send invoice
    customer_Z
      send invoice
      fix bug

* or to prefix it with the "whole path" (parent todos) like this:

  customers:customer_X:send invoice
  customers:customer_Y:send invoice
  customers:customer_Z:send invoice
  customers:customer_Z:fix bug

  and to only list leaves of the todo-tree - which is a policy
  decision though - one that we had to do in karm too :-/ 

Thanks a lot for your good work korganizer people!! Greets,
*t
Comment 1 Reinhold Kainhofer 2004-10-04 01:09:36 UTC
*** Bug 66219 has been marked as a duplicate of this bug. ***
Comment 2 Reinhold Kainhofer 2004-11-13 18:48:40 UTC
*** Bug 92365 has been marked as a duplicate of this bug. ***
Comment 3 Anton Markov 2004-12-24 04:43:52 UTC
I've taken a look at the sourcecode (mainly in kowhatsnextview.cpp) and it looks like the second method, "prefix it with the "whole path" (parent todos)", should be fairely easy to implement.

Doing a true hierchial representation (aka. method 1) looks complex, since it would require bulding a tree representation of the ToDo's first. This is also necessairy to group the ToDo's with their parents.

Is someone currently working on this bug, or should I take a shot at it? I think I have an idea for how to get the hierchial view (which is the method I like) to  work.
Comment 4 Reinhold Kainhofer 2004-12-24 14:17:23 UTC
Hi Anton,
Currently there's no-one working on that issue. I agree that method 1 would be easier to implement, but it has lots of problems. In particular, to-do summaries can be quite long. Concatting several of these might give you a three or four-line text...

To get the hierarchy, you could just iterate over the whole to-do list, and just look at top-level items (i.e. items that don't have a relatedTo item set). For each of these, you can go recursively through it's children (related()).

Cheers,
Reinhold

Comment 5 Anton Markov 2004-12-25 05:54:18 UTC
Created attachment 8807 [details]
Hierchial Todo display (version 1)

Here is a first draft of a patch to add hierchial display of Todo items to the
"What's New" view.

I'll briefly describe the new behaviour:
- The ordering remains the same, but, for example, if a todo to be render
first, it will cause the whole tree to be rendered first. Todo items within a
tree are ordered by due date.
(a tree is a hierchy of todos starting with a top-level item (having no
parent))

- Rendering one todo causes the entire tree to be rendered regardless of
whether or not they fit the priority/date criteria. Only trees with no rendered
children are ignored. I think this makes sense.

- Colour-coding was added to distinguish the importance of various Todos (since
now a lot more todos are rendered). The colours were chosen to match the Todo
List colours.
 - Navy-blue - normal
 - Blue - due soon (within current time-period)
 - Red - overdue (due before current time-period)
 - Grey - low priority

- If a Todo is complete, it will not be displayed, and its entire sub-tree will
be hidden. This behaviour would be consistent with the changes I propose in bug
95803, which proposes marking all sub-todos of a completed todo complete.

One major todo is making the colours configurable. In fact, it would be nice to
use KHtml for the "What's New" view so we could use custom CSS stylesheets like
Kopete does.

Comments are welcome.
Comment 6 Reinhold Kainhofer 2006-11-02 19:09:31 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 7 ned 2007-03-27 05:03:45 UTC
this feature would STILL be very useful :)