Re: js-info polishing

2021-05-04 Thread Per Bothner
On 5/2/21 2:16 PM, Gavin Smith wrote: I've noticed something else (sorry, don't know how hard it would be to fix). When on a page that has sub-sections in the same page (due to the level of "split"), the keyboard commands "n" and "p" don't work for the sub-sections that are in the same page. Fo

Re: js-info polishing

2021-05-03 Thread Gavin Smith
On Sun, May 02, 2021 at 03:09:19PM -0700, Per Bothner wrote: > > > On 5/2/21 2:16 PM, Gavin Smith wrote: > > I've noticed something else (sorry, don't know how hard it would be > > to fix). When on a page that has sub-sections in the same page (due > > to the level of "split"), the keyboard comm

Re: js-info polishing

2021-05-02 Thread Per Bothner
On 5/2/21 2:16 PM, Gavin Smith wrote: I've noticed something else (sorry, don't know how hard it would be to fix). When on a page that has sub-sections in the same page (due to the level of "split"), the keyboard commands "n" and "p" don't work for the sub-sections that are in the same page.

Re: js-info polishing

2021-05-02 Thread Gavin Smith
On Sun, May 02, 2021 at 10:17:43AM -0700, Per Bothner wrote: > > > On 5/2/21 10:10 AM, Gavin Smith wrote: > > I saw that you've commited a change to this but it is not reflected for > > me at > > > > https://per.bothner.com/tmp/Kawa-txjs-plain/style/info.js > > > > in the on_message function. >

Re: js-info polishing

2021-05-02 Thread Per Bothner
On 5/2/21 10:10 AM, Gavin Smith wrote: I saw that you've commited a change to this but it is not reflected for me at https://per.bothner.com/tmp/Kawa-txjs-plain/style/info.js in the on_message function. I'm confused about what happened, but should be fixed now. -- --Per Bothner p.

Re: js-info polishing

2021-05-02 Thread Gavin Smith
On Sun, May 02, 2021 at 08:26:14AM -0700, Per Bothner wrote: > > > On 4/30/21 4:06 AM, Per Bothner wrote: > > > > > > On 4/29/21 9:40 AM, Gavin Smith wrote: > > > Another problem: Navigate to > > > > > > https://per.bothner.com/tmp/Kawa-txjs-plain/index.html > > > > > > type "i" then "constan

Re: js-info polishing

2021-05-02 Thread Per Bothner
On 4/30/21 4:06 AM, Per Bothner wrote: On 4/29/21 9:40 AM, Gavin Smith wrote: Another problem: Navigate to https://per.bothner.com/tmp/Kawa-txjs-plain/index.html type "i" then "constant-fold", select the option in the menu, then pressĀ  Return. Then the page https://per.bothner.com/tmp/

Re: js-info polishing

2021-04-30 Thread Per Bothner
On 4/29/21 9:40 AM, Gavin Smith wrote: Another problem: Navigate to https://per.bothner.com/tmp/Kawa-txjs-plain/index.html type "i" then "constant-fold", select the option in the menu, then press Return. Then the page https://per.bothner.com/tmp/Kawa-txjs-plain/Application-and-Arguments-

Re: js-info polishing

2021-04-29 Thread Eli Zaretskii
> From: Gavin Smith > Date: Thu, 29 Apr 2021 17:30:42 +0100 > Cc: Per Bothner , bug-texinfo@gnu.org > > On Thu, Apr 29, 2021 at 07:15:27PM +0300, Eli Zaretskii wrote: > > One possible aspect for improvement: the way the input field for Index > > search is placed it obscures other text, and there

Re: js-info polishing

2021-04-29 Thread Per Bothner
On 4/29/21 9:30 AM, Gavin Smith wrote: On Thu, Apr 29, 2021 at 07:15:27PM +0300, Eli Zaretskii wrote: One possible aspect for improvement: the way the input field for Index search is placed it obscures other text, and there doesn't seem to be a way of getting rid of it if I decide not to type

Re: js-info polishing

2021-04-29 Thread Gavin Smith
On Thu, Apr 29, 2021 at 08:58:47AM -0700, Per Bothner wrote: > Please try https://per.bothner.com/tmp/Kawa-txjs-plain/index.html > It has an index. The 'i' command works seems to work nicely > (after fixing one minor typo). > -- > --Per Bothner > p...@bothner.com http://per.bothner.com/ >

Re: js-info polishing

2021-04-29 Thread Gavin Smith
On Thu, Apr 29, 2021 at 08:56:16AM -0700, Per Bothner wrote: > I implemented the following. > Pleae try https://per.bothner.com/tmp/Kawa-txjs-plain/index.html > > This uses default texinfo styling, without any Kawa/DomTerm-specific tweaks. > Note the "Hide sidebar" text is now vertical, which I th

