Nice! I was able to do the following:<div><br></div><div>- grab your copy of org-taskjuggler.el and install it</div><div>- get the .org file here: <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://orgmode.org/manual/TaskJuggler-export.html">http://orgmode.org/manual/TaskJuggler-export.html</a></div>
<div><a href="http://orgmode.org/manual/TaskJuggler-export.html"></a>- export to a .tjp</div><div>- swap out the default export with the code below and run &quot;tj3 tj3-test.tjp&quot; and get a nice html report!</div><div>
--- If you&#39;re looking for a default tj3 export... perhaps start with what&#39;s below?</div><div><br></div><div>Great work!</div><div><br></div><div><br></div><div>John</div><div><br></div><div><br></div><div><br></div>
<div>The export code that creates quite a nice html report (from tj3 documentation)</div><div>--------------</div><div><div>navigator navbar {</div><div>  hidereport 0</div><div>}</div><div><br></div><div>macro TaskTip [</div>
<div>  tooltip istask() -8&lt;-</div><div>    &#39;&#39;&#39;Start: &#39;&#39;&#39; &lt;-query attribute=&#39;start&#39;-&gt;</div><div>    &#39;&#39;&#39;End: &#39;&#39;&#39; &lt;-query attribute=&#39;end&#39;-&gt;</div>
<div>    ----</div><div>    &#39;&#39;&#39;Resources:&#39;&#39;&#39;</div><div>    </div><div>    &lt;-query attribute=&#39;resources&#39;-&gt;</div><div>    ----</div><div>    &#39;&#39;&#39;Precursors: &#39;&#39;&#39;</div>
<div>    </div><div>    &lt;-query attribute=&#39;precursors&#39;-&gt;</div><div>    ----</div><div>    &#39;&#39;&#39;Followers: &#39;&#39;&#39;</div><div>    </div><div>    &lt;-query attribute=&#39;followers&#39;-&gt;</div>
<div>    -&gt;8-</div><div>]</div><div><br></div><div>textreport frame &quot;&quot; {</div><div>  header -8&lt;-</div><div>    == Accounting Software Project ==</div><div>    ----</div><div>    &lt;[navigator id=&quot;navbar&quot;]&gt;</div>
<div>    ----</div><div>  -&gt;8-</div><div>  footer &quot;----&quot;</div><div>  textreport index &quot;Overview&quot; {</div><div>    formats html</div><div>    center &#39;&lt;[report id=&quot;overview&quot;]&gt;&#39;</div>
<div>  }</div><div><br></div><div>  textreport &quot;Status&quot; {</div><div>    formats html</div><div>    center -8&lt;-</div><div>      &lt;[report id=&quot;status.dashboard&quot;]&gt;</div><div>      ----</div><div>      &lt;[report id=&quot;status.completed&quot;]&gt;</div>
<div>      ----</div><div>      &lt;[report id=&quot;status.ongoing&quot;]&gt;</div><div>      ----</div><div>      &lt;[report id=&quot;status.future&quot;]&gt;</div><div>    -&gt;8-   </div><div>  }</div><div><br></div>
<div>  textreport development &quot;Development&quot; {</div><div>    formats html</div><div>    center &#39;&lt;[report id=&quot;development&quot;]&gt;&#39;</div><div>  }</div><div><br></div><div>  textreport &quot;Deliveries&quot; {</div>
<div>    formats html</div><div>    center &#39;&lt;[report id=&quot;deliveries&quot;]&gt;&#39;</div><div>  }</div><div><br></div><div>  textreport &quot;ContactList&quot; {</div><div>    formats html</div><div>    title &quot;Contact List&quot;</div>
<div>    center &#39;&lt;[report id=&quot;contactList&quot;]&gt;&#39;</div><div>  }</div><div>  textreport &quot;ResourceGraph&quot; {</div><div>    formats html</div><div>    title &quot;Resource Graph&quot;</div><div>    center &#39;&lt;[report id=&quot;resourceGraph&quot;]&gt;&#39;</div>
<div>  }</div><div>}</div><div><br></div><div># A traditional Gantt chart with a project overview.</div><div>taskreport overview &quot;&quot; {</div><div>  header -8&lt;-</div><div>    === Project Overview ===</div><div>    </div>
<div>    The project is structured into 3 phases.</div><div>    </div><div>    # Specification</div><div>    # &lt;-reportlink id=&#39;frame.development&#39;-&gt;</div><div>    # Testing</div><div>    </div><div>    === Original Project Plan ===</div>
<div>  -&gt;8-</div><div>  columns hierarchindex,</div><div>          name, start, end, effort, duration, cost,</div><div>          revenue, chart { ${TaskTip} }</div><div>  # For this report we like to have the abbreviated weekday in front</div>
<div>  # of the date. %a is the tag for this.</div><div>  timeformat &quot;%a %Y-%m-%d&quot;</div><div>  loadunit days</div><div>  hideresource 1</div><div>  caption &#39;All effort values are in man days.&#39;</div><div>
<br></div><div>  footer -8&lt;-</div><div>    === Staffing ===</div><div>    </div><div>    All project phases are properly staffed. See [[ResourceGraph]] for</div><div>    detailed resource allocations.</div><div>    </div>
<div>    === Current Status ===</div><div>    </div><div>    The project started off with a delay of 4 days. This slightly affected</div><div>    the original schedule. See [[Deliveries]] for the impact on the</div><div>    delivery dates.</div>
<div>  -&gt;8-</div><div>}</div><div><br></div><div># Macro to set the background color of a cell according to the alert</div><div># level of the task.</div><div>macro AlertColor [</div><div>  cellcolor plan.alert = 0 &quot;#00D000&quot; # green</div>
<div>  cellcolor plan.alert = 1 &quot;#D0D000&quot; # yellow</div><div>  cellcolor plan.alert = 2 &quot;#D00000&quot; # red</div><div>]</div><div><br></div><div>taskreport status &quot;&quot; {</div><div>  columns wbs, name, start, end, effort, alert { tooltip plan.journal</div>
<div>  != &#39;&#39; &quot;&lt;-query attribute=&#39;journal&#39;-&gt;&quot; }, status</div><div><br></div><div>  taskreport dashboard &quot;&quot; {</div><div>    headline &quot;Project Dashboard (&lt;-query attribute=&#39;now&#39;-&gt;)&quot;</div>
<div>    columns name { title &quot;Task&quot; ${AlertColor} },</div><div>            resources { width 200 ${AlertColor} </div><div>                        start ${projectstart} end ${projectend} },</div><div>            alerttrend { title &quot;Trend&quot; ${AlertColor} },</div>
<div>            journalmessages { width 260 ${AlertColor} }</div><div>    hidetask ~hasalert(0)</div><div>    sorttasks alert.down</div><div>    period %{${now} - 1w} +1w</div><div>  }</div><div>  taskreport completed &quot;&quot; {</div>
<div>    headline &quot;Already completed tasks&quot;</div><div>  }</div><div>  taskreport ongoing &quot;&quot; {</div><div>    headline &quot;Ongoing tasks&quot;</div><div>  }</div><div>  taskreport future &quot;&quot; {</div>
<div>    headline &quot;Future tasks&quot;</div><div>  }</div><div>}</div><div><br></div><div># A list of tasks showing the resources assigned to each task.</div><div>taskreport development &quot;&quot; {</div><div>  headline &quot;Development - Resource Allocation Report&quot;</div>
<div>  columns hierarchindex, name, start, end, effort { title &quot;Work&quot; },</div><div>          duration, chart { ${TaskTip} scale day width 500 }</div><div>  timeformat &quot;%Y-%m-%d&quot;</div><div>  hideresource ~(isleaf() &amp; isleaf_())</div>
<div>  sortresources name.up</div><div>}</div><div><br></div><div># A list of all tasks with the percentage completed for each task</div><div>taskreport deliveries &quot;&quot; {</div><div>  headline &quot;Project Deliverables&quot;</div>
<div>  columns hierarchindex, name, start, end, note { width 150 }, complete,</div><div>          chart { ${TaskTip} } </div><div><br></div><div>  hideresource 1</div><div>}</div><div># A list of all employees with their contact details.</div>
<div>resourcereport contactList &quot;&quot; {</div><div>  headline &quot;Contact list and duty plan&quot;</div><div>  columns name,</div><div>          email { celltext 1 &quot;[mailto:&lt;-email-&gt; &lt;-email-&gt;]&quot; },</div>
<div>          chart { scale day }</div><div>  hideresource ~isleaf()</div><div>  sortresources name.up</div><div>  hidetask 1</div><div>}</div><div><br></div><div># A graph showing resource allocation. It identifies whether each</div>
<div># resource is under- or over-allocated for.</div><div>resourcereport resourceGraph &quot;&quot; {</div><div>  headline &quot;Resource Allocation Graph&quot;</div><div>  columns no, name, effort, rate, weekly { ${TaskTip} }</div>
<div>  loadunit shortauto</div><div>  # We only like to show leaf tasks for leaf resources.</div><div>  hidetask ~(isleaf() &amp; isleaf_())</div><div>  sorttasks plan.start.up</div><div>}</div><div>-----------------</div>
<br><div class="gmail_quote">On Mon, Nov 1, 2010 at 9:05 PM, Anthony Lander <span dir="ltr">&lt;<a href="mailto:anthonylander@yahoo.com">anthonylander@yahoo.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi everyone,<br>
<br>
Christian Egli and I have been having an off-list exchange about making a TaskJuggler3 exporter. In fact, Christian would like to change the current exporter to export to either TaskJuggler2 or TaskJuggler3, depending on a defcustom! We have quite a number of ideas in the pipeline now, and thought it would be best to move the discussion, and access to the source code, back onto the list.<br>

