From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode and Taskjuggler
Date: Sat, 13 Jul 2013 22:49:26 -0400 [thread overview]
Message-ID: <87d2qlj1op.fsf@gmail.com> (raw)
In-Reply-To: CA+M2ft_fHrODnhAtDoZDRxgMBrnRpo4iAdD0x9Ku7C8Ewj2Phw@mail.gmail.com
John Hendy <jw.hendy@gmail.com> writes:
> Just wanted to post and update that I finally put some more work into
> the Taskjuggler (tj3) documentation on Worg. Still haven't migrated
> over the export file, but added more about the available settings,
> pointed to some helpful tj3 documentation, and mapping tj3 syntax to
> Org property syntax.
>
> I was planning to use a simple home renovation project (which I am
> undergoing, hence my massive delays in contributing) as an example to
> walkthrough basic steps and task attributes.
>
> I can still create a tj3 compatible version of the official
> Taskjuggler tutorial in Org-mode format (or probably just modify the
> TJ v2.4.3 one that's used at the other Taskjuggler worg tutorial) as a
> more full capability example.
>
> Lastly, unless the default report definition is done, I'll include a
> reports.tji file with the default Taskjuggler report definition from
> their tutorial example as well.
>
> Feedback is welcome based on how the above sounds.
>
Sounds good to me. The org example blocks were coming out funny (at
least on the chromium browser) so I added commas in front of the
"headlines" (I also made them org src blocks, but I'm not sure that's
the right thing to do). In any case, they look better to me, but can you
take a look and make sure that I didn't screw anything up? Also the footnote
seems to be obsolete, but I didn't change it.
> - http://orgmode.org/worg/exporters/taskjuggler/ox-taskjuggler.html
>
> I noticed that this isn't seeming to be indexed by google. I moved it
> from the following location probably 2-3 months ago, but when I search
> "orgmode taskjuggler tj3," only the previous location comes up as a
> search results:
>
> - http://orgmode.org/worg/org-tutorials/org-taskjuggler3.html
>
> Is the dir structure too deep to get indexed?
>
>
> John
>
>
--
Nick
next prev parent reply other threads:[~2013-07-14 2:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-14 1:13 Org-mode and Taskjuggler John Hendy
2013-07-14 2:49 ` Nick Dokos [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-29 20:52 [Taskjuggler] Status of exporter Christian Egli
2013-05-02 20:18 ` Eric S Fraga
2013-05-03 10:20 ` Christian Egli
2013-05-03 14:38 ` Eric S Fraga
2013-05-03 15:19 ` Christian Egli
2013-05-03 20:40 ` Christian Egli
[not found] ` <51B5F967.1040905@dayspringpublisher.com>
2013-06-10 16:09 ` Org-mode and Taskjuggler Louis Turk
2013-06-11 8:46 ` Christian Egli
2013-06-11 12:20 ` John Hendy
2013-06-13 4:38 ` Louis Turk
2013-06-13 5:21 ` Nick Dokos
2013-06-14 20:21 ` Louis Turk
2013-06-14 20:31 ` Nick Dokos
2013-06-13 13:06 ` John Hendy
2013-06-13 15:06 ` Christian Egli
2013-06-14 21:29 ` Louis Turk
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=87d2qlj1op.fsf@gmail.com \
--to=ndokos@gmail.com \
--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).