some overhaul issues

[David W. Farmer]

I am starting a new thread about the overhaul branch, as a
catch-all for issues I am encountering.

Currently the main content of a page (everything below the masthead
and navbar, and to the right of the footer), is in a div#content .

In overhaul, we have made some changes:

"ptx-content" instead of "content".
(a reasonable change, to avoid conflict with outside css)

A preference for class names instead of ids
(even when we only expect one object to have that class/id)

So, div#content became div.ptx-content .

Now we have a problem, because the "skip to main content" link
can't go to the main content, because the main content has a
class, not an id.

I can change the class to an id, and change 1000 lines of css
(because we also decided to have almost every css selector for
the main content to start with .ptx-content).

Please say something soon if you have a better idea.

Regards,

David

[Alex Jordan]

Is there a reason not to have both? Add back the id, leaving the class in place. Then the link will work and no css editing needed. 

--
You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/a0a63e3d-7438-2a40-722c-c13b2d4a102b%40aimath.org.

[Rob Beezer]

> Please say something soon if you have a better idea.

> A preference for class names instead of ids

Key word being "preference"? Why not have an @id for this special case? The
exception to the rule. Make it obscure:

id="the-place-we-skip-to"

It'd be an easy XSL change.

I can't recall if the class-preference was a React thing.

There is a "no" list for @xml:id values to avoid clashes, that was part of my
rationale for encouraging a *preference* for class names.

Volker Sorge yesterday sent me some accessibility items, from real-world
testing. One was:

> Autofocus main content after selection from toc

which I do not 100% understand, but it seems highly-related.

Rob

> Regards,
>
> David
>

[David W. Farmer]

What is the emoji for smack-palm-on-forehead?

Thank you for the (obvious, after you see it) suggestion.

David

> To view this discussion on the web visithttps://groups.google.com/d/msgid/pretext-dev/CA%2BR-jrc13wAARn4Kq1keM8osz36BcW%3DteapEkjd-3Tt025onOQ%40mail.gmail
> .com.
>
>

[Thomas Shemanske]

This question is probably orthogonal to current trends, but I suspect that when overhaul is released, it may spur a bit more experimentation from users.

In particular, it would be natural for someone to tweak CSS parameters on outer styling.  Once someone familiarizes themselves with David's CSS, it would be easy to override certain items to experiment with a local CSS file loaded after the standard styling.  If I recall correctly, older versions of PreTeXt had a hook for a developer CSS file.  

The point, finally, is whether it is possible to add a line in the publication file for HTML which gives a local path for a CSS file to be loaded.

Cheers,

Tom

[David W. Farmer]

Dear Tom,

I was thinking we need at least 3 options for the CSS:

1) From the server (i.e., what we have now)

2) Compressed and shipped with the HTML files, so offline viewing
is possible

3) Shipped with the HTML files in their expanded form, so that
it is easy for more people to do development.

Because we did not have 3, you had to jump through hoops and
create a complicated setup in order to do your CRC work.

If we had 3) now, it can serve the purpose of 2). When we get
to the React part of the overhaul, we can do 2) properly.

Regards,

David

> To view this discussion on the web visithttps://groups.google.com/d/msgid/pretext-dev/d65a97e2-c158-4385-92a2-6ac551485c87n%40googlegroups.co
> m.
>
>

[Rob Beezer]

Not disputing anything David said, but adding on.

Right now on overhaul, we will still load a "developer.css" file that allows you
to add to the existing cascade. But you gotta set the string parameter
debug.developer.css to "yes" to ge that action.

We also have the string parameter html.css.extra which is a comma- or space-
separated list of filenames. That comes after stock CSS and before developer.css.

String parameters for authors and publishers are nearly expunged. (Today!?)
They will live on for developers. Once off overhaul we can rationalize all
this, and if reminded, I could start documenation of long-running backdoors for
devlopers in the part of The Guide already in place for this sort of thing.

I seem to be going backwards. I should have started with the primary supported
way to *choose* CSS

Section 29.6: Styling
https://pretextbook.org/doc/guide/html/online-style.html#online-style

where in the code, it assumes the same server as "everything else". In other
words, one *could* host stock PreTeXt CSS on a server (localhost?), mimic the
directory structure at pretextbook.org and provide four or five files
targeting parts of the UI. See the XSL template whose name is simply "css".

Which seems to answer my question on another thread about parameters versus
variables.

Sorry this is a bit disjointed. I should be more familiar with all this.

Rob

[Rob Beezer]

Dear David,

I plan to make three betas this weekend using overhaul and the latest master
branch, so folks can also render their own projects next week with the latest -
before we make overhaul mainstream. Any idea on when would be best? I've got
time, but also have a few other things happening for the long weekend.

Rob

[David W. Farmer]

Dear Rob,

I have been building my latest project from the overhaul branch,
with everything looking okay except for a couple CSS tweaks (which
for some reason look different than the recent betas you made).

There is some JavaScript work I'd like to do, but I don't think
that requires different HTML markup. So, I think we may be ready
for an overhaul/main branch where we ask people to build, look
for anomalies, and post so that others can take a look.

I am happy to work from the examples that people post, although
it is always good to have whatever betas you can create.

Regards,

David

> https://groups.google.com/d/msgid/pretext-dev/cbc654ac-7d9a-7eaf-5035-bb8340d55da2%40ups.edu.
>
>

[Rob Beezer]

Thanks, David! I'll see about betas and trial-build instructions this afternoon.

Rob

[Rob Beezer]

The "offical" Pretext repository, my personal repository (rbeezer/pretext) with
the "overhaul" branch, and my local clone of my personal repository, are all
up-to-date and synced with one another. Betas below are built with my local clone.


Sample article: "default" style, "default" CSS files
https://pretextbook.org/beta/2022-11-28-overhaul-default

Sample article: "oscarlevin" style, "default" CSS files
https://pretextbook.org/beta/2022-11-28-overhaul-oscarlevin

Sample article: "default" style, "crc" CSS files
https://pretextbook.org/beta/2022-11-28-overhaul-crc

Sample book, with "structural" parts: "default" style, "default" CSS files
https://pretextbook.org/beta/2022-11-28-overhaul-book-parts


Some things that require a "base URL" are broken due to the alternate hosting
(such as Asymptote 3D images). And the "publication-oscarlevin.xml" publication
file is raising errors that I've not debugged. It is *not* the actual style
itself, but some other variation in the publication file (some circular variable
creation, I think).

Next message will have plans and a call for participation.

Rob

[Thomas Shemanske]

A small item on https://pretextbook.org/beta/2022-11-28-overhaul-crc

The first note may still be tied up with JavaScript changes, but on page load, the TOC menu should not be visible.

