From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eddward DeVilla" Subject: Re: depending TODOs, scheduling following TODOs automatically Date: Mon, 8 Oct 2007 21:58:37 -0500 Message-ID: References: <6dbd4d000710080626i52f0f0t9354addc33c0efee@mail.gmail.com> <20071008134353.GA10774@odin.demosthenes.org> <877ilxmimn.fsf@bzg.ath.cx> <877ilxnh44.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1If5Iv-00016T-TU for emacs-orgmode@gnu.org; Mon, 08 Oct 2007 22:58:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1If5Iu-00013g-E5 for emacs-orgmode@gnu.org; Mon, 08 Oct 2007 22:58:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1If5Iu-00013R-7k for emacs-orgmode@gnu.org; Mon, 08 Oct 2007 22:58:40 -0400 Received: from fk-out-0910.google.com ([209.85.128.184]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1If5It-0005FW-7E for emacs-orgmode@gnu.org; Mon, 08 Oct 2007 22:58:39 -0400 Received: by fk-out-0910.google.com with SMTP id 19so1418377fkr for ; Mon, 08 Oct 2007 19:58:37 -0700 (PDT) In-Reply-To: <877ilxnh44.fsf@bzg.ath.cx> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org I'm not sure we are talking about the same things really. On 10/8/07, Bastien wrote: > "Eddward DeVilla" writes: > > > My only real issue is that I tend to think of task dependencies in > > terms of the other tasks a given task is waiting on rather than what > > other tasks are waiting on a given task. > > Ok, then: > > * Task A > * Task B > :PROPERTIES: > :>TODO: {TODO 'previous "DONE"} > :END: > > => becomes TODO when previous tasks is DONE. I'm not really trying to deal with linear C depends and B which depends on A type things. Those are easy. I don't really need org to change the states for me. It's more like, work can't even begin E until A, C & D are done. Work can't start F until A & B are done. The reasons for the dependencies could be anything. (Requires a certain person's time, requires requisite info/result generated in other/blocking steps, artistic flare) Given a set of such ordering constraints, and estimated times to complete a step, what is the soonest a step can be started or completed? Can I use this info to generate a table of tasks with project start and end dates? > > This feels a little backward to me, but I could still use it. I'd > > still have to think about how to use this to make projections, but all > > the info is there for that. > > Sure! > > Two ideas again: > > 1) one aspect of Org is that it is very *fast*; we can change the TODO > state of an item with just one keystroke. Making this change trigger > actions should require some kind of double-check, otherwise we could > end up with a lot of changes that we're not fully aware of. > > One way to check the triggered changes is to build an actions pool > gathering all actions to be performed, then ask the user if he wants > to perform them. > > 2) In my proposal, the actions are just triggered by TODO state changes. > But each action could affect or be affected by any property. > > * Task A > :PROPERTIES: > :COLOR: red > :END: > > * Task B > :PROPERTIES: > :>TODO: {COLOR 'previous "green"} > :END: > > => becomes TODO when previous tasks property COLOR is "green". Again, interesting, but different from where I was going. I'm not after editing as a side effect. Just planning and organizing. In a previous message you said it isn't as complex as package dependencies. I guess what I was after might be. Edd