Re: js-info polishing

2021-04-29 Thread Gavin Smith
On Thu, Apr 29, 2021 at 07:15:27PM +0300, Eli Zaretskii wrote: > One possible aspect for improvement: the way the input field for Index > search is placed it obscures other text, and there doesn't seem to be > a way of getting rid of it if I decide not to type anything into that > field. You get r

Re: js-info polishing

2021-04-29 Thread Eli Zaretskii
> Cc: bug-texinfo@gnu.org > From: Per Bothner > Date: Thu, 29 Apr 2021 08:58:47 -0700 > > On 4/27/21 12:15 PM, Eli Zaretskii wrote: > > It looks like the manual at those URLs doesn't have an Index? If so, > > would it be possible to set up a manual with one or more indices, so > > that the index

Re: js-info polishing

2021-04-29 Thread Per Bothner
On 4/27/21 12:15 PM, Eli Zaretskii wrote: It looks like the manual at those URLs doesn't have an Index? If so, would it be possible to set up a manual with one or more indices, so that the index search could be test-driven? Please try https://per.bothner.com/tmp/Kawa-txjs-plain/index.html I

Re: js-info polishing

2021-04-29 Thread Per Bothner
I implemented the following. Pleae try https://per.bothner.com/tmp/Kawa-txjs-plain/index.html This uses default texinfo styling, without any Kawa/DomTerm-specific tweaks. Note the "Hide sidebar" text is now vertical, which I think looks nicer. On 4/27/21 2:14 PM, Gavin Smith wrote: On Tue, Apr

Re: js-info polishing

2021-04-27 Thread Gavin Smith
On Tue, Apr 27, 2021 at 12:43:22PM -0700, Per Bothner wrote: > So if I understand you correctly, you would prefer: > * If the sidebar is hidden, the only way to show it is to click > on the "Show sidebar" button. (Perhaps we could add a keybinding as well.) > * Navigating by clicking in the sideba

Re: js-info polishing

2021-04-27 Thread Per Bothner
On 4/27/21 12:15 PM, Eli Zaretskii wrote: It looks like the manual at those URLs doesn't have an Index? If so, would it be possible to set up a manual with one or more indices, so that the index search could be test-driven? I'll try building the Kawa manual (which has an index) this way. It

Re: js-info polishing