The second is an artifact I noted that on any page, when the content menu is toggled and the menu disappears, the lower right corner of the box surrounding the head is missing.

Cheers,

T

[David W. Farmer]

Having the TOC hidden on load has to be done with JavaScript (otherwise
the page is not usable when there is no JavaScript). So, that will
have to be implemented once the overhaul is official.

Isn't the TOC styling wrong? I thought that the CRC style was not using
the colors and general appearance of the default TOC. I'll need to see
if that styling was lost, or maybe I just have it set up wrong.

Also, hiding the TOC should be a publisher option, so there needs to be
some XSL work to implement that option.

I am not seeing the lower right corner of the head missing when the TOC is
hidden. Is that right above the magnifying glass for search? I can't
detect a change.

David

> https://groups.google.com/d/msgid/pretext-dev/b45b1eab-5b03-4163-8bdb-b00893839d09n%40googlegroups.com.
>
>

[Thomas Shemanske]

Image attached.

Notice the vertical bar on the RHS should extend down past the next button

T

[Thomas R. Shemanske]

And yes, the color scheme for the TOC is not what was intended for the CRC

You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/43eb69f9-4937-44a2-a540-430daa4a2745n%40googlegroups.com.

--

Thomas R. Shemanske
Grantham, NH 

[David W. Farmer]

Weird. It looks correct to me in Safari, Firefox, and Chrome.

> https://groups.google.com/d/msgid/pretext-dev/43eb69f9-4937-44a2-a540-430daa4a2745n%40googlegroups.com.
>
>

[Thomas R. Shemanske]

My screenshot was from chrome on Linux.  It does look fine on FF and Vivaldi also on Linux

T

You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/95e9629-174d-dd50-9cdd-193560d416a%40aimath.org.

[Oscar Levin]

Not sure if this is expected with the current status or not, but on my android based chrome browser, clicking the TOC hamburger menu has no effect.

[David W. Farmer]

I think you mean: when I open the page on a narrow device, the TOC is
hidden and it does not appear when I tap the hamburger.

If that was it, then it should be fixed (although I had some trouble
with the page width very close to the break point of whether the TOC
appears or not).

David

> https://groups.google.com/d/msgid/pretext-dev/e19b890c-6909-40eb-a5bb-b73eca99265bn%40googlegroups.com.
>
>

[Oscar Levin]

Yes, that is what I meant, and yes, it does seem fixed (after fighting with my phone to force refresh.

[Rob Beezer]

Experimenting with the "default" version, only. Not comprehensive, but thought
I'd get this out before I can get another chance to experiment some more.

* The navigation buttons in the footer (and "Feedback") seem to get an
underline on hover, like they are "a" elements with a default styling?

* From some other chapter, I use the ToC to go to a subdivision of Chapter 4,
"Symbolic and Numerical Integrals". I get a pink flash, then it scrolls down
out of view. Maybe all the Sage cells just prior are expanding to occupy more
space?

* ToC sidebar scrolling seems much improved! If I follow an "in-context" link
from an "xref" knowl, could the target chapter scoll so that it is at the *top*
of the sidebar? Or am I expecting too much? ;-)

* "Empty heading!" is on me, I'd guess. Probably shouldn't ever happen, and is
maybe an artifact of the age of the sample article.

Rob

[Jason Siefken]

It appears that there are conflicts between the CSS in

https://runestone.academy/cdn/runestone/6.3.24/637.0fa6cababf056764.css

and the pretext css. (I am testing the React code, but I suspect that that file is also what's causing links to be underlined elsewhere).

I believe Brad and I talked about (and got working?) a prefixing of all of Runestone's CSS. I think the prefixed runestone CSS should be deployed to all, since Runestone components should now have a runestone class on their parent elements.

[David W. Farmer]

There are several other conflicts with Runestone CSS which I have
been dealing with steadily (typically by adding or adding more specific
selectors).

1) The underlining in the bottom nav buttons should be gone now.

2) MathJax, sage cells, and other things that change the page after
it loads, can cause the target location to scroll out of view. (Maybe
MathJax will not cause that if we use the setting where it only
typesets what is currently in view). I do not have a proposed solution.

3) I added very simple JavaScript to scroll the TOC so the followed
link is in the vertical center of the screen. If the anchor is not in
the TOC, then assumes the section.

a) It would be better if it assumed whatever parent of the target anchor
was in the TOC.

b) I did not write any code to adjust the TOC highlighting when you move
up and down the content of the page.

c) All I wanted to do at this point was make something that was usable.
The React version will do all of that correctly. Once we have that,
then we can discuss how much functionality we want in the non-React
version (indeed, who will want the non-React version, and why?)

4) Once the overhaul is official, maybe we just hide the "empty heading",
unless it is a symptom of a more serious problem? (Indeed, the heading
is literally empty, and I set the CSS to insert "empty heading" as an
indication that something was not quite right.)

David

> --
> You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
> pretext-dev...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/05677b29-f3c6-9242-c47d-e9820e3fb349%40gmail.com.
>
>

[Brad Miller]

I just did a build for academy using the overhaul branch, locally.  I will do one on the public development server today.  I'm sure David is aware  of these, but I'll mention them anyway.

1. There are a few things to deal with in the styling of the interactive components. Multiple choice questions are displaying the choice and answer on separate lines.
2. the 👤 menu needs to be brought up to date
3. The pencil icon is not functional 

Bradley Miller, PhD

Professor Emeritus Computer Science

Luther College

Founder, Runestone Interactive

Blog: A Reputable Journal

Democratizing Textbooks for the 21st Century - Please Support Runestone

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/5beb6ef-afff-8f7f-4724-5592dec27e8%40aimath.org.

[Brad Miller]

OK, build on dev is finally live.

https://dev.runestoneacademy.org/ns/books/published/PTXSB/multiple-choice-exercises.html

Brad

Bradley Miller, PhD

Professor Emeritus Computer Science

Luther College

Founder, Runestone Interactive

Blog: A Reputable Journal

Democratizing Textbooks for the 21st Century - Please Support Runestone

[David W. Farmer]

I think the CRC shell will look closer to what Tom intended if it
is built with colors_bluegreen_grey . So, next round of betas
could use that with the CRC sample. (But no need to make new
betas yet.)

I'd really like to get rid of the scaffolding.less CSS. I can
add what is needed to the pretext css. (Most of scaffolding.less
is harmless or I have already over-ridden. The fact that it sets
the fonts is the main headache.)

Next I'll see what is up with the overhaul on Runestone.

Regards,

David

[David W. Farmer]

Overhaul in Runestone looks better:

https://runestone.academy/ns/books/published/PTXSB/sample-book.html

