From: John Hendy <jw.hendy@gmail.com>
To: Christian Egli <christian.egli@sbs.ch>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: [ANN] TaskJuggler ported to new export framework
Date: Mon, 4 Mar 2013 16:06:35 -0600 [thread overview]
Message-ID: <CA+M2ft_26h1BHUYHaf1ekA=F-PF4zB5_nuXTFM-MXyC-kEFYGg@mail.gmail.com> (raw)
In-Reply-To: <87txorqm77.fsf@sbs.ch>
On Mon, Mar 4, 2013 at 8:22 AM, Christian Egli <christian.egli@sbs.ch> wrote:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>>>> If the Worg page about TaskJuggler needs some update, please feel
>>>> free to go ahead or ask some help on the list.
>>>
>>> It does. I'll see what I can do.
>>
>> Does it? Even though the internals have been rewritten, it shouldn't
>> change anything to syntax.
>>
>> Did I miss something?
>
> Sorry, this is completely orthogonal to the new exporter. These are
> changes that should have been on the worg page before. E.g. For a while
> the exporter supported tj3. This fact was never properly publizized and
> the worg page still shows screen shots with tj2.
Agreed -- there are some threads I may have started or at least
contributed to about using with tj3. I've still been using it (in
fact, just today without even seeing this) and can voice some issues I
had. I had to change some variables to work properly, and even if the
syntax would work with tj3, the default report never has.
You need a report definition that's tj3 compatible saved to
reports.tji and then set Org to use "include reports.tji" for the
report definition.
- This thread has some helpful stuff:
http://comments.gmane.org/gmane.emacs.orgmode/51814
I volunteer to help update Worg, if desired. I've been using emacs to
just write the .tjp directly, but wanted to switch to using the actual
Orgmode format for easier rearranging. I can go through that process
and document stuff along the way and send it to the list if that would
be helpful, or just push it to Worg. From monitoring tj a bit over the
past year or two, I'd suggest just using v3.0 as that's what all the
development is going toward. Or is there still compelling reason to
keep v2.4?
John
>
> Thanks
> Christian
>
> --
> Christian Egli
> Swiss Library for the Blind, Visually Impaired and Print Disabled
> Grubenstrasse 12, CH-8045 Zürich, Switzerland
>
> -----
> Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter http://online.sbs.ch
>
next prev parent reply other threads:[~2013-03-04 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 23:38 [ANN] TaskJuggler ported to new export framework Nicolas Goaziou
2013-02-22 8:12 ` Bastien
2013-03-04 12:59 ` Christian Egli
2013-03-04 13:58 ` Nicolas Goaziou
2013-03-04 14:22 ` Christian Egli
2013-03-04 18:59 ` Bastien
2013-03-04 22:06 ` John Hendy [this message]
2013-03-14 2:36 ` Bastien
2013-03-25 23:30 ` 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='CA+M2ft_26h1BHUYHaf1ekA=F-PF4zB5_nuXTFM-MXyC-kEFYGg@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=christian.egli@sbs.ch \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).