On 12 February 2016 at 08:15, Per Bothner <[email protected]> wrote: > We already have a reader that can read html files - it's called a web > browser. > We have to clarify what we want from a "graphical documentation viewer" > *beyond* what we have. If it the keyboard-centric UI - if so, the simplest > (and maybe best) solution is JavaScript and event handlers.
Here's an attempt at a list: * Keyboard-centric UI * Fast, responsive UI * Index search, both when program is first invoked and during interactive use * Search for files in several directories, both when program (... ditto) * Search a manual with regular expressions. * Other searching improvements (may already exist in some web browsers): The "next match" key to go to the next match below the currently displayed part, instead of jumping back up the page to the last match that hasn't been highlighted yet. Skip current screen when going to next match, in order to display a screen-full of matches at a time. * Search under a unit of a manual, for example search only in one chapter or section