2021-04-27 Thread Per Bothner
On 4/27/21 11:27 AM, Gavin Smith wrote: One small problem (I didn't check if it was a problem before or not) is that if you click on a link in the table of contents for a section it opens in a new browser tab. For example, click on "Architecture Notes" and then "Automatic Input Mode" in the m

Re: js-info polishing

2021-04-27 Thread Eli Zaretskii
> From: Gavin Smith > Date: Tue, 27 Apr 2021 19:27:50 +0100 > Cc: Texinfo > > On Tue, Apr 27, 2021 at 09:59:59AM -0700, Per Bothner wrote: > > I didn't get any feedback on changes mentioned in my 3/22 message, > > but checked it in belatedly just now > > > > To see the effect see > > https://pe

Re: js-info polishing

2021-04-27 Thread Gavin Smith
On Tue, Apr 27, 2021 at 09:59:59AM -0700, Per Bothner wrote: > I didn't get any feedback on changes mentioned in my 3/22 message, > but checked it in belatedly just now > > To see the effect see > https://per.bothner.com/tmp/DomTerm-txjs-plain (default GNU styling) > or:https://per.bothner.com/tmp

Re: js-info polishing

2021-04-27 Thread Per Bothner
I didn't get any feedback on changes mentioned in my 3/22 message, but checked it in belatedly just now To see the effect see https://per.bothner.com/tmp/DomTerm-txjs-plain (default GNU styling) or:https://per.bothner.com/tmp/DomTerm-txjs (DomTerm styling) -- --Per Bothner p...@bothner.co

Re: js-info polishing

2021-03-22 Thread Per Bothner
On 3/22/21 12:33 PM, Gavin Smith wrote: Do you have the same problem when using the DomTerm styling? No. Now that is strange ... Perhaps something in the DomTerm styling fixes whatever the problem is? Might be painful to debug (though I do have some old versions of Electron I could use a

Re: js-info polishing

2021-03-22 Thread Gavin Smith
On Mon, Mar 22, 2021 at 6:54 PM Per Bothner wrote: > > > > On 3/22/21 11:33 AM, Gavin Smith wrote: > > On Mon, Mar 22, 2021 at 6:13 PM Per Bothner wrote: > >> There should be a triple-right-arrow in a button-box in the top-left > >> of the page. If you're not seeing that, perhaps it's a font iss

Re: js-info polishing

2021-03-22 Thread Per Bothner
On 3/22/21 11:33 AM, Gavin Smith wrote: On Mon, Mar 22, 2021 at 6:13 PM Per Bothner wrote: There should be a triple-right-arrow in a button-box in the top-left of the page. If you're not seeing that, perhaps it's a font issue. When you see the sidebar with the "Hide sidebar" text, there sho

Re: js-info polishing

2021-03-22 Thread Gavin Smith
On Mon, Mar 22, 2021 at 6:13 PM Per Bothner wrote: > There should be a triple-right-arrow in a button-box in the top-left > of the page. If you're not seeing that, perhaps it's a font issue. > When you see the sidebar with the "Hide sidebar" text, there should be > a triple-left-arrow above the t

Re: js-info polishing

2021-03-22 Thread Per Bothner
On 3/22/21 10:46 AM, Gavin Smith wrote: On Mon, Mar 22, 2021 at 5:02 PM Per Bothner wrote: Please try: https://per.bothner.com/tmp/DomTerm-txjs (DomTerm styling) https://per.bothner.com/tmp/DomTerm-txjs-plain (default info styling) A couple things I noticed: On the second link, once you c

Re: js-info polishing

2021-03-22 Thread Gavin Smith
On Mon, Mar 22, 2021 at 5:02 PM Per Bothner wrote: > Please try: > https://per.bothner.com/tmp/DomTerm-txjs (DomTerm styling) > https://per.bothner.com/tmp/DomTerm-txjs-plain (default info styling) A couple things I noticed: On the second link, once you click to hide the sidebar there is no way

Re: js-info polishing

2021-03-22 Thread Per Bothner
On 2/23/21 2:46 PM, Gavin Smith wrote: If your changes are just for the hide/show button I think that is a good feature to have although I think it would be better to have a less obtrusive button. It would be nicer to have a little arrow that you click on to do it, which is more like similar int

Re: js-info polishing

2021-02-24 Thread Per Bothner
On 2/23/21 2:46 PM, Gavin Smith wrote: If your changes are just for the hide/show button I think that is a good feature to have although I think it would be better to have a less obtrusive button. It would be nicer to have a little arrow that you click on to do it, which is more like similar int

Re: js-info polishing

2021-02-23 Thread Gavin Smith
On Tue, Feb 23, 2021 at 02:29:04PM -0800, Per Bothner wrote: > It seems the problems Gavin reported were with domterm-specfic > "extra styling", but using the plan "info.css" works ok. > So should I check in the changes I made to info.js/info.css? > I can leave out the special styling rules for nar

Re: js-info polishing

2021-02-23 Thread Per Bothner
It seems the problems Gavin reported were with domterm-specfic "extra styling", but using the plan "info.css" works ok. So should I check in the changes I made to info.js/info.css? I can leave out the special styling rules for narrow windows, for now, if you think that is best. -- --Per Bo

Re: js-info polishing

2021-02-21 Thread Per Bothner
On 2/21/21 2:52 AM, Gavin Smith wrote: Version 80.0.3987.87 (Official Build) Built on Ubuntu , running on LinuxMint 19.2 (64-bit) I was able to find and download Chromium 80.0.3987.0 (Developer Build) (64-bit). Everything seems to work fine for me. No wobbling. Sigh. The hide/show sidebar

Re: js-info polishing

2021-02-21 Thread Gavin Smith
On Sat, Feb 20, 2021 at 10:03:49PM -0800, Per Bothner wrote: > I think I've gotten my changes to the js-info reader to a state where it > can be checked in. See attachment. > > In addition to the a "Hide sidebar"/"Show sidebar" button (lower left), > there is also magic to handle narrows screen b

Re: js-info polishing

2021-02-21 Thread Gavin Smith
On Sat, Feb 20, 2021 at 10:03:49PM -0800, Per Bothner wrote: > I think I've gotten my changes to the js-info reader to a state where it > can be checked in. See attachment. > > In addition to the a "Hide sidebar"/"Show sidebar" button (lower left), > there is also magic to handle narrows screen b

js-info polishing

2021-02-20 Thread Per Bothner
I think I've gotten my changes to the js-info reader to a state where it can be checked in. See attachment. In addition to the a "Hide sidebar"/"Show sidebar" button (lower left), there is also magic to handle narrows screen better, including auto-hide of the sidebar. * js/info.js: Add