The scratch active code button works, but take a some time to
appear.

The Runestone menu is in a .dropdown, but we had changed the HTML
to use .runestonebustmenu . Maybe something did not get pulled
into overhaul? (Changing the HTML will mess up the CSS, but it is
no problem for me to adjust the selectors.)

I still need to properly position the search box. If there are
other issues with the overhaul, please post.

David

[Thomas R. Shemanske]

Yes; I agree with David that the CRC style wanted colors_bluegreen_grey.

Cheers,

Tom

--
You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/5dee2ab8-81b-b52-8137-1a2f5bd62a8%40aimath.org.

[Rob Beezer]

Entirely for Brad and Jason. We discussed during Drop-In having some
experimental Runestone Services javascript available for testing with React
(namespaced, iirc). PreTeXt orginally assumed a redirection file was available
locally, with the latest version numbers. We weaved in in a way to get that
online from the Runestone CDN. So the logic is a bit complicated to patch
again, and we already have a debugging scenario (which assumes a local copy).
How about...

1. When Brad is ready, he posts his webpack redirection XML file for the
experimental JS at a permanent address, and semi-silently updates whenever
necessary.

2. Jason scripts retrieving that file with wget or curl into a location
in/near his working copy of the PreTeXt repo.

3. Jason sets the PreTeXt string parameter debug.rs.services.file to point to
the file he has retrieved.

(a) a full path is safest/easiest

(b) a relative path must be relative to pretext/xsl

4. An alternative is that the file from (2) replaces
pretext/xsl/support/runestone-services.xml in a scratch copy of the PreTeXt
repository, though that will interfere with pulling, etc. This would make (3)
unnecessary.

[Rob Beezer]

On 12/6/22 11:13, Thomas R. Shemanske wrote:
> Yes; I agree with David that the CRC style wanted colors_bluegreen_grey.

Since we are close to the finish line, I made a "crc" with the bluegreen_grey
color scheme.

https://pretextbook.org/beta/2022-12-07-overhaul-crc-color

[Rob Beezer]

With the "crc" version, it seems the "Search Results" box is displayed *under*
the bar with "Index", "Prev/Up/Next", etc.

Both posted betas - 10 days ago, and a couple hours ago.

Rob

On 12/7/22 10:00, Rob Beezer wrote:
> https://pretextbook.org/beta/2022-12-07-overhaul-crc-color

[David W. Farmer]

Thanks.

Fixed.

> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to pretext-dev...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/d1a059a4-c2e3-7baa-a167-9c2f07a7be6e%40ups.edu.
>
>

[Thomas R. Shemanske]

I noticed an odd navigation issue with the new crc beta

https://pretextbook.org/beta/2022-12-07-overhaul-crc-color

When I select Chapter 14 from the TOC, it goes there initially and after a few seconds jumps down to section 14.8; screenshot attached.

This happens on Linux with chrome, vivaldi and firefox

Cheers,

Tom

--
You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/bea3de0d-2594-8259-f296-531738bdfa9a%40ups.edu.

[David W. Farmer]

A particular GeoGebra interactive is grabbing focus.

If you wait for the page to settle, and then use the arrow keys, you will
see something move in Figure 14.24

Not new to overhaul: same occurs in the current version.

Anyone know how to stop GeoGebra from doing that?



On Thu, 8 Dec 2022, Thomas R. Shemanske wrote:

> I noticed an odd navigation issue with the new crc betahttps://pretextbook.org/beta/2022-12-07-overhaul-crc-color

> You received this message because you are subscribed to the Google Groups "PreTeXt development" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/CA%2Bz8C4hQ_0xcRkTdwCMXd8mX592NOpzLCyZG5Kp%3Dc-N%3DqM2tqQ%40mail.gmail.com.
>
>

[Rob Beezer]

On 12/8/22 06:39, David W. Farmer wrote:
>
> A particular GeoGebra interactive is grabbing focus.
>

> Anyone know how to stop GeoGebra from doing that?
>

Appears to be upstream...

https://github.com/PreTeXtBook/pretext/issues/1086

[Thomas Shemanske]

Footers are having issues.

The Dec10-build.png is the build today with a project I have after a fresh clone of PreTeXtBook/pretext

The other two are from betas (Oscar Levin and CRC)

The footer in the beta CRC version rendered correctly; not in OL

 

I tried to compile the CRC version with  <css style="crc" colors="bluegreen_grey"/>, but only the colors were respected.

Tom

[Oscar Levin]

Buttons on narrow screens are overflowing to the next line: 

[Sean Fitzpatrick]

A few things I've noticed:

- WeBWorK activate button is working now!

- David's fix to the CSS has taken care of overlapping figures for me. (Follow-up question: the CSS change was to override a bit of Runestone CSS. When I put the book on a Runestone server, is this going to crop back up?)

- One of the very last things to load is the JavaScript that controls menu hiding. So when you open a link on mobile, and it's a book like APEX with lots of things that need to load, it takes 5-10 seconds before the menu sidebar goes away. A new reader might assume that the book is unreadable on mobile without changing to landscape

--

You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/2a183899-c5a7-46c5-9cc7-00f9ef82fe5en%40googlegroups.com.

[David W. Farmer]

A few things:

1) I fixed the button overflow on narrow screens.
(I do not know why that was happening, because I am sure
it was okay before.)

2) The "Contents" button has those words not vertically centered
when I build, and on Steven's build. But it looks okay when Sean
or Rob build. What could be different?
(I also see that I need to clean up the navbar css because it is in two
files.)

3) Permalinks are on paragraphs again. They are there on Figure
captions, but for some reason don't show up when you mouse over them.
I though we had that problem and I solved it, but apparently not.

Sean: these fixes are independent on whether the hosting is on
Runestone.

Sean: there are some things that will require the React JavaScript.
Particularly involving the TOC.

David

[Thomas R. Shemanske]

Below is the screenshot of a crc build after figuring out the appropriate entries in the publication file:

<css shell="crc" banner="crc" navbar="crc" toc="crc" colors="bluegreen_grey"/>

The footer is better than the default, although the feedback button is missing, and at least on linux chrome

part of the right-hand border around the header is not visible.

T

--
You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/e298c0fb-9f3-26a7-6ed4-4e291dec09e%40aimath.org.

[Rob Beezer]

On 12/10/22 08:47, David W. Farmer wrote:
> 2) The "Contents" button has those words not vertically centered
> when I build, and on Steven's build.  But it looks okay when Sean
> or Rob build.  What could be different?
>    (I also see that I need to clean up the navbar css because it is in two files.)

APEX has Runestone goodies, Steve/CLI-template does not.

I was only reminded Thursday that the XSL does zero Runestone setup for a
generic HTML build when it is not needed.

