Fwd: Duration Tally

["Eddward DeVilla" <eddward@gmail.com>]

Just forwarding to the list.  I forgot to.

---------- Forwarded message ----------
From: Eddward DeVilla <eddward@gmail.com>
Date: Jun 13, 2007 8:37 PM
Subject: Re: [Orgmode] Duration Tally
To: Scott Jaderholm <jaderholm@gmail.com>


On 6/13/07, Scott Jaderholm <jaderholm@gmail.com> wrote:
> On 6/13/07, Russell Adams <RLAdams@adamsinfoserv.com> wrote:
>
> > I'm planning ahead on some items, and having a way to represent the
> > amount of time a TODO item will take
>
> On a similar note, I like using the clocktable to see how long things
> have taken me, but sometimes I just want to put a time value under a
> heading, not a time range (because I forgot to clock in/out). Could
> CLOCK: => 2:00 or something similar work? If it did, maybe this could
> work for Russell as well (if he didn't mind using a clocktable instead
> of seeing it in the headline).
>
> Btw, I like Eddward's idea. Two other candidates for the property
> list/table are status (TODO, DONE) and tags. It might be more work
> however refactoring all the code that uses/displays them than the
> consistency would be worth.
>
> --Scott

Well, I wouldn't want too go to far in changing/breaking things.  I
just know that some things matter to me, but they might not matter to
enough others to build it into org.  Tags and todo sequences are
pretty general in themselves and it make sense for them to be treated
special bu org and agenda.  Also, all of this hinges on it not being
too unreasonable to fit into org-mode.  I just figured that attaching
an easy to access list of key value pairs that can be filtered on and
use in calculations might be generally useful.  I was just trying to
expand on the schedule keywords.

I haven't use clock table yet so I can't really comment on that.  I
was going to try to use deadlines, estimates and dependencies on todos
to build something like a gant chart or milestone table.

Edd