From: Bernhard Schmitz <Bernhard.Schmitz@vis.uni-stuttgart.de>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Cc: "devnull@Karl-Voit.at" <devnull@Karl-Voit.at>
Subject: Re: Testers / Feedback wanted: Gantt charts via org-gantt.el
Date: Sat, 20 Jun 2015 12:46:49 +0000 [thread overview]
Message-ID: <b2ed392aeee147368012ed5606a39c37@barcarole.visus.uni-stuttgart.de> (raw)
In-Reply-To: <2015-06-03T17-15-29@devnull.Karl-Voit.at>
Hi Karl, hi Eric,
I know it has been a while. I think every suggestion has been implemented by now, except for linking independent headlines.
I wanted to ask for your input again, as I'm still not sure how to handle this, and both of your suggestions seemed to fall into the same category for me.
* Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
> The only comments I have at the moment is that it is missing support for
> milestones and all of my GANTT charts have such and that I would like to
> be able to link tasks across headlines (i.e. groups). Can I suggest a
>:milestone: tag or MILESTONE property for the former and a LINKED-TO or
> similar for the latter?
Should this link only be a graphical link, or should the start time of the second headline be determined by the end time of the first (as it is done with ordered headlines)? Or can what you have in mind be expressed by org-depend (see below)?
Karl:
> Oh, I was too lazy to write a working example.
>
> ,----[ working example ]
> | ** DONE My pretty task
> | CLOSED: [2015-04-30 Thu 07:50] SCHEDULED: <2015-04-30 Thu>
> | :PROPERTIES:
> | :CREATED: [2015-04-17 Fri 15:36]
> | :ID: 2015-04-17-Dach-zu
> | :TRIGGER: foo1(NEXT) bar1(WAITING)
> | :BLOCKER: previousXY prevZ
> | :END:
> `----
>
> So when this task got marked as DONE, the headings with the ID
> propertes "previousXY" and "prevZ" must not have been in an open
> state. Further more, the headings with ID "foo1" got the new states
> NEXT and "bar1" WAITING accordingly.
Your example clarified the effects of org-depend on the actual org file, but I'm not sure how this should translate to the gantt chart.
The :BLOCKER: property says that when this gets marked as done, the blockers must not be open. So actually, the :BLOCKER: property has no effect on either the start time, nor on the end time of a headline. It only clarifies the earliest possible end time - which cannot be expressed in a gantt chart.
Similarly, the :TRIGGER: property does not define a start or an end time of the triggered property either. The only case in which it does is if it triggers a (DONE), which would mean that an unrelated task suddenly becomes done simply by another task being done, and I don't think that happens all too often.
I now know that I can implement whatever you suggest with relatively little effort, but first I need to know what actually should happen.
Regards,
Bernhard
next prev parent reply other threads:[~2015-06-20 12:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 11:33 Testers / Feedback wanted: Gantt charts via org-gantt.el Bernhard Schmitz
2015-05-31 13:13 ` Axel Kielhorn
2015-06-01 12:51 ` Bernhard Schmitz
2015-06-01 15:26 ` Axel Kielhorn
2015-06-01 18:38 ` Axel Kielhorn
2015-06-02 8:42 ` Bernhard Schmitz
2015-06-01 11:16 ` Karl Voit
2015-06-02 8:15 ` Bernhard Schmitz
2015-06-03 15:13 ` Karl Voit
2015-06-02 8:38 ` Eric S Fraga
2015-06-03 15:17 ` Karl Voit
2015-06-05 8:20 ` Bernhard Schmitz
2015-06-20 12:46 ` Bernhard Schmitz [this message]
2015-06-25 8:04 ` Eric S Fraga
2015-11-09 15:02 ` Karl Voit
2015-08-05 0:00 ` Bastien Guerry
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=b2ed392aeee147368012ed5606a39c37@barcarole.visus.uni-stuttgart.de \
--to=bernhard.schmitz@vis.uni-stuttgart.de \
--cc=devnull@Karl-Voit.at \
--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).