Re: [ANN] Exporter for taskjuggler

[Dan Davison <davison@stats.ox.ac.uk>]

Christian Egli <christian.egli@sbszh.ch> writes:
[...]
>> It would also be nice if repeated invocation of
>> org-export-as-taskjuggler-and-open on the same project didn't spawn
>> multiple TJ instances (TJ v2.4.3 ubuntu).
>
> Hm, yes. Good idea. Do you have an idea how this could be done easily in
> elisp?

Is this more the reponsibility of the application?  E.g. I just did
'firefox some.png' from the shell and it opened a new tab in a running
process. So maybe it's a question of checking whether / requesting that
the new ruby implementation has a way of telling it from the shell to
open (update?) a project in an already-running TJ process.

[...]
>> Make it work if `org-odd-levels-only' is in use:
>>
>> diff --git a/org-taskjuggler.el b/org-taskjuggler.el
>> index e887d33..e843dcd 100644
>> --- a/org-taskjuggler.el
>> +++ b/org-taskjuggler.el
>> @@ -309,7 +309,7 @@ the current node such as the headline, the level, todo state
>>  information, all the properties, etc."
>>    (let* ((props (org-entry-properties))
>>  	 (components (org-heading-components))
>> -	 (level (car components))
>> +	 (level (nth 1 components))
>>  	 (headline (nth 4 components))
>>  	 (parent-ordered (org-taskjuggler-parent-is-ordered-p)))
>>      (push (cons "level" level) props)
>
> Oh, OK, good catch. Does this also work if `org-odd-levels-only' is not
> in use?

Yes. C-h f org-heading-components says the second element differs from
the first only if org-odd-levels-only is set.

Dan