<br>
Christian has set up a github repository with the changes he is making here: <a href="http://github.com/egli/org-mode" target="_blank">http://github.com/egli/org-mode</a><br>
<br>
And the code I sent to Christian, which makes the exporter work with TJ3, and also introduces some bug fixes and new features is here: <a href="http://github.com/alander/org-taskjuggler3" target="_blank">http://github.com/alander/org-taskjuggler3</a>. Please note that this is different from Christian&#39;s code, and that he is the maintainer of the exporter that is part of org-mode. I needed something to work, so I spent an afternoon hacking until it did what I needed.<br>

<br>
If you are interested in the details, our e-mail exchange is reproduced below.<br>
<br>
  -Anthony<br>
<br>
<br>
------------------------8&lt;-------------------------<br>
<br>
        From:   <a href="mailto:christian.egli@sbs.ch" target="_blank">christian.egli@sbs.ch</a><br>
        Subject:        Re: [Orgmode] Re: TaskJuggler 3, revisited<br>
        Date:   October 19, 2010 5:29:42 AM GMT-04:00<br>
        To:     <a href="mailto:anthonylander@yahoo.com" target="_blank">anthonylander@yahoo.com</a><br>
        Cc:     <a href="mailto:emacs-orgmode@gnu.org" target="_blank">emacs-orgmode@gnu.org</a><br>
