emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bernhard Schmitz <Bernhard.Schmitz@vis.uni-stuttgart.de>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Testers / Feedback wanted: Gantt charts via org-gantt.el
Date: Tue, 2 Jun 2015 08:15:40 +0000	[thread overview]
Message-ID: <db9ac8b995a84d79993f17c435012f10@barcarole.visus.uni-stuttgart.de> (raw)
In-Reply-To: <2015-06-01T13-12-59@devnull.Karl-Voit.at>

Hi,

> Von: Karl Voit [mailto:devnull@Karl-Voit.at]
> 
> And accomplishing this, I personally would like to see that your
> method takes org-depend into consideration. Namely the properties
> BLOCKER and TRIGGER:(NEXT|TODO|STARTED). I plan my projects using
> mostly BLOCKER and TRIGGER:NEXT to express dependencies.

This should be possible (might take a while, and no promises), at least for those simple dependencies. More complicated things expressed via org-depend would require some serious effort.
I don't understand the TRIGGER:(NEXT) syntax, though. According to the org-depend documentation TRIGGER: requires an id or a chain-siblings string.
So if you can describe a consistent way that org-gantt should handle org-depend, then I might implement it (again, no promises), but as I have never used org-depend I don't know if whatever I could come up with would make sense.

Regards,
Bernhard

next prev parent reply	other threads:[~2015-06-02  8:15 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 [this message]
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
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=db9ac8b995a84d79993f17c435012f10@barcarole.visus.uni-stuttgart.de \
    --to=bernhard.schmitz@vis.uni-stuttgart.de \
    --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

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).