That is a hangover from Runestone being new to us for generic builds. I don't
expect to last forever. But of course, it complicates current task. It has
been present in the sample article (all pages), which has a goodie or two to
provoke RS setup for just this reason.

Advise if changes are needed.

Rob

[Rob Beezer]

On desktop, in (new) Firefox.

Clicking on "Contents" makes ToC hide/show, but main text does not slide left/right.

See recent builds:

https://stevenclontz.github.io/fluffy-giggle/solutions-1.html

https://opentext.uleth.ca/apex-overhaul/apex-calculus.html

Rob

[Rob Beezer]

On 12/10/22 09:02, Thomas R. Shemanske wrote:
> although the feedback button is missing

And it would be present if you don't use "crc" CSS?

Is it present in the HTML you used for that screenshot? (I can't peek beneath
the screenshot.... ;-) )

[David W. Farmer]

Main content now slides left when no TOC.

Rob: is it better to have the appearance of the "You!" menu
depend on a debug flag, or for me to just hide it with CSS
and I can un-hide it when I want to work on it?

Either is fine with me, but didn't want to hide it without
telling you, and have you wonder where it went. Maybe using
CSS is better because then I don't need to rebuild to test?

Tom: I can't replicate the issue with the missing border header,
and the footer looks okay to me in the oscarlevin style
(That style is not supposed to change the footer.)

Anything else waiting on me?

David

> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pretext-dev...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/140f0567-c45a-03bd-d5f2-90c8afe63345%40ups.edu.
>
>

[Thomas R. Shemanske]

One issue present in all of these images below (today's build) is that the feedback button is missing, and that is because it is missing from the rendered HTML which says:

<div class="ptx-page-footer">
<a class="pretext-link" href="https://pretextbook.org"><div class="name">Authored in PreTeXt</div>
<div class="logo"><svg xmlns="http://www.w3.org/2000/svg" width="100%" height="100%" viewBox="338 3000 8772 6866"> ... </svg></div></a><a class="mathjax-logo" href="https://www.mathjax.org"><img title="Powered by MathJax" src="https://www.mathjax.org/badge/badge.gif" alt="Powered by MathJax"></a>
</div>

In the default style, the height and width of the footer are out of whack; in the crc it is correct.

And not that it is a huge deal, but may relate to the "You!" button.  In the Dec11-LAR images, there is neither an index nor calc button and spacing seems fine.  In the Dec11-SPA* image, I included an index and the spacing between the three buttons Contents, Index and You is uneven.  Perhaps that is because the middle slot was for two buttons.

The border around the header with the crc menu being not fully closed does seem to be a chrome on linux issue, so I guess we ignore it.

Tom

You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/c567293c-5654-c5ee-1ce6-d5f252d85bd%40aimath.org.

[Thomas R. Shemanske]

Thinking about the feedback button a bit more, would the following make sense?

Arrange the buttons in order PreTeXt -- Feedback -- MahtJax, and make the appearance of the feedback button an option based on a publisher file entry

I can think of many uses of PreTeXt where a Feedback button is not something of value, and with the ordering as above, the spacing would be symmetric

Tom

[David W. Farmer]

I'll need live html, not a picture, to fix the footers.

Regards,

David

> https://groups.google.com/d/msgid/pretext-dev/CA%2Bz8C4ivrKvZewzpXMFgW-fF6aGeyth4%3DeE5NALKjvwNDBOqdw%40mail.gmail.com.
>
>

[Thomas R. Shemanske]

https://hecke.dartmouth.edu/pretext-test/linear-algebra-refresher-CLI/output/web/lar.html

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/912f4de3-1238-d1d2-ee18-916513614d2a%40aimath.org.

[Rob Beezer]

Thanks, Tom.

On 12/11/22 05:57, Thomas R. Shemanske wrote:
> One issue present in all of these images below (today's build) is that the
> feedback button is missing, and that is because it is missing from the rendered
> HTML which says:

The button is conditional on having a "docinfo/feedback" element in your source.
I presume you don't have such a thing in your source?

I can see in the code where it is added to div.ptx-page-footer. So I don't
think it has gone AWOL as part of overhaul.

Rob

[Rob Beezer]

On 12/11/22 07:52, Thomas R. Shemanske wrote:
> Thinking about the feedback button a bit more, would the following make sense?
>
> Arrange the buttons in order PreTeXt -- Feedback -- MahtJax, and make the
> appearance of the feedback button an option based on a publisher file entry
>
> I can think of many uses of PreTeXt where a Feedback button is not something of
> value, and with the ordering as above, the spacing would be symmetric

Yes, I've been thinking this is another thing that should migrate out of
"docinfo" and into a publisher option. (That's the next front, now that most
(all??) string parameters have been deprecated.

We also need a Runestone logo/badge/link in the footer. Brad has been waiting
patiently. ;-) It'll say "powered by" for generic HTML builds, and "hosted on"
for Runestone Academy builds.

@Brad - we just get the MathJax badge from them;
https://www.mathjax.org/badge/badge.gif. Do you have something similar? We can
use a full URL in one case, and a shortened version when hosted at RS. A
compact SVG might make the most sense if there are no gradients. (Doesn't need
to be a GIF!)

Rob

[Rob Beezer]

On 12/10/22 13:29, David W. Farmer wrote:
> Main content now slides left when no TOC.

Very good, thanks.

> Rob:  is it better to have the appearance of the "You!" menu
> depend on a debug flag, or for me to just hide it with CSS
> and I can un-hide it when I want to work on it?
>
> Either is fine with me, but  didn't want to hide it without
> telling you, and have you wonder where it went.  Maybe using
> CSS is better because then I don't need to rebuild to test?

If it is just YOU! working on it, let's go with CSS. When we are ready to
release something substantial, we can use a flag to let people test during a
soft opening.

> Anything else waiting on me?

Text on Contents button seems to now be centered vertically on RS-powered
builds, and I think you've announced everything else.

Rob

[David W. Farmer]

I made the footers less bad. I'll look at them more carefully
after the Runestone item is added.

I have hidden the "You!" button.

> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pretext-dev...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/d7ada87f-1684-8073-1e9e-66be598e0a60%40ups.edu.
>
>

[Thomas R. Shemanske]

Yes; I now see where the feedback button is activated in docinfo.  Perhaps David's revision to the footer will make it look more natural when feedback is absent.

Cheers,

T

--
You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/36c895fa-c0f6-b275-6bb7-2179c56efbf3%40ups.edu.

[Oscar Levin]

Not sure if this is on anyone's radar, but on short pages (e.g. https://pretextbook.org/doc/guide/html/editors-supporting-schema.html), the footer is slide to the right of the TOC.  Seems like this could be fixed by some sort of height minimum/maximum relative to window size.

I have also found it distracting when the TOC moves twice: once when you scroll down (when the title moves up) and once again when the footer moves into view.  More noticeable on short pages, of course.

[Steven Clontz]

@Oscar - are we thinking that the minor bump 1.2 is the appropriate next release to include Overhaul, once things are stable?

[Jason Siefken]

I also find that behavior annoying...I am not sure what the best solution is.

You received this message because you are subscribed to the Google Groups "PreTeXt development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/64e886f4-ffaf-41f8-ab55-a98add0701abn%40googlegroups.com.

[Thomas Shemanske]

Is the tableofcontents level option working in the new pretext version?

The following seems to have no effect in the publication file

 <common>
    <tableofcontents level="2" />
  </common>

and I am getting a fully expanded TOC such as in 

https://hecke.dartmouth.edu/pretext-test/linear-algebra-refresher-CLI/output/web/lar.html

[Rob Beezer]

On 12/16/22 10:41, Thomas Shemanske wrote:
> Is the tableofcontents level option working in the new pretext version?

No - just checked. The ToC never used to go past sections (of a book), and I
think you could skinny it down to just chapters (much to the consternation of
David F).

I think the expectation is we will have some Javascript enabling expand/collapse
behavior. Then, maybe the setting in the publication file will just control the
default/opening state?

Rob

[David W. Farmer]

This is addressed in the new thread I started. But to clarify:
everything that could be in the TOC, has to be there as part of
the page. Then JavaScript and CSS can do the right thing.

Currently, all that TOC information is visible. Because it
does not make sense to expend effort on the pre_Reach version.

If we decide to offer a non-React version,
probably the default will be set to the previous default
of two levels, just by hiding the lower levels. But the hope
is that the React version will be the default, which will allow
more flexibility, such as collapsing and expanding parts of the TOC.

I'd also like to have the TOC dynamically show more detail near
the reader's current location, and also dynamically change what
is shown as the reader scrolls the TOC. It should be possible to
simultaneously make almost everyone happy.

David

> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pretext-dev...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/f72cef01-4205-972c-381a-86358703d349%40ups.edu.
>
>

[David W. Farmer]

Dear Tom,

I tried and failed to implement that behavior in the TOC.

What I think is wanted is:

1) You can see the beginning of the TOC whether the page is scrolled
to the top or not.

2) The page footer covers the bottom of the TOC (so the TOC does not
move) when the page is scrolled to the bottom.

