Mart Rotteveel wrote: > > First impressions of the HTML (after 1-2 minutes of reading and scrolling): > > > > - Font size is rather biggish. Maybe 10% smaller or so would be better and > > more in line with the average informative website? > > The font size is based on the default font size in your browser > settings. Would changing that setting be good enough for you?
Not really, because my default font size is simply the browser default (i.e. 'Ctrl-0'), and suits me fine on 90% of the sites I visit. If I set a smaller default, it will be too small for comfort on many other sites. I uploaded an example here: http://firebird.vinkenoog.nl/Fontgroottes_uitsnede.png where you can see, left to right: your rendering, the Firebird website and the BBC. The lowercase letter height is around 12% bigger on your site than on the other two; that of capitals 20% bigger than the Fb site and 10% bigger than the BBC. The Firebird site is still fine with me, althought near the lower limit. The Beeb is perfect (I think), and I imagine this size might be OK for many people. > > - I thought the horizontal margins around the main text were too small, but > > then I noticed that they grow if I widen the window. This is not what one > > expects in HTML, but it works. (However: could a minimum margin be imposed > > that is bigger that the current one?) > > This is pretty much standard today, this restricts the reading area to > about 50-70 characters wide is good for readability. Agreed. > Eg compare: > https://www.firebirdsql.org/file/documentation/drivers_documentation/java/4.0.x/release_notes.html#general-notes > with > https://www.firebirdsql.org/file/documentation/drivers_documentation/java/2.2.x/release_notes.html#general-notes Wow! Talk about small font sizes! :-) > I'll see if I can add a wider padding, but reducing the font-size would > already 'fix' this. Not if the padding was specified in ex units ;-) But more seriously: a 5-10% font size reduction would mean a relative margin widening of around the same percentage. I think 50-100% wider would be better, but of course youy have to see these things 'in action'. Mind you, I can live with both the font size and the margins as they are. > > - But I really don't like the way the ToC adjusts when you use the slider > > to scroll up and down. Stuff in the ToC rolls up and down, collapses and > > expands, and all this is animated. That draws your attention constantly to > > a place where it isn't needed. If there's an option to turn the animation > > off, > > I would prefer that. (The fact as such that the ToC follows the scrolling is > > of course very useful.) > > This is actually something that is not part of the standard asciidoc > output (see https://asciidoctor.org/docs/user-manual/ for an example > with a standard TOC). I added it because the TOC becomes a bit too big > in something like the language reference, and in the mono-html output > you will miss the section tocs we had in the old chunked html > (especially in chapters like "Built-in functions and Variables"). > > This is a trade-off between showing everything (or at least: 3 levels > deep in the current config), and being able to quickly navigate to a > specific chapter without having to scroll a lot in the TOC itself. I > think the annoying effect you notice is more pronounced by quickly > scrolling through it, than when you're actually reading a document or > consulting it as a reference. True. If you're just reading it's much less irritating. > I can't tweak much about this, except showing the three levels of the > TOC all the time. That kind of defeats the purpose why I added this in > the first place. And maybe I can tweak something about the animation of > the transition, but the current 300ms 'ease-in-out' animation applied > for expanding and collapsing is less fidgety than no delay to me, and > increasing the delay a lot further makes it seem sluggish, but will > reduce the jitter while scrolling very fast. I realize now that what irritates me most is that first something goes down (as the newly focused section is expanded) and than it goes up again (as the previously focused section is collapsed). And this also happens if you're not scrolling, bust just click somewhere in the ToC. I think I'd prefer this instantaneoulsy. However, this too is not a big issue. And one we can always explore later. Cheers, Paul _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
