Am 18.05.2018 um 10:44 schrieb Stéph:
> Overall, my view is that a better option would be to give all tasks a
> start date (meaning the first date that you /*can* /do them, not the
> first date that you */plan to /*do them
By the way, this is a general problem with nearly all todo managers -
they don't distinguish between "scheduled date" (date you plan to do a
task) and "start date" (earliest date you can work on the task). Most
don't even distinguish between due date (last date you can work on the
task) and start date, offering only one date field.
Of course, entering three dates makes everything more complicated. The
challenge lies in creating an interface that makes entering them easy.
Often you don't need to enter three different dates, so there should be
ways to enter only one date, and then differentiate in case of need. And
there should be ways to visualize tasks an move them on a time axis,
i.e. use of drag&drop, user-friendly calendar widgets, sliders etc. It's
time somebody comes up with a simple solution for that problem.
The worst thing is when fields are used inconsistently. Like in our
example, a start date on one task means earliest date and on another
task means scheduled date. Or an empty start date on one task means "can
start any time" (the task would be considered active), or on another
task means "has not yet started" (the task would be still inactive).
Once fields are used ambiguously, you can't create meaningful dynamic
views any more. Even inside MLO itself there is some inconsistency e.g.
in the formula for the computed score (used for ordering tasks), where
MLO interprets an empty due date as "today", which is usually not what
the user intended. Software should help people more in this regard by
making it crystal clear what every field means, and disambiguating edge
cases like empty dates.
Solving this problem would be in my view more helpful than any other
improvement or addition of features.
-- Christoph