From: Shelagh Manton <email@example.com>
Subject: Re: org and taskjuggler
Date: Tue, 16 Dec 2008 03:52:30 +0000 (UTC) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Mon, 15 Dec 2008 11:37:07 +0100, Christian Egli wrote:
> Shelagh Manton <email@example.com> writes:
>> One of the set tasks for the project scenario is to produce a Gantt
>> Or perhaps someone knows another way to get a Gantt chart out of
>> org-mode data.
> I'm using a very hackish "works-for-me" python script that converts a
> tsv export from an org-mode file to a taskjuggler file. Probably has
> lots of implizit assumptions which not even I remember.
> The basic work-flow is to create your hierarchy of tasks, add some
> effort estimates and some other properties, export this to a csv and run
> the attached python script on it. This will generate a taskjuggler
> include file (tji) which can be used in a main taskjuggler file (tjp).
> You could use the following Makefile snippet to automate the process:
> projectPlan.csv: projectPlan.org
> $(EMACS) -batch \
> -eval "(progn (find-file \"$<\") (re-search-forward \"^|
> (org-table-export \"$@\"))" -kill
> projectPlan.tji: projectPlan.csv
> $(CSV2TASKJUGGLER) < $< > $@
> projectPlan.taskreport.html: projectPlan.tjp projectPlan.tji
> $(TASKJUGGLER) $<
> Attached is the python script, an example org file and an example for a
> tjp file. Let me know if this works for you.
> I meant to write a tutorial about this but you know how it is. Maybe you
> could write one as you get this to work :-)
> Hope this helps
Oh very interesting. I know it will take me a while but I will look at
this closely to understand what is happening.
Another think I'm slowly working through is to understand etask which
uses LaTeX and pstricks to make a Gantt chart.
prev parent reply other threads:[~2008-12-16 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 20:36 org and taskjuggler Shelagh Manton
2008-12-15 10:37 ` Christian Egli
2008-12-16 3:52 ` Shelagh Manton [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).