Skip to content

[ReaderFooter] Adds a fixed-width setting for progress bar alongside items#14980

Merged
Frenzie merged 5 commits into
koreader:masterfrom
jonnyl2:fixed-width
Mar 9, 2026
Merged

[ReaderFooter] Adds a fixed-width setting for progress bar alongside items#14980
Frenzie merged 5 commits into
koreader:masterfrom
jonnyl2:fixed-width

Conversation

@jonnyl2

@jonnyl2 jonnyl2 commented Feb 15, 2026

Copy link
Copy Markdown
Contributor

Added a Fixed-width setting for the progress bar, available when displayed alongside the text items.

013006

Without fixed width setting the progress bar size can vary widely, making the tracking of one's position more difficult :

dynamic.mp4

With fixed with setting (new):

fixed.mp4

I also increased the available range for the minimum width in the UI from 50% of the screen width to 90%, since with the fixed setting it could otherwise never get larger than 50%, but a wider size will be useful if only few and short items fill up less than 50% of the remaining space.


This change is Reviewable

Comment thread frontend/apps/reader/modules/readerfooter.lua Outdated
Comment thread frontend/apps/reader/modules/readerfooter.lua Outdated
@mergen3107

Copy link
Copy Markdown
Contributor

Looks cool!

Comment thread frontend/apps/reader/modules/readerfooter.lua Outdated
Comment thread frontend/apps/reader/modules/readerfooter.lua Outdated
Comment thread frontend/apps/reader/modules/readerfooter.lua Outdated
@hius07

hius07 commented Feb 15, 2026

Copy link
Copy Markdown
Member

I like the idea.

@Commodore64user

Copy link
Copy Markdown
Member

Boxes at the top of clusters or your other option is to add a checkbox to the spin widget where one sets the minimum.

Comment thread frontend/apps/reader/modules/readerfooter.lua

@Commodore64user Commodore64user left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please move the box to the top.

@jonnyl2

jonnyl2 commented Feb 21, 2026

Copy link
Copy Markdown
Contributor Author

1841481

@Commodore64user

Commodore64user commented Feb 21, 2026

Copy link
Copy Markdown
Member

I said #14980 (comment) keep the two together

Lock
Minimum
Thickness
Margin

edit: the entire status bar menu follows one simple rule, Boxes at the top of their clusters.

@hius07

hius07 commented Feb 21, 2026

Copy link
Copy Markdown
Member

I'd prefer the current order unchanged.

@Commodore64user

Copy link
Copy Markdown
Member

but I don't, because there is some order now, and I don't want anyone circumventing it. We all know what mess it was like before, so @Frenzie, break the tie

@hius07

hius07 commented Feb 21, 2026

Copy link
Copy Markdown
Member

Style
Margins
Minimum
Lock

@Frenzie

Frenzie commented Feb 21, 2026

Copy link
Copy Markdown
Member

I don't understand what lock would do on top. I'd also make it minimum followed by lock.

@Commodore64user

Copy link
Copy Markdown
Member

The same it would be doing at the bottom ;) plus remaining consistent with the rest of the menu

@Frenzie

Frenzie commented Feb 21, 2026

Copy link
Copy Markdown
Member

Consistent with what? It's a minor visual detail, not a "show this thing yes or no" setting.

@Commodore64user

Copy link
Copy Markdown
Member

That's the problem exactly, cumulative "minor" things make a big thing. I thought you were built differently ;) do you think S. Jobs would have said the same? I doubt it

@Frenzie

Frenzie commented Feb 21, 2026

Copy link
Copy Markdown
Member

I'm not entirely sure if you're just joking but I mean the setting toggles a minor visual subdetail that is dependent on the other setting that should therefore logically be above it, which is different in kind from the checkboxes you're referring to. Checkboxes shouldn't come first because they're checkboxes. They merely frequently come first because of what they do.

@Frenzie

Frenzie commented Feb 21, 2026

Copy link
Copy Markdown
Member

PS Does the width dialog support adding a checkbox at the bottom of it? It doesn't necessarily need to be in the menu at all.

@jonnyl2

jonnyl2 commented Feb 21, 2026

Copy link
Copy Markdown
Contributor Author

I was looking at that when I first started, but I couldn't find any example of a single spin-widget with a checkbox underneath. Also, I don't really like the idea of having to go one further level down to toggle this.

@Frenzie

Frenzie commented Feb 21, 2026

Copy link
Copy Markdown
Member

Alright.

@jonnyl2

jonnyl2 commented Feb 23, 2026

Copy link
Copy Markdown
Contributor Author

What if we move up the separator:

103910

@Frenzie Frenzie added this to the 2026.02 milestone Mar 9, 2026
@Frenzie

Frenzie commented Mar 9, 2026

Copy link
Copy Markdown
Member

It looks fine graphically, but it doesn't seem to make much sense in regard to the underlying meaning.

I'll merge it as is for this release.

@Frenzie Frenzie dismissed Commodore64user’s stale review March 9, 2026 14:56

Well, I was asked to break the tie after all. Sorry. :-)

@Frenzie Frenzie merged commit 0f8f24b into koreader:master Mar 9, 2026
4 checks passed
@jonnyl2 jonnyl2 deleted the fixed-width branch March 9, 2026 18:09
0xstillb pushed a commit to 0xstillb/koreader-thai that referenced this pull request May 9, 2026
…items (koreader#14980)

Also increased the available range for the minimum width in the UI from 50% of the screen width to 90%, since with the fixed setting it could otherwise never get larger than 50%, but a wider size will be useful if only few and short items fill up less than 50% of the remaining space.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants