On 12/24/24 9:50 AM, Gavin Smith wrote:
I mentioned info.js already in TODO.HTML.
However, this system is only appropriate for online manuals, not for
locally installed manuals. The reason for this is that it only handles
one manual at a time and does not handle searching for a manual.
I haven't seen that before - and I disagree with it. It is perfectly well
suited for browsing local manuals. When I read an manual, it is seldom
that I need to jump between manuals. If you need to handle/search for
manuals, that could probably be implemented without too much pain.
Certainly, an embedded browser such WebKitGTK can register a hook
to resolved a cross-manual reference or search, fairly easily.
Basically embedding info.js is just an unnecessary complication. Implementing
everything again is not such a big problem (and it should all be done
already - assuming the program compiles with recent WebKitGTK, which
I haven't checked).
Well, js-info does handle some non-trivial operations, primarily
navigation, updating side panels, and more. Though perhaps not
in the same way Yelp wants things. The same probably applies
the WebKitGTK-based info reader - it is unclear how much of that
would be useful to Yelp.
I already have a sketchy understanding of how info.js actually
works - adding hooks for WebKitGTK could push it into the realms of
unmaintainability.
I do wish Matthieu hadn't changed to js-info to use this hard-to-understand
event-based pattern. I am not convinced it added anything. However,
adding hooks that can be be overridden by an embedding browser would be
more local and modest.
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