I could not come up with a combination that accomplished this.

Also, I agree that the page footer being at the bottom on very short
pages would be better. This can be accomplished with the whole
page using flex or grid. I don't want to do that in the midst of
other changes, so I filed an issue:

https://github.com/PreTeXtBook/CSS_core/issues/47

Regards,

David

> You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to

> pretext-dev...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/64e886f4-ffaf-41f8-ab55-a98add0701abn%40googlegroups.com.
>
>

[Rob Beezer]

We are manufacturing a separate "manifest" for the React work, which is very
similar to the ToC. That may be moot at the moment.

A huge ToC sidebar (see The Guide) is pretty bad. I do understand why. The
ul.structural we are building is done with a recursive template. Trivial I
think to chop it off at its knees with $toc-level PLUS a we-are-not-doing-react
flag we already have. So it would all be there for React testing.

In other words, I think it is worth the effort to have an abbreviated ToC during
the interregnum, which will be easy to go in and easy to rip out later.

Yes? No?

Rob

[Jason Siefken]

React rebuilds the TOC from the manifest.xml file, so the static HTML can be cut off wherever you think a non-JS website's TOC to be cut off.

[Rob Beezer]

Thanks, Jason. I'm going to go ahead on a branch, and David can call me off if
need be.

> <mailto:pretext-dev...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/2a9f92a5-059a-2a0a-d96f-921c74a33691%40gmail.com <https://groups.google.com/d/msgid/pretext-dev/2a9f92a5-059a-2a0a-d96f-921c74a33691%40gmail.com?utm_medium=email&utm_source=footer>.

[David W. Farmer]

No, stop!

I'll hide those with CSS.

> https://groups.google.com/d/msgid/pretext-dev/d5eedec0-0fcf-e88f-04bb-d6aa3e1dd7f7%40ups.edu.
>

[Rob Beezer]

Done. (Not pushed.)

How are you going to respect the $toc-level variable?

[David W. Farmer]

> How are you going to respect the $toc-level variable?

Is that a trick question? There is a class="depth2" on the #ptx-toc ,
so I used that to hide everything below that depth.

That seems to be the default, so everyone is getting that now.

Keep in mind that this is just a temporary convenience to keep
everyone from being distracted by a long TOC. The React version
will do it better.

Live, if you reload.

David

[Thomas R. Shemanske]

The change class="depth2" does not seem to be working for me despite the source saying

<div id="ptx-sidebar"><nav id="ptx-toc" class="depth2"><ul class="structural">

See https://hecke.dartmouth.edu/pretext-test/linear-algebra-refresher-CLI/output/web/lar.html

--
You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/61b3620-ec91-81d4-6b28-90f3d0f1566f%40aimath.org.

[David W. Farmer]

Sorry, fixed now. Also the footer is better now.

> You received this message because you are subscribed to the Google Groups "PreTeXt development" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to
> pretext-dev...@googlegroups.com.
> To view this discussion on the web visithttps://groups.google.com/d/msgid/pretext-dev/CA%2Bz8C4jraagswZMJBuXUPVAW5Wg0CMDVO-BUjE_Cer%2B1LtX%2ByA%40mail.gm
> ail.com.
>
>

[Thomas R. Shemanske]

Excellent!  Many thanks.

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/527c38d7-53c0-a327-67f8-d18763201185%40aimath.org.

[Rob Beezer]

On 12/19/22 07:18, David W. Farmer wrote:
>> How are you going to respect the $toc-level variable?
>
> Is that a trick question?

Would I do that? ;-)

We have long had explicit control over the depth of the ToC. And it is meant to
apply to any conversion. (Separate publisher files could be used for separate
outputs to vary the behavior.) But in HTML we only ever wrote out to the level
of "section" in books.

And there is a common use case (which I was describing to a new author during
Drop-In last week) for no ToC at all. See bullet 3:

Section 29.10: Single Page HTML
https://pretextbook.org/doc/guide/html/one-page-html.html

Rob

[David W. Farmer]

If we are still trying to preserve the option of a functional
non-React version, then I think we need to send the whole TOC
in the HTML and just hide at the appropriate level.

If it is all one page, then that presumably means no index,
and no "Contents" in the nav bar across the top. Also no
Prev/Up/Next. I have no opinion whether the TOC for a single page
document is missing, or there but hidden. But we may need
to do some styling for such a specialized page.

