From: Christian Egli <christian.egli@sbs.ch>
To: emacs-orgmode@gnu.org
Subject: Re: Setting taskjuggler project start date (ox-taskjuggler)
Date: Wed, 24 Apr 2013 10:30:55 +0200 [thread overview]
Message-ID: <871ua0tjnk.fsf@sbs.ch> (raw)
In-Reply-To: CA+M2ft8HnVmQB5-Hq-BLutNH5viSQ3HT4bVpR2k_PJnueFD48g@mail.gmail.com
John Hendy <jw.hendy@gmail.com> writes:
> On Wed, Mar 27, 2013 at 9:37 AM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>> Hello,
>>
>> John Hendy <jw.hendy@gmail.com> 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
prev parent reply other threads:[~2013-04-24 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 6:27 Setting taskjuggler project start date (ox-taskjuggler) John Hendy
2013-03-25 7:17 ` John Hendy
2013-03-25 7:30 ` John Hendy
2013-03-25 20:15 ` Nicolas Goaziou
2013-03-25 22:14 ` John Hendy
2013-03-27 14:37 ` Nicolas Goaziou
2013-03-27 22:00 ` John Hendy
2013-04-24 8:30 ` Christian Egli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871ua0tjnk.fsf@sbs.ch \
--to=christian.egli@sbs.ch \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).