From: Christian Egli <christian.egli@sbs.ch>
To: emacs-orgmode@gnu.org
Subject: Re: taskjuggler (tj3) export issues and proposals
Date: Thu, 02 Feb 2012 09:23:51 +0100 [thread overview]
Message-ID: <87d39xr6co.fsf@sbs.ch> (raw)
In-Reply-To: CA+M2ft8BAQNOcgZwRBOZP_EA=LEuesx_tOOC105_uVM8oT9j_w@mail.gmail.com
John Hendy <jw.hendy@gmail.com> writes:
>> First off let me say that I'm using the taskjuggler exporter with tj3,
>> so it should work.
>>
>
> This statement seems to indicate that org may work out of the box with tj3.
Well if you take it out of the box it doesn't work with tj3. You need to
adapt the target version and the default reports. I think it might be
time to change this since most distros do not have taskjuggler2.4
anymore (except Debian stable is still happily using it) and tj2.4
doesn't even run on Windows or Mac.
>> The exporter just makes the task_id locally unique. That's what tj
>> expects. From your usage I guess that you have a lot of tasks with the
>> same name (probably within different hierarchies). Both methods you
>> outline could be implemented. Which one is more general?
>>
>
> Maybe "parent_headline_task_headline"? But that gets tricking for:
>
> * Task Container
> ** Send product samples to X
> ** Send product samples to Y
> ** Send product samples to Z
>
> Append a number? My files are not [too] complex; perhaps the exporter
> should be done while thinking of how org might have worked for the
> Fedora tj example
> (http://www.taskjuggler.org/tj3/examples/Fedora-20/f-20.tjp).
I had a look at the Fedora tj example. This is using tj to the max. It
might not be a good use case for the tj exporter :-). But to understand
your use case, could you maybe send me some example org files of yours,
so I could look at them (off-list if you like)
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
next prev parent reply other threads:[~2012-02-02 8:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 4:59 taskjuggler (tj3) export issues and proposals John Hendy
2012-02-01 14:09 ` Christian Egli
2012-02-01 14:18 ` Rainer M Krug
2012-02-01 15:20 ` John Hendy
2012-02-01 15:54 ` Christian Egli
2012-02-01 17:47 ` John Hendy
2012-02-02 7:10 ` Christian Egli
2012-02-02 15:49 ` John Hendy
2012-02-02 16:08 ` OT: taskjuggler question [was: Re: taskjuggler (tj3) export issues and proposals] Nick Dokos
2012-02-02 16:22 ` John Hendy
2012-02-02 16:24 ` OT: taskjuggler question Christian Egli
2012-02-02 17:13 ` Nick Dokos
2012-02-01 18:36 ` taskjuggler (tj3) export issues and proposals Rainer M Krug
2012-02-01 15:07 ` John Hendy
2012-02-02 8:23 ` Christian Egli [this message]
2012-05-07 4:26 ` Eric S Fraga
2012-05-08 8:16 ` Bastien
2012-05-08 9:14 ` Eric Fraga
2012-05-08 14:36 ` John Hendy
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=87d39xr6co.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).