Version: (using KDE KDE 3.2.2) Installed from: Debian testing/unstable Packages The idea of todo is something you need to do NOW, right? But some things need to be done every quarter or some other time period. And they may take a while. or you cannot get to them today. They may be put in as an event so that they will reccur with alarms but it is messy to have to click suspend 59 minutes for 24 hours until you can get to it the next day. or days from then. If you OK it then you will not be reminded again. I propose that an event should have a button next to the sound and program buttons for 'make todo'. When the alarm goes off the event automatically becomes a todo at some predefined priority. perhaps when you click on the button it could be set. More background. right now I am leaving quarterly and monthly todos in the list and marking them as done but not purging them. I also put in a recurring event for the same item. when the event goes off i uncheck the todo. If i could simply have the recurring event create a new todo, i could purge the old ones and have a less cluttered todo list. this would also alleviate the problem of having to remember them myself as well if i cant get to them today.
Another thing is, that an appointment may be missed and nobody notices. That's why I would like to confirm all appointments with checks (like a TODO). Or simply make an option to merge these concepts of events and todos, because in practise they don't differ that much. The only difference is: TODOs can be checked but need not to be scheduled and appointments must have an associated time, because they are always scheduled. Dynamically switching between them makes a schedule more flexible and thus korganzier much more useful.
Hello JT, KOrganizer now supports recurring to-dos. Don't they do what you want? Cheers, Reinhold
Not exactly. If i read the implmentation correctly it simply creates a new todo with a new due date immediately upon checking the old one. One of my goals was to clean up the todo list. I was thinking of events that come due in the calendar which should become a todo. Do reoccuring todos show up in the calendar? Can data easily move from an event to a TODO. The anniversary example given in http://bugs.kde.org/show_bug.cgi?id=57921 is exactly what I am thinking. But if I read the implementation correctly that example is not exactly fitting that request because your todo list would have to be sorted by date instead of priority. I figure the main difference between a todo and an event is the way they are used. They contain most of the same data but events are sorted chronologically whereas todos generally are sorted by priority but may also be sorted by date and other fields. I personally sort them by priority. If I have to add dates to all of them can I get them sorted by date then priority? This feature would help you to not lose events that you cannot get to right now but need to get to sometime today or tommorrow. The event does not need to be on the todo list all the time but when it comes due it should be added until you can get to it. Then you mark it as done. It might or might not come due again based on the original event recurrence settings. The todo itself would not be recurring. Also, instead of automatically having an event become a TODO (as I originally proposed) it should probably be on the Alarm box with suspend and OK. The user could then choose the priority level for the todo along with adjusting date information if needed.
I agree with JT here. Another example is a CRM-usage (e.g. a CRM using the korganizer framework for display). The event "call customer not before day X" could be modeled perfectly using this feature. So this is really very useful.
You can add a start date to a to-do, and hide all to-dos (using a filter) where the start date/time has not yet happened. Isn't this exactly what you are requesting? Reinhold
There are two parts to my request. Event and Todo. Recurring todos does solve the TODO part of the request but I want to see that information on the calendar that will become a TODO. No this does not fully implement my request. In other words I have events on the calendar that I want to see there and when those event alarms go off I want to convert them into TODOs. With the current implemenation I still have to maintain two inputs for the same task; one as a todo and the other as an event. If I could convert an event alarm into a todo I would only need one input. The conversion would be done on alarm. Yes I can do it manually but that is the point of the feature request: to automate as much as possible.
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
Reassigning the bug also changed the status from UNCONFIRMED to NEW. Undoing that manually :-(