David

> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pretext-dev...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/96c5d27b-a85c-ac44-53a9-41c8b5926986%40ups.edu.
>
>

[Rob Beezer]

> still trying to preserve the option of a functional non-React version

I definitely think we should be, until we have a React version that we are
confident enough to commit to and support with enough people knowledgeable with
React. And it had better be as accessible as what we have now.

So I'm pushing on this one because I don't want to have suspended functionality
for months.

I can put class names on the ul.structural that reflect their depth, if that
helps (depth1, depth2, depth3, ...). Should I write the publisher's requested
depth into the HTML as a Javascript variable so the CSS can react to it? Is
this a start on an EBookConfig-style structure?

Rob

[Jason Siefken]

It would be better to add a data-pretext-flags attribute to the root element. CSS can easily read data attributes specified as a space-separated lists and then do what it pleases with those.

But, I think there's a miscommunication (unless I am misunderstanding myself). When David says "no React" version, I think he means a version without any JS at all.

[David W. Farmer]

All I need to give the publisher what they want, is what you already
provide: a "depthN" class on the #ptx-toc.

Assuming I am interpreting that class correctly.

We did a pretty good job (during overhaul times) of structuring the
HTML TOC, so I can just figure out the depth of anything and hide
as appropriate.

I (perhaps mistakenly) assumed it was easier if the HTML version
always provided the whole TOC, only indicating the publisher choice
by a class. What I do is CSS only: no need for a JavaScript variable.
If there are reasons not write the whole TOC, then let's discuss.

> https://groups.google.com/d/msgid/pretext-dev/95ff046a-6fc5-1746-2cff-81705c691458%40ups.edu.
>

[David W. Farmer]

> But, I think there's a miscommunication (unless I am misunderstanding myself). When David says "no React" version,
> I think he means a version without any JS at all.

Actually, I mean both: we need the page to be usable with no JS. And for
now it would be prudent to have reasonable functionality without using
the React framework.

[Rob Beezer]

On 12/19/22 12:13, David W. Farmer wrote:
> All I need to give the publisher what they want, is what you already
> provide:  a "depthN" class on the #ptx-toc.

Oh! It was a trick question. #ptx-toc.depth2 is hard-coded. No variance. No
such thing as "depthN". ;-)

Some expedient from the overhaul work, I guess. Sorry to be a bit slow on the
uptake.

I should provide depth0, depth1, depth2, depth3, ...? (Trivial to do.)

I believe "depth0" previously just left the ToC out. It did not mean the
document was single-page. (It is just a streamlining thing in the single-page
case.) So the Prev/UP/Next could still have some functionality.

Do we need a publisher switch for single-page and we adjust accordingly? Alex
is making new publisher switches like this a no-brainer. I can go to town.

Do we want to allow a "no-ToC" option, independent of "single-page"?

Rob

[Rob Beezer]

Two small HTML items exposed by the more complete and reimagined ToC. Mea
culpa, but I need David's help with #2.

1. The "contributors" division (much like a preface) was trying to number
itself. Loads of errors at the console, but no apparent harm a reader could
see. So harmless. Fix will be pushed today. Mostly an FYI here if we get
caught-out between CLI releases and somebody hollers.

2. For "article" (only), I made "abstract" a level 2 item in the ToC. It
appears as part of the HTML page provoked by the "frontmatter" element (and so
is below "Front Matter" in the ToC). Only it has never had a title. Worse
still, it is just a bare HTML "p" sitting on the page. So it needs some
structure. Following would look like what we have in the vicinity.

div.abstract
span.title
[Several "p" for content]

@David - workable? I'd post a beta if it looks like crud, but otherwise might
just let you style from the sample article online (not there yet!).

Off to hunt down some LaTeX bugs.

Thanks,
Rob

[David W. Farmer]

There are maybe two issues with the abstract.

a) In the TOC it is an entry with empty title. That is why you see
"empty heading!"

https://aimath.org/~farmer/tmp/RHNoDoubt/frontmatter-1.html

So, we need that title (presumably "Abstract". Internationalized)
in the TOC.

b) On that page, same link above, it is fine to have the div.abstract
wrapper. Numerous style guides say that an abstract should be one
paragraph, but I guess we should be flexible. Having that
wrapper makes it easier to reference, so definitely do that.

Do we want a nonempty span.title, presumably containing the single
word "Abstract". At this instant I have not formed a strong opinion.
The example above seems to work fine without that word. But I
probably would not have had a problem if it were there.

Maybe make a beta with "Abstract" as the title, on the page and in the
TOC, and we can see how it looks (after we see if it needs styling).

David


On Mon, 19 Dec 2022, Rob Beezer wrote:

> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pretext-dev...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/22d1cdea-36e2-5547-58a7-3238936fd895%40ups.edu.
>
>

[Rob Beezer]

Perfect. Thanks, David.

Yes, the "empty heading!" tipped me off. ;-) And as you say, there is no title
there.

LaTeX does a mildly prominent (bold?) centered "Abstract" just above (see sample
article posted online). So this is a case where I think mimicking is a good
thing to do.

Once in the ToC it'll be just a bit more obvious where a reader can find it
(even if it does seem to be working just fine right now, only out of neglect).

Essy enough to enforce a single "p" and drop everything else. ;-) But I think
you are right that that could be over the line.

Rob

[Sean Fitzpatrick]

I'm noticing some navigation issues; these are more noticeable with the CRC format, but present in the default as well:

If you have a book with a long TOC, and you are viewing a long page, you can't scroll all the way to the bottom of the TOC.

See here, for example: https://opentext.uleth.ca/apex-crc/sec_chainrule.html

To see the last few lines of the TOC, I have to scroll to the bottom of the page. Once the footer appears, so does the bottom of the TOC.

This is a little bit annoying, but manageable.

Somewhat more problematic. If you open one of the sections at the very end of the TOC, then TOC navigation will want that part of the TOC visible.

This requires the footer to be on the page, which results in the page loading at the very bottom, rather than at the top.

Examples:

CRC: https://opentext.uleth.ca/apex-crc/backmatter-1.html (you have to scroll up to see anything)

Default: https://opentext.uleth.ca/apex-overhaul/section-98.html

[David W. Farmer]

I did something crude so that you don't have to scroll the page to see the
bottom of the TOC.

That does not fix the other problems.

> To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/ddba179d-62c4-4dcc-9192-e85e75473445n%40googlegroups.com.
>
>

[Steven Clontz]

