Re: [Evolution] Tasks % complete idea

On 13 Feb 2001 19:25:05 -0500, JP Rosevear wrote:
On 11 Feb 2001 15:27:04 -0500, Ben FrantzDale wrote:
I was mentioning this sort of thing before but for the % complete entry
of the todo (tasks) list, It would be great if I could type in 21/64 and
have that become 33%.  (21/64=.328125)
The reason being, for reading assignments in school I know how many
pages I have to read and how many I've read. Currently 21 of 64. I'm
sure there are other tasks that could be entered much easier as a

Well, I'll file this as a feature request, but to be honest i don't see
this as a priority.

Also, I've noticed there isn't a field for estimated time required. That
would be nice. Then a summary could say ``you have x hours of work to do
today'' or the % complete column could say ``20% (3 hours to go)''

Well the duration field in the icalendar is mutually exclusive with the
due field.  There is a funny inconsistency with the spec I believe.
I've sent mail to get clarification.

I don't know the spec, but logically I don't see an inconsistency. Do
you mean that the icalender spec somehow only alows one field or the
other? It seems like there should be a way to say ``it's due at time x
on day y but will take z hours to complete''.

Also, if a big (time consuming) asignment were comming up, Evolution
could be smart and highlight an item due in 5 days requiring 2 days work
before something due tomarrow requiring five minutes time.

Do you have any ideas for the heuristic to determine the ordering?

Something along the lines of what Eric Newman said: priority should be
proportional to the time density that it will require to finish on time.

(Aside: Consider this for a future, more complex behavior, though: Since
the system knows my calendar, it could calculate weighting for
work-related tasks during only work hours. Or it could suggest that now
might be a good time to start laundry or whatever... There are all sorts
of possabilities for the organization-impared :-)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]