I had a similar idea once (before I knew about tj3). I modeled the graph
** node that comes after "node"
** node that also comes after "node"
So each node in a deeper level of the hierarchy would depend on its
parent. In addition, I could define properties to specify arbitrary
other dependencies ("blocks" and "depends").
org2dot < test.org
| dot -Tpdf -o test.pdf
On the other hand, I found out about tj3 and how it plays together with
Orgmode. I have a setup where I define my projects and resources in
Orgmode (which I find much nicer than directly in tj3).
In conclusion: The org file my single source file, from which tj3 source
and reports, PDF documents and graphviz dependency graphs are generated.
I wrote the program org2dot in Haskell, its here:
You would have to change it slightly because in tj3, the property names
"blocks" and "depends" have different names. You may also have to use
awk or so, to pre-process the org file to contain the task ids in the
header lines. This should not be too hard.
But I guess it's a lot to learn if you're new to Orgmode. Here is the
documentation for Orgmode tj3 export:
My Makefile rule to generate the tj3 file from Orgmode is:
%.tjp: %.org *.tjp.txt
emacs $< --batch -l
sed -i '1s/ nil / $* /' $@
cat leaves.tjp.txt reports.tjp.txt >> $@
It combines leaves and report specifications that reside in separate
files, not in the org file.
Hope that helps.
Am 26.08.20 um 05:08 schrieb gra...@harris.net.nz