In addition to the weird "empty heading!" the links to Colophon and Acknowledgements are broken in our JMM workshop article (they lead to HTML files but should be #heading anchors): https://stevenclontz.github.io/ptx-jmm-2023/meta_frontmatter.html

Steven Clontz

https://clontz.org - steven...@gmail.com

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/822abd16-9c60-296f-97de-6ed2a29edd6a%40aimath.org.

[Rob Beezer]

Thanks, I think I know where to go for that one...

On 12/20/22 10:58, Steven Clontz wrote:
> In addition to the weird "empty heading!" the links to Colophon and
> Acknowledgements are broken in our JMM workshop article (they lead to HTML files
> but should be #heading anchors):
> https://stevenclontz.github.io/ptx-jmm-2023/meta_frontmatter.html
> <https://stevenclontz.github.io/ptx-jmm-2023/meta_frontmatter.html>
>
>
> Steven Clontz

> https://clontz.org <https://clontz.org> - steven...@gmail.com
> <mailto:steven...@gmail.com>

> <mailto:pretext-dev...@googlegroups.com>.

> >       >> To view this discussion on the web visit
> >       >>

> https://groups.google.com/d/msgid/pretext-dev/22d1cdea-36e2-5547-58a7-3238936fd895%40ups.edu <https://groups.google.com/d/msgid/pretext-dev/22d1cdea-36e2-5547-58a7-3238936fd895%40ups.edu>.

> >       >>
> >       >>
> >       >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> email to pretext-dev...@googlegroups.com

> <mailto:pretext-dev%2Bunsu...@googlegroups.com>.

> > To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/ddba179d-62c4-4dcc-9192-e85e75473445n%40googlegroups.com <https://groups.google.com/d/msgid/pretext-dev/ddba179d-62c4-4dcc-9192-e85e75473445n%40googlegroups.com>.

> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pretext-dev...@googlegroups.com

> <mailto:pretext-dev%2Bunsu...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/822abd16-9c60-296f-97de-6ed2a29edd6a%40aimath.org <https://groups.google.com/d/msgid/pretext-dev/822abd16-9c60-296f-97de-6ed2a29edd6a%40aimath.org>.

>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-dev...@googlegroups.com

> <mailto:pretext-dev...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/CAOWT6ThCF6yCDHQKG2ZyEpRV1impwXdq3X4Kf_qe73paODVSvw%40mail.gmail.com <https://groups.google.com/d/msgid/pretext-dev/CAOWT6ThCF6yCDHQKG2ZyEpRV1impwXdq3X4Kf_qe73paODVSvw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

[Rob Beezer]

On 12/20/22 10:58, Steven Clontz wrote:

> In addition to the weird "empty heading!"

Not weird, David put it there intentionally to catch these sorts of problems.
Useful.

the links to Colophon and
> Acknowledgements are broken in our JMM workshop article

An "article" does not have a "colophon" nor an "acknowledgements".

Rob

[Rob Beezer]

Beta available now to style. Just the bare minimum. One page, no images, etc.

https://pretextbook.org/beta/2022-12-20-abstract/frontmatter.html

Thanks,

Rob

On 12/19/22 16:39, David W. Farmer wrote:
>

[Rob Beezer]

On 12/19/22 12:33, Rob Beezer wrote:
> I should provide  depth0, depth1, depth2, depth3, ...?  (Trivial to do.)

I answered my own question. Experimentally.

But I think "depth4" might be off-by-one?

Grab any page of the sample book as posted now. There is a division "E.1.1.1"
which should show in the ToC sidebar iff "depth5". I think it shows prematurely
with "depth4" (and then is OK at "depth5").

All ready to go, may push after dinner.

Rob

[David W. Farmer]

I had not styled depth4, but I just did. That should fix the
off-by-one.

depth5 or higher just shows whatever there is.

> https://groups.google.com/d/msgid/pretext-dev/f2039fb9-a25d-6565-4211-2058967a28c7%40ups.edu.
>
>

[Rob Beezer]

Thanks! I'll push in the morning.

Rob

[David W. Farmer]

Abstract styled, minimally.

> https://groups.google.com/d/msgid/pretext-dev/22d7a224-6ff0-9069-6493-1df062872f39%40ups.edu.
>
>

[Rob Beezer]

Looking good! Thanks.

Merged, and updating website samples right now.

[Rob Beezer]

Thanks for the clean-up. Merged and pushed. Website updated just now.

"depth0" just leaves an empty sidebar. Good. Do we want to also hide away the
contents button? Slide main content left?

For a truly 1-page production, I think the navigation buttons will be
"greyed-out". So they don't really need to be hidden, and they may be
useful/necessary for a multi-page production where somebody wants the navigation
buttons.

So, two things to think about:

1. How should depth0 be?

2. Do we want an explicit "one-page-production" publication setting?

Rob

On 12/20/22 19:09, David W. Farmer wrote:
>

[Rob Beezer]

In case you missed it, the Table of Contents depth is working now. Subject to
catching up with the CLI.

On 12/16/22 10:41, Thomas Shemanske wrote:
> Is the tableofcontents level option working in the new pretext version?
>
> The following seems to have no effect in the publication file
>
>  <common>
>     <tableofcontents level="2" />
>   </common>
>
> and I am getting a fully expanded TOC such as in
> https://hecke.dartmouth.edu/pretext-test/linear-algebra-refresher-CLI/output/web/lar.html
>
>
> On Wednesday, December 14, 2022 at 6:59:03 PM UTC-5 sief...@gmail.com wrote:
>
> I also find that behavior annoying...I am not sure what the best solution is.
>
>
> On 12/14/22 4:00 PM, Oscar Levin wrote:
>> Not sure if this is on anyone's radar, but on short pages (e.g.
>> https://pretextbook.org/doc/guide/html/editors-supporting-schema.html
>> <https://pretextbook.org/doc/guide/html/editors-supporting-schema.html>),
>> the footer is slide to the right of the TOC.  Seems like this could be
>> fixed by some sort of height minimum/maximum relative to window size.
>>
>> I have also found it distracting when the TOC moves twice: once when you
>> scroll down (when the title moves up) and once again when the footer moves
>> into view.  More noticeable on short pages, of course.
>>
>> On Sunday, December 11, 2022 at 12:56:05 PM UTC-7 thomas.r....@gmail.com
>> wrote:
>>
>> Yes; I now see where the feedback button is activated in docinfo.
>> Perhaps David's revision to the footer will make it look more natural
>> when feedback is absent.
>>
>> Cheers,
>>
>> T
>>
>> On Sun, Dec 11, 2022 at 1:45 PM Rob Beezer <bee...@ups.edu> wrote:
>>
>> Thanks, Tom.
>>
>> On 12/11/22 05:57, Thomas R. Shemanske wrote:
>> > One issue present in all of these images below (today's build)
>> is that the
>> > feedback button is missing, and that is because it is missing
>> from the rendered
>> > HTML which says:
>>
>> The button is conditional on having a "docinfo/feedback" element
>> in your source.
>>   I presume you don't have such a thing in your source?
>>
>> I can see in the code where it is added to div.ptx-page-footer.
>> So I don't
>> think it has gone AWOL as part of overhaul.
>>
>> Rob
>>
>> --
>> You received this message because you are subscribed to a topic in

>> the Google Groups "PreTeXt development" group.

>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe <https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe>.
>> To unsubscribe from this group and all its topics, send an email

>> to pretext-dev...@googlegroups.com.
>>
>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/pretext-dev/36c895fa-c0f6-b275-6bb7-2179c56efbf3%40ups.edu <https://groups.google.com/d/msgid/pretext-dev/36c895fa-c0f6-b275-6bb7-2179c56efbf3%40ups.edu>.

>>
>>
>>
>> --
>> Thomas R. Shemanske
>> Grantham, NH
>>

>> --
>> You received this message because you are subscribed to the Google Groups
>> "PreTeXt development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to pretext-dev...@googlegroups.com.
>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/pretext-dev/64e886f4-ffaf-41f8-ab55-a98add0701abn%40googlegroups.com <https://groups.google.com/d/msgid/pretext-dev/64e886f4-ffaf-41f8-ab55-a98add0701abn%40googlegroups.com?utm_medium=email&utm_source=footer>.

>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-dev...@googlegroups.com

> <mailto:pretext-dev...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/pretext-dev/44346e6b-14b6-4c3b-a72e-ef1e271d91d9n%40googlegroups.com <https://groups.google.com/d/msgid/pretext-dev/44346e6b-14b6-4c3b-a72e-ef1e271d91d9n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[David W. Farmer]

If we want to hide the Contents button with CSS, we will need some class
higher up. Same if we want the content to slide left.

Will that be a special case? If so, then maybe the special case should
just omit the navigation bar and the TOC?

Is multi-page but no TOC an option? I don't see the use case for that,
but if that is reasonable (even if not common) then we need to provide for
that.

It makes no difference to the CSS. But maybe the XSL is more natural or
easier to maintain with one of the approaches.

Let me know if I should say where the classes should go for
the CSS method.

David

> https://groups.google.com/d/msgid/pretext-dev/abf90cca-98d5-8951-33c9-f7e82b8a83a8%40ups.edu.
>
>

[Thomas Shemanske]

Perhaps I should have posted this note here instead of the "Alternate Look and Feel" thread.

I recognize that this is a very small matter,  but I do not want it lost.

In the bluegreen_grey color scheme, a tweak is needed.  When the section being viewed is highlighted in the TOC, it is a different blue than when you mouseover a different section in the TOC.  The preferred color is the dark bluegreen (mouseover color) as shown in the screenshot.  It is possible it should be a contrasting color (I am terrible with colors), but the current blue is not optimal; and yes I recognize there would be no difference between the highlighted color and the mouseover color.  Perhaps there is better insight or something down the road for others.

Sample available at https://hecke.dartmouth.edu/pretext-test/linear-algebra-refresher-CLI/output/web/vector-spaces-linear-maps-matrices.html

Thanks,

Tom

[Steven Clontz]

Using CRC and a long ToC, some content is being hidden by the ToC scrollbar: (I'll get a live example available shortly)

[Steven Clontz]

Live example: https://teambasedinquirylearning.github.io/linear-algebra/2023e/frontmatter.html

Note also the gap to the left of the title (we don't have a logo so perhaps this space should be collapsed).

[David W. Farmer]

Fixed the issues with titles behind the scrollbar.

Also changed the TOC section color for the section being viewed.
I am not sure it is better. Feel free to suggest a different color
(as in, tell me the #RRGGBB code).

For the issue of a missing logo: this is similar to the discussion
about one-page documents, which will not have a TOC or navigation
buttons. The similarity is that the style assumes certain elements
are present, so how do we deal with them when they are missing?
(And does missing mean the content is missing, or does it mean that
the wrapper for the content is also missing?.
Please follow up on that thread if you have an idea.

Regards,

David

On Thu, 22 Dec 2022, Steven Clontz wrote:

> Live example: https://teambasedinquirylearning.github.io/linear-algebra/2023e/frontmatter.html
> Note also the gap to the left of the title (we don't have a logo so perhaps this space should be collapsed).
>
>

> Screenshot 2022-12-22 140719.png
> On Thursday, December 22, 2022 at 1:13:48 PM UTC-6 Steven Clontz wrote:
> Using CRC and a long ToC, some content is being hidden by the ToC scrollbar: (I'll get a live example available shortly)
>

> To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/ba40a7c5-38ce-4cf5-9642-6c97a26046bbn%40googlegroups.com.
>
>

[Thomas R. Shemanske]

Dear David,

Here are two options which should help colors_bluegreen_grey.css a bit.  I am sure they are not contrast compliant, but it improves the situation for now.

Option one is simplest, but will not change the background color when the toc entry is moused over:

Change --documenttitle from #2a5ea4; to var(--bluegreen);

Change --sectiontocactive from #366 to var(--documenttitle);

Option two provides slightly darker backgrounds to chaptertocactive and sectiontocactive, so mousing over becomes noticeable.

--darkbluegreen:  hsl(192,98%,19%);  = #014D60  (BTW bluegreen which is hsl(192, 98%,23%) = #015D74)
--documenttitle: var(--bluegreen);

--chaptertocactive: var(--darkbluegreen); 

--sectiontocactive: var(--darkbluegreen);

Best,

Tom

You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/dd-dEKy5rak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/5baac138-63aa-156a-66e2-55c9e7f9e0%40aimath.org.

[Brad Miller]

Hi Everyone,

I rebuilt all the PreTeXt books on Academy this morning with the CLI version 1.2.1.

@TomJudson -- This build has the support for attaching files to short answer questions.  Only tested by me...

Brad

Bradley Miller, PhD

Professor Emeritus Computer Science

Luther College

Founder, Runestone Interactive

Blog: A Reputable Journal

Democratizing Textbooks for the 21st Century - Please Support Runestone

To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/CA%2Bz8C4g5BHSVx8e6ra0xcs-JKv8vZC3Pzi%3Djp9afy-O2en%3DPFQ%40mail.gmail.com.

[David W. Farmer]

I went with the second option.

I had trouble with the darkgreen variable, so I just used its value twice.

> To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/CA%2Bz8C4g5BHSVx8e6ra0xcs-JKv8vZC3Pzi%3Djp9afy-O2en%3DPFQ%40mail.gmail.com.
>
>