Re: what is the status of the JavaScript reader?

[Per Bothner]

On 8/4/20 4:53 PM, Gavin Smith wrote:
> I guess what I am wondering is if it is good enough to distribute.  Have
> you tried the results with your manuals and did you think the results
> were good enough that you would use them for your websites?
>
> You would also gain the use of the index search feature and keyboard
> navigation.

I tried changing the Makefile for DomTerm to do:

$(MAKEINFO) -I=doc --html --split=section --no-number-sections --css-ref="style/domterm-1col.css" --css-ref="style/info.css" -c 
EXTRA_HEAD='<script src="style/modernizr.js" type="text/javascript"></script><script src="style/info.js" 
type="text/javascript"></script>' doc/DomTerm.texi -o web/

It seems to work tolerably well.  The URLs seems to be the same as before
(when using http:/https: - there are security reasons why it has different URLs 
for file:).

The result is viewable at https://per.bothner.com/tmp/DomTerm-txjs/
Compare the version using Docbook: https://domterm.org/
Some of the styling differences are no doubt due to different
class/element names, and may be trivial to fix, though I have not tried to do 
so.

The DomTerm-txjs is quite usable, though there are some things I'd like to fix.
Some can probably be fixed with some css tweaks; other with some pre-processing.

Some issues I noted:

* Various colors etc are different - but that can be fixed with CSS.

* The "front page" has an extra title heading I'd like to avoid.

* The "DomTerm home" link is missing in the navigation bar.

* I prefer not to have the navigation links at the top of each page (it's 
clutter),
but it looks like that can be easily fixed with CSS.

* For definitions, I prefer a style where the definition kind is at the right 
margin.
See https://domterm.org/Python-tips.html and scroll to dtutils.print_html .
They may be achievable with CSS; if not a JavaScript hook could be used.
Regardless, this is not a show-stopper.

* The Icon above the navigation bar is missing - don't know what would be 
needed to fix it.

* The Docbook version lends itself to bundling as an EPUB e-book.  I don't 
think that's
an option until the generated HTML is made more "structured" and 
xhtml-compatible
(as discussed earlier).  This is an issue for the Kawa manual, but currently 
not the DomTerm one.

Bottom line: I think it could be made acceptable (to me) with a few modest CSS 
and
other tweaks.

(I expect I would migrate the DomTerm manual first.  The Kawa manual would come 
later;
after we figure out what to do about EPUB support.)
--
        --Per Bothner
per@bothner.com   http://per.bothner.com/