Re: [O] Remaining Work Report

[Myles English]

Forgot to copying this to the list:

>> On Tue, 15 May 2012 13:07:12 +0100, Myles English said:

  > Hi Sebastian,

I mean 'Sebastien'.

  > Sorry it has taken a long time to reply; I have been customising my
  > emacs, or has it been customising me...?

>> On Thu, 03 May 2012 16:38:12 +0200, Sebastien Vauban said:

  >> Hi Myles,
  >> Myles English wrote:
  >>>>> On Mon, 19 Mar 2012 14:33:17 +0100, Sebastien Vauban said:
  
  >>> > The question I'm trying to give an answer to is: *what's the
  >>> > remaining number of hours (or days) to finish my project*?

  > So that is your goal.
 
  >>> To exclude DONE items from the columnview I moved the Effort property out 
of
  >>> the way to the Old_Effort property when the state changes to DONE:

  > [function snipped]

  >>> Unlike your example I made heavy use of inline tasks and also wanted 
heading
  >>> numbers instead of asterisks, so that the final table looks like a table 
of
  >>> contents with estimated times remaining. I had to do some more things to
  >>> achieve this and can elaborate if you like.

  >> I finally spend some time to look at your answer, and give a feedback.

  >> First, I really thank you for your answer. It really is interesting to see 
how
  >> others tackle with the same (kind of) problem.

  > You're welcome.  It helps to justify the amount of time I spent on it if
  > I can share it with someone else.

  >> Second, about your "workaround". It does not satisfy me (renaming the 
property
  >> Effort to Old_Effort upon transition change to DONE)[1] because:

  >> - What happens if you reopen the task, clock some time on it, and close it?
  >> A new move of the property will occur, with a nil (hence, null?) value?
  >> Your Old_Effort will be overwritten?

  > Yes something like that, the function I posted is not consistent or
  > even reliable really.  It was intended as a starting point.

  >> - My goal is to show, in a table, the progress made on all tasks (TODO, 
STRT,
  >> DONE), and moreover to compare "spent time" (CLOCK) vs "estimated time"
  >> (Effort). Hence, I need to have the effort property at all times[2].

  > Okay so your goal has changed and looks like it would be approximately
  > double the work of what I needed.  When you reopen a task presumably you
  > would re-estimate the effort too which could lead to complications.  You
  > could may be consider never reopening a task and always starting a new
  > one?

  >> Do you have, maybe, an alternative way for those?

  > No, but if you look at the functions I sent originally and diff them
  > against the org- functions mentioned in their descriptions then you will
  > see what I had to change, which was not that much really, and maybe you
  > can build on it.

  > I would be interested to hear if you make something great with this.

  > -- 
  >   `--[ Myles ]

-- 
  `--[ Myles ]