Ralf Hemmecke wrote:
> 
> I claim that I am basically finished with re-establishing the build of
> the hyperdoc documentation from the .htex files.
> 
> I've basically split into just two patches. The first one basically
> brings everything in place whereas the second one moves the releaseNotes
> and "Changes to Spad language" into ug15.htex.
> 
> https://github.com/hemmecke/fricas/commits/htexdoc
> 
> I have incorporated the relevant .htex files from NAGcdrom and removed
> the corresponding .ht files.
> 
> Some of the .help files will be generated and some where simply copied
> from NAGcdrom.
> 
> The glossary (gloss.ht, glossdef.text, glosskey.text) is regenerated
> from gloss.text.
> 
> The viewports are generated. The special mobius stuff has been replaced
> by a saddle picture that is anyway generated during the viewport generation.

What problem do you have with mobius picture?

> I've changed the configure.ac file to test whether the xvfb-run program
> is available. If it is, the viewports will be built automatically. If it
> isn't, then viewports build is delayed until one explicitly calls
> 
>   cd src/hyper; make MAYBE_VIEWPORTS=viewports
> 
> This will (as was before) pop up windows and makes working on the
> machine nearly impossible for a while. One can, of course, add "-j 8"
> to run the build process in parallel.
> 
> Actually, the input files
> 
> https://github.com/hemmecke/fricas/blob/f5f5030f8938f18cba6c9a17e234f405f9055563/src/hyper/Makefile.in#L296
> 
> UG_EXTRA_INPUT = arrows bouquet matrix newton ribbon vectors
> 
> could all be generated from ug15.htex, but I haven't bothered, because
> they already exist in .input.pamphlet form.
> 
> I hope you like it.

In general it looks good.  However I do not like generating .ht files
in 'src/hyper' directory. 'src/hyper' is for building HyperDoc,
building HyperDoc pages beside using HyperDoc programs has nothing
to do with building HyperDoc.  That is why I created the 'src/paste'
directory.  If you do not like 'src/paste' use 'src/htex' or create
different subdirectory, but please do not use 'src/hyper'.

Rule for 'gloss.ht' is unnecessarly complicated, see patch in
attachenent for simpler rule.  Also, it would be good to
avoid copy of 'gloss.text', this can be done by adding
pathname argument to 'buildGloss'.

> 
> PS:
> Maybe I should add the content of this mail into the commit message. ;-)

I prefer to keep commit messages short (basically one short sentence)
because from time to time I go trough all messages (or all messages
in some period, or all messages affecting given file) to find a
particular commit.  Longer messages mean that reading them will
take more time... Also, longer messages complicate
automatic formatting and consequently make list of commits harder
to read.  Slightly longer messages are apropriate
in ChangeLog, but again being concise is a virtue.


-- 
                              Waldek Hebisch
[email protected] 

-- 
You received this message because you are subscribed to the Google Groups 
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/groups/opt_out.


diff --git a/src/hyper/Makefile.in b/src/hyper/Makefile.in
index 43c84db..dcff075 100644
--- a/src/hyper/Makefile.in
+++ b/src/hyper/Makefile.in
@@ -371,18 +371,10 @@ coverex.ht: ${HTEXAMPLES_COVEREXHT_FILES}
         cat  ${HTEXAMPLES_COVEREXHT_FILES}\
        ) > $@
 
-# We must copy the scripts because reading them from ${interpsrcdir}
-# generates .clisp and .fasl files inside the original source dir.
-GLOSSARY_SCRIPTS=htcheck.boot c-doc.boot br-util.boot br-data.boot
-${GLOSSARY_SCRIPTS}: %: ${interpsrcdir}/%
-       cp $< $@
-
-gloss.ht: ${htsrcdir}/gloss.text ${GLOSSARY_SCRIPTS}
+gloss.ht: ${htsrcdir}/gloss.text
        cp $< ${AXIOM}
-       ( echo ')read htcheck.boot'; \
-         echo ')read c-doc.boot'; \
-         echo ')read br-util.boot'; \
-         echo ')read br-data.boot'; \
+       ( echo ')boot browserAutoloadOnceTrigger()'; \
+         echo ')boot oldCompilerAutoloadOnceTrigger()'; \
          echo ')boot buildGloss()') \
        | ${INTERPSYS}
 

Reply via email to