Martin Rubey wrote:
Well if I could easily get access to parents/siblings/children from the .asy
file in a some more attractive way for me, that would make me happy and would
probably be the dead of current hyperdoc, since then hyperdoc(-similar) pages
could be created in the following way
.pamphlet (with aldordoc-like +++ descriptions) -->
.ao file -->
libaxiom.al
Having libaxiom.al then extract the .ao again -->
.asy (with +++ comments) -->
.tex (with the +++ comments like in ALLPROSE) -->
latex/pdflatex/htlatex that .tex files to get an API
descriptions in dvi/pdf/html form.
For the Spad files, this is rather easy and was described by Tim in a recent
email. Would this be good enough for you? In fact, asq does most of it already:
Try
asq -doc PI
Hmmm, that looks pretty much like a .asy file. (-fasy switch of aldor).
However, to replace hyperdoc, you would have to have one dvi file for each
operation and each constructor, which would probably be a burden for the
harddisk.
I don't know why you want to stick to .dvi files here.
I think that the proper format for the hyperdoc replacement is a
database of html chunks.
Of course a hyperdoc replacement would be something html-like.
Ralf
_______________________________________________
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