<br>
Hi Anthony<br>
<br>
Anthony Lander &lt;<a href="mailto:anthonylander@yahoo.com" target="_blank">anthonylander@yahoo.com</a>&gt; writes:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Please find attached a somewhat improved version of your TJ2 exporter,<br>
a drop-in replacement that exports to TJ3, and also a sample .org<br>
file.<br>
</blockquote>
<br>
This is all exciting stuff. It&#39;s a little hard to digest (many changes<br>
rolled into one, white space formatting changes that make it hard to find<br>
the real change, common lisp idioms which I&#39;m not familiar with). Let me<br>
get back to you with some questions and then we can discuss how to most<br>
easily merge the stuff.<br>
<br>
- Why did you compute the leafiness? I seem to have experienced that tj3<br>
 has a problem with zero effort tasks that aren&#39;t marked as milestones.<br>
 Is that the reason?<br>
<br>
- Why do you add a duration of 1d if the task has neither a duration, an<br>
 end, a period nor an effort? Shouldn&#39;t that be a milestone instead?<br>
<br>
- I see that there is a need to annotate a project with stuff such as<br>
 scenarios, etc and I was missing a way to have file specific reports<br>
 or other globals. Your additional tags solve that problem. However I&#39;m<br>
 a bit reluctant to add more magic tags that mark the trees in some<br>
 way. I was hoping to find a more general way for this problem. So far<br>
 I haven&#39;t found a good solution though.<br>
<br>
- I like the idea of the TJ drawer, but in the end you just seem to use<br>
 it for the project node and the globals node. So in essence they are<br>
 taskjuggler source code blocks (in disguise) which are tied to a<br>
 particular node. In fact they are not even really tied to a particular<br>
 node, especially in the case of the globals. This goes back to the<br>
 previous question about a good way to add file specific globals. Maybe<br>
 some kind taskjuggler specific export option is really what we are<br>
 looking for.<br>
