as a widget outside of the
embedded browser.
That's ok if you don't mind implementing and maintaining two separate
implementations, one for online documentation access and one for local
documentation.
I would recommend against that.
--
--Per Bothner
p...@bothner.
Netsurf?
Dillo does not support JavaScript or frames, which would seem to preclude
(or at least complicate) the kind of functionality we are hoping for.
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
ip archive, and the domterm command (using libwebsockets) starts up a browser
window
with a URL pointing back at itself. When files are requested it can send them
to the browser as ‘Content-Encoding: gzip’, without having to uncompress them
first.
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
ng makeinfo convert texinfo to html
instead of info, and installing html in distributions.
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
o use html.
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
k at the Qt code for DomTerm at:
https://github.com/PerBothner/DomTerm/tree/master/qtdomterm
This handles creating a QtWebEngine window, menus, and bi-directional
communication with the JavaScript in the QtWebEngine window. It's not
super-compact, but it's quite reasonable. (The main C code for
process/pty management is in the lws-term directory.)
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
org/, which is a compact C-language http server.
DomTerm uses this to "serve" the JavaScript files to the browser,
and a revamped 'info' program could do the same.
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
