emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Egli <christian.egli@sbs.ch>
To: Anthony Lander <anthonylander@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: TaskJuggler 3, revisited
Date: Tue, 19 Oct 2010 11:29:42 +0200	[thread overview]
Message-ID: <87vd4ymsxl.fsf@saadawi.sbszh.ch> (raw)
In-Reply-To: <98BDDE23-2AA0-4B2A-B089-688F7BC46A49@yahoo.com> (Anthony Lander's message of "Mon, 18 Oct 2010 12:59:16 -0400")

Hi Anthony

Anthony Lander <anthonylander@yahoo.com> writes:

> Please find attached a somewhat improved version of your TJ2 exporter,
> a drop-in replacement that exports to TJ3, and also a sample .org
> file. 

This is all exciting stuff. It's a little hard to digest (many changes
rolled into one, white space formatting changes that make it hard to find
the real change, common lisp idioms which I'm not familiar with). Let me
get back to you with some questions and then we can discuss how to most
easily merge the stuff.

- Why did you compute the leafiness? I seem to have experienced that tj3
  has a problem with zero effort tasks that aren't marked as milestones.
  Is that the reason?

- Why do you add a duration of 1d if the task has neither a duration, an
  end, a period nor an effort? Shouldn't that be a milestone instead?

- I see that there is a need to annotate a project with stuff such as
  scenarios, etc and I was missing a way to have file specific reports
  or other globals. Your additional tags solve that problem. However I'm
  a bit reluctant to add more magic tags that mark the trees in some
  way. I was hoping to find a more general way for this problem. So far
  I haven't found a good solution though.

- I like the idea of the TJ drawer, but in the end you just seem to use
  it for the project node and the globals node. So in essence they are
  taskjuggler source code blocks (in disguise) which are tied to a
  particular node. In fact they are not even really tied to a particular
  node, especially in the case of the globals. This goes back to the
  previous question about a good way to add file specific globals. Maybe
  some kind taskjuggler specific export option is really what we are
  looking for.

As an aside, I think it's better to post the source code to the list.
There might be other people interested in it and pitching in with
opinions and improvements.

Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland

  parent reply	other threads:[~2010-10-19  9:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-09  1:24 TaskJuggler 3, revisited John Hendy
2010-10-09 11:04 ` Detlef Steuer
2010-10-09 19:25   ` John Hendy
2010-10-14  6:24   ` Eric S Fraga
2010-10-18 14:54     ` Christian Egli
2010-10-18 17:46       ` Eric S Fraga
2010-10-09 13:00 ` Anthony Lander
2010-10-18 14:52   ` Christian Egli
2010-10-18 15:45     ` Louis Turk
2010-10-18 16:55     ` Anthony Lander
     [not found]     ` <98BDDE23-2AA0-4B2A-B089-688F7BC46A49@yahoo.com>
2010-10-19  9:29       ` Christian Egli [this message]
     [not found]         ` <0EBF5950-179C-44CC-958C-EB9CF06A44AF@yahoo.com>
2010-10-28  7:28           ` Christian Egli
2010-10-29 15:07 ` Christian Egli

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:

  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=87vd4ymsxl.fsf@saadawi.sbszh.ch \
    --to=christian.egli@sbs.ch \
    --cc=anthonylander@yahoo.com \
    --cc=emacs-orgmode@gnu.org \


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