<br>
As an aside, I think it&#39;s better to post the source code to the list.<br>
There might be other people interested in it and pitching in with<br>
opinions and improvements.<br>
<br>
Thanks<div class="im"><br>
-- <br>
Christian Egli<br>
Swiss Library for the Blind, Visually Impaired and Print Disabled<br>
Grubenstrasse 12, CH-8045 Zürich, Switzerland<br>
<br></div>
------------------------8&lt;-------------------------<br>
<br>
        From:   <a href="mailto:anthonylander@yahoo.com" target="_blank">anthonylander@yahoo.com</a><br>
        Subject:        Re: [Orgmode] Re: TaskJuggler 3, revisited<br>
        Date:   October 19, 2010 8:55:38 AM GMT-04:00<br>
        To:     <a href="mailto:christian.egli@sbs.ch" target="_blank">christian.egli@sbs.ch</a><br>
<br>
Hi Christian,<br>
<br>
<br>
On 10-Oct-19, at 5:29 AM, Christian Egli wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is all exciting stuff. It&#39;s a little hard to digest (many changes<br>
rolled into one, white space formatting changes that make it hard to find<br>
the real change, common lisp idioms which I&#39;m not familiar with). Let me<br>
get back to you with some questions and then we can discuss how to most<br>
easily merge the stuff.<br>
</blockquote>
<br>
Apologies for the big blob of changes - I was initially just trying to get stuff to work, and, well, just kept going. As for the spacing/formatting, I ran M-x indent-region RET on the whole file to get the formatting consistent. I know it makes diffing hard, though :(<br>

<br>
Is the unfamiliar idiom the backtick list with the ,variables in it, by chance?<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- Why did you compute the leafiness? I seem to have experienced that tj3<br>
has a problem with zero effort tasks that aren&#39;t marked as milestones.<br>
Is that the reason?<br>
- Why do you add a duration of 1d if the task has neither a duration, an<br>
end, a period nor an effort? Shouldn&#39;t that be a milestone instead?<br>
</blockquote>
<br>
Ah, sorry. This I should have documented. The problem is that TJ3 fails to compile the file if there is a leaf node with no computable end date. TJ2 happily ignored the situation, but TJ3 throws an error.  So the problem I&#39;m trying to solve is that as you are working on your project plan, it won&#39;t compile unless you put in a bunch of dummy estimates for the leaf nodes.<br>

<br>
I found it easier to let the exporter put them in, so that I don&#39;t always think to myself, &quot;did I put this in as a real estimate or just to make the compiler happy?&quot; Perhaps it would be better to change 1 day to 1 minute or 1 second to make it very obviously a dummy duration that is put in only to satisfy the compiler. And maybe even a comment in the exported file, too.<br>

<br>
Also, I hadn&#39;t thought of milestones. I think the code needs a bit of a fix because it needs to know that a milestone has zero effort, but won&#39;t cause the compiler to fail.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- I see that there is a need to annotate a project with stuff such as<br>
scenarios, etc and I was missing a way to have file specific reports<br>
or other globals. Your additional tags solve that problem. However I&#39;m<br>
a bit reluctant to add more magic tags that mark the trees in some<br>
way. I was hoping to find a more general way for this problem. So far<br>
I haven&#39;t found a good solution though.<br>
</blockquote>
<br>
I agree with you about the magic tags. I hate the feeling of reimplementing the entire TJ3 file format in org. That&#39;s asking to always be playing catch-up, and to always be missing features. I like very much the idea of &quot;borrowing&quot; features from org that make sense, and doing something useful on export. Examples are your % doneness of a task, and your &quot;ordered tasks in a hierarchy&quot; ideas. And in fact I added using the todo states and tags as flags so you can easily build tj reports that reference them (see the &quot;active&quot; gantt chart, for example).<br>

<br>
In the end, I felt the project needed a special marker because there are specific TJ3 features that go with it. And also, the globals need to go somewhere. I am also not thrilled with making all these tags, but I didn&#39;t have a better solution either.<br>

<br>
In any event, the TJ drawer is my attempt at a catch-all solution. It at least allows a user to use missing features without waiting for a development change. So for example, I personally will never use the accounting stuff, and would not be very motivated to add it to the exporter, but if someone needed it, they could put the required code in the TJ drawer, and they could still use the TJ exporter for their project instead of having to abandon org-mode entirely for one missing feature.<br>

<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- I like the idea of the TJ drawer, but in the end you just seem to use<br>
it for the project node and the globals node. So in essence they are<br>
taskjuggler source code blocks (in disguise) which are tied to a<br>
particular node. In fact they are not even really tied to a particular<br>
node, especially in the case of the globals. This goes back to the<br>
previous question about a good way to add file specific globals. Maybe<br>
some kind taskjuggler specific export option is really what we are<br>
looking for.<br>
</blockquote>
<br>
Interesting thought. I very much like the idea that you can do other things with your org-file than export it to taskjuggler. For example, keep actual notes in the file, and export it to other formats like html or LaTeX, for purposes other than project planning. Being able to say &quot;no, this is not a task&quot; in the task tree would be very useful. I don&#39;t know how to do it nicely either (yet).<br>

<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As an aside, I think it&#39;s better to post the source code to the list.<br>
There might be other people interested in it and pitching in with<br>
opinions and improvements.<br>
</blockquote>
<br>
That&#39;s a good idea. How about if we set up a git repository on github with the files, and then post the link on the mailing list? I worry that posting code and patches will badly confuse the patch manager software than grabs code from the mailing list. Also, if we&#39;re going to do that, I think we should put your email, and this reply to the list as well. Your thoughts?<br>

<br>
All the best,<br>
<br>
 -Anthony<br>
<br>
------------------------8&lt;-------------------------<br>
<br>
        From:   <a href="mailto:christian.egli@sbs.ch" target="_blank">christian.egli@sbs.ch</a><br>
        Subject:        Re: [Orgmode] Re: TaskJuggler 3, revisited<br>
        Date:   October 28, 2010 3:28:13 AM GMT-04:00<br>
        To:     <a href="mailto:anthonylander@yahoo.com" target="_blank">anthonylander@yahoo.com</a><br>
        Cc:     <a href="mailto:emacs-orgmode@gnu.org" target="_blank">emacs-orgmode@gnu.org</a><br>
<br>
Hi Anthony<br>
<br>
Anthony Lander &lt;<a href="mailto:anthonylander@yahoo.com" target="_blank">anthonylander@yahoo.com</a>&gt; writes:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is the unfamiliar idiom the backtick list with the ,variables in it,<br>
by chance?<br>
</blockquote>
<br>
No it was more stuff like `return&#39; and `return-from&#39;.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ah, sorry. This I should have documented. The problem is that TJ3<br>
fails to compile the file if there is a leaf node with no computable<br>
end date. TJ2 happily ignored the situation, but TJ3 throws an error.<br>
</blockquote>
<br>
OK, I understand. I managed to slowly integrate (some of) your changes.<br>
It should now generate milestones for nodes that cannot be scheduled and<br>
are leaf nodes. So basically it should export valid code for tj3 if you<br>
set org-export-taskjuggler-target-version to 3.0. Of course the report<br>
definitions in the defcustom org-export-taskjuggler-default-reports are<br>
not compatible with tj3 so you will need to change these.<br>
<br>
I have (or I guess rather had) some fondness for recursive functions, so<br>
I re-implemented your leafiness function recursively. However I ran into<br>
problems with max-lisp-eval-depth and it appears that recursion is not<br>
encouraged in Emacs lisp<br>
(<a href="http://www.gnu.org/s/emacs/manual/html_node/elisp/Compilation-Tips.html#Compilation-Tips" target="_blank">http://www.gnu.org/s/emacs/manual/html_node/elisp/Compilation-Tips.html#Compilation-Tips</a>).<br>
So I guess it&#39;s back to iterative style.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In any event, the TJ drawer is my attempt at a catch-all solution. It<br>
at least allows a user to use missing features without waiting for a<br>
development change. So for example, I personally will never use the<br>
accounting stuff, and would not be very motivated to add it to the<br>
exporter, but if someone needed it, they could put the required code<br>
in the TJ drawer, and they could still use the TJ exporter for their<br>
project instead of having to abandon org-mode entirely for one missing<br>
feature.<br>
</blockquote>
<br>
I like the drawer stuff and will integrate it.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Interesting thought. I very much like the idea that you can do other<br>
things with your org-file than export it to taskjuggler. For example,<br>
keep actual notes in the file, and export it to other formats like<br>
html or LaTeX, for purposes other than project planning.<br>
</blockquote>
<br>
Absolutely, I agree.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Being able to say &quot;no, this is not a task&quot; in the task tree would be<br>
very useful. I don&#39;t know how to do it nicely either (yet).<br>
</blockquote>
<br>
Hm, no this is not possible right now. Why would you want to do this?<br>
Maybe we could just mark it as a comment and make the exporter honor<br>
comments.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
How about if we set up a git repository on github<br>
with the files, and then post the link on the mailing list?<br>
</blockquote>
<br>
I set up a repo and pushed my changes to the code there<br>
(<a href="http://github.com/egli/org-mode" target="_blank">http://github.com/egli/org-mode</a>).<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think we should put your email, and this reply to the<br>
list as well.<br>
</blockquote>
<br>
Yes, I almost forgot. Would you mind doing that?<br>
<br>
Thanks<br>
Christian<div class="im"><br>
<br>
-- <br>
Christian Egli<br>
Swiss Library for the Blind, Visually Impaired and Print Disabled<br>
Grubenstrasse 12, CH-8045 Zürich, Switzerland<br>
<br></div>
------------------------8&lt;-------------------------<br>
<br>
        From:   <a href="mailto:anthonylander@yahoo.com" target="_blank">anthonylander@yahoo.com</a><br>
        Subject:        Re: [Orgmode] Re: TaskJuggler 3, revisited<br>
        Date:   October 31, 2010 11:45:34 AM GMT-04:00<br>
        To:     <a href="mailto:christian.egli@sbs.ch" target="_blank">christian.egli@sbs.ch</a><br>
<br>
<br>
On 10-Oct-28, at 3:28 AM, Christian Egli wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Anthony Lander &lt;<a href="mailto:anthonylander@yahoo.com" target="_blank">anthonylander@yahoo.com</a>&gt; writes:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is the unfamiliar idiom the backtick list with the ,variables in it,<br>
by chance?<br>
</blockquote>
<br>
No it was more stuff like `return&#39; and `return-from&#39;.<br>
</blockquote>
<br>
I see. Well, once you were explicitly requiring &#39;cl.... :) And as you discovered, without a tail-recursion optimizing compiler, recursive functions are prohibitively expensive in elisp. Once you are iterating, you need a way to exit iteration scopes before the end of the iteration.<br>

<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So basically it should export valid code for tj3 if you<br>
set org-export-taskjuggler-target-version to 3.0. Of course the report<br>
definitions in the defcustom org-export-taskjuggler-default-reports are<br>
not compatible with tj3 so you will need to change these.<br>
</blockquote>
<br>
Right. Or perhaps better, have different default reports for TJ2 or TJ3, which the exporter selects as appropriate.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Interesting thought. I very much like the idea that you can do other<br>
things with your org-file than export it to taskjuggler. For example,<br>
keep actual notes in the file, and export it to other formats like<br>
html or LaTeX, for purposes other than project planning.<br>
</blockquote>
<br>
Absolutely, I agree.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Being able to say &quot;no, this is not a task&quot; in the task tree would be<br>
very useful. I don&#39;t know how to do it nicely either (yet).<br>
</blockquote>
<br>
Hm, no this is not possible right now. Why would you want to do this?<br>
Maybe we could just mark it as a comment and make the exporter honor<br>
comments.<br>
</blockquote>
<br>
Yes, marking it as a comment is not a bad idea. The reason I want to do that goes with the idea of using the org file for additional purposes than just a task tree. So for example, I would like to be able to have nodes with meeting notes, or links to related files etc etc under a task. That way I am only maintaining one project document, not separate ones for notes, scheduling, etc. I think that is very much in the spirit of org-mode, which so heavily emphasizes sparse trees, agenda views etc as ways to tease out relevant information from an intermingled file.<br>

<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
How about if we set up a git repository on github<br>
with the files, and then post the link on the mailing list?<br>
</blockquote>
<br>
I set up a repo and pushed my changes to the code there<br>
(<a href="http://github.com/egli/org-mode" target="_blank">http://github.com/egli/org-mode</a>).<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think we should put your email, and this reply to the<br>
list as well.<br>
</blockquote>
<br>
Yes, I almost forgot. Would you mind doing that?<br>
</blockquote>
<br>
I&#39;ll do that, yes.<br>
<br>
Best regards,<br><font color="#888888">
<br>
 -Anthony</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Emacs-orgmode mailing list<br>
Please use `Reply All&#39; to send replies to the list.<br>
<a href="mailto:Emacs-orgmode@gnu.org" target="_blank">Emacs-orgmode@gnu.org</a><br>
<a href="http://lists.gnu.org/mailman/listinfo/emacs-orgmode" target="_blank">http://lists.gnu.org/mailman/listinfo/emacs-orgmode</a><br>
</div></div></blockquote></div><br></div>