From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Egli Subject: Re: Setting taskjuggler project start date (ox-taskjuggler) Date: Wed, 24 Apr 2013 10:30:55 +0200 Message-ID: <871ua0tjnk.fsf@sbs.ch> References: <87ppynxml5.fsf@gmail.com> <87sj3ggb8j.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:40736) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUv6a-0005K9-EO for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 04:31:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UUv6Y-0005j3-U4 for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 04:31:08 -0400 Received: from plane.gmane.org ([80.91.229.3]:39696) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUv6Y-0005ix-Nl for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 04:31:06 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UUv6V-00033b-U4 for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 10:31:03 +0200 Received: from alouette.sbs.ch ([194.29.12.218]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 Apr 2013 10:31:03 +0200 Received: from christian.egli by alouette.sbs.ch with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 Apr 2013 10:31:03 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org John Hendy writes: > On Wed, Mar 27, 2013 at 9:37 AM, Nicolas Goaziou wrote: >> Hello, >> >> John Hendy writes: >> >>> If you have =org-taskjuggler-keep-project-as-task=, it will take the >>> :start: property and use this in the project-as-top-level-task output. >>> Could this be used after =scheduled= and before defaulting to today's >>> date? This would seem to unify the syntax. >>> >>> It strikes me as reasonable to take 1) scheduled, 2) :start: in >>> property drawer and 3) default to today's date (in that order). I just pushed a change that should implement this the way you describe above. > Also, since I noticed that my tasks pick up the :start: property and > that the get-start (item) function *could* pick up a scheduled date as > well... might be good to anticipate the case in which the user > specifies both (probably accidentally). Maybe just provide an error > that either scheduled/deadline *or* :start: should be used, but not > both. Currently the org-taskjuggler-get-start function is only used to determine the start of a project or when checking if a task is a milestone (ie has neither a start nor an end), so the problem above is independent of that. But yes it is a problem: if you schedule a task and add a start attribute you will most likely have two start attributes for that task in your tjp file and the tj3 compilation will fail. Wouldn't this be sufficient? > Or if scheduled date conflicts with an duration/dependency > relationship as well? What do you mean? This to me sounds like it's the job of tj3. > Some of this might be handled by the tj3 command on the resultant .tjp > file, though. Yes, my sentiments exactly :-) Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland