Re: depending TODOs, scheduling following TODOs automatically

From: Carsten Dominik <dominik@science.uva.nl>
To: Russell Adams <RLAdams@AdamsInfoServ.Com>
Cc: emacs-orgmode@gnu.org
Subject: Re: depending TODOs, scheduling following TODOs automatically
Date: Mon, 8 Oct 2007 21:48:28 +0200	[thread overview]
Message-ID: <4451bef76a71d49ffc88d9d8b87f2940@science.uva.nl> (raw)
In-Reply-To: <20071008135240.GB10774@odin.demosthenes.org>

On Oct 8, 2007, at 15:52, Russell Adams wrote:

> I know I'm replying to myself, but I had an idea.
>
> If a link could show the state of a linked TODO, that would make for a
> good visualization. I could then follow the link and just adjust my
> order to account for dependencies. It sounds like a more "permanent"
> agenda view that you could edit to get the right order.
>
> Ie:
>
> * Things to do in reverse order
> ** TODO One
> ** TODO Two
> ** TODO Three
>
> * Implementation Order
>
>  TODO Three
>  TODO Two
>  TODO One

I don't know what others think, but I did not understand a single word 
of this message :-)  Could you please be a bit more verbose?

- Carsten

>
>
>
> On Mon, Oct 08, 2007 at 08:43:53AM -0500, Russell Adams wrote:
>> Lets make that more generic. How do you organize your dependencies
>> anyway? The basic hierarchy can't always be setup in order.
>>
>> One of the things I'd considered is an optional GUID property for each
>> todo, and then a DEPENDS property with the GUID of any (potentially
>> multiple?) dependencies.
>>
>> There'd need to be a way to navigate this list, though goto via GUID
>> link would work nicely. It may even be appropriate to list the current
>> TODO as BLOCKED until all dependencies are DONE.
>>
>> Russell
>>
>> On Mon, Oct 08, 2007 at 09:26:58AM -0400, Denis Bueno wrote:
>>> On 10/8/07, Rainer Stengele <rainer.stengele@diplan.de> wrote:
>>>> Hi!
>>>>
>>>> Having a TODO which depends on an earlier TODO I would like to 
>>>> trigger the timestamped scheduling of
>>>> the following TODO when the former is DONE.
>>>
>>> I second this request.  I often like to schedule a workflow where 
>>> task
>>> A must precede B which precedes C, &c., but I'd rather not see that B
>>> and C are scheduled until and (and B, respectively) are DONE.  Seems
>>> like a very useful way to organise.
>>>
>>> -- 
>>>                               Denis
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Remember: use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>> ------------------------------------------------------------------
>> Russell Adams                            RLAdams@AdamsInfoServ.com
>>
>> PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/
>>
>> Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> ------------------------------------------------------------------
> Russell Adams                            RLAdams@AdamsInfoServ.com
>
> PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/
>
> Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>

--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477