[Status bar] Major UI makeover #11678

Commodore64user · 2024-04-14T00:36:34Z

As discussed in #11605 and #11533, here is my proposal for the new and improved status bar menu.

No changes were made to the logic besides, adding a few if isTouch() statements to a couple of settings that shouldn't be available to non-touch devices (lock status bar and hold to skim) and any necessary changes for the correct operation of the menu. Also a checked function was added to the battery complication on the alternative status bar.

Most of the settings were reworded and/or rewritten. Please don't take it personally if I changed yours.

In defence of "complications": The word is borrowed from horology (science of time and timekeeping) were it refers to features on mechanical watches (smart ones too) that convey information not related to hours, minutes or seconds.
In the KOReader context, they refer to all features that convey any type of information on the status bar. I have decided, against your better judgement, to use the word in this PR as no better alternative was put forward and, all other possible replacements seem to fall short of the goal.

Some suggestions like "components" and "elements" were straight up rejected by other GitHub users, others like "status icons", "symbols", "status indicators", and all possible permutations of those fail to completely convey the idea of "Information". For example, 45/254 (page 45 of 254) is neither a symbol, or "icon" or "indicator", it is simply a piece of information. Besides, some of those same terms are already being used in a different context within the 'status bar' menu.

I encourage EVERYONE to download the files and run them on your machines, as that is the only way in which all of these changes will make sense. Read all the menus, play with them, in short; go have fun.

Due to the sheer number of changes, providing a pdf (like in #11549) documenting all changes would be a monster task I am not happy to go through right now. So I would appreciate it if one of you could kindly provide screenshots like the ones found here #11533 (comment), although bear in mind, those are from an older state of development. But again, preferably run it locally.

Special thanks to @poire-z who provided unrelenting support throughout the redevelopment of the menu.

This change is

yparitcher

Please no Complications.

hius07 · 2024-04-14T04:42:58Z

I do not like "complication". Neutral "items" works for me.
EDIT: or "indicators", to be used in phrases like "battery indicator".

poire-z

Hard to review with the reorganization and stuff moved around, so I may have missed little changes, even rewording.
But testing and reading menu items, these are the ones I did notice - meaning I'm probably fine with all the other rewordings. Except of course with "Complication" that I don't want to see anywhere (and not in the code).

I probably also did not check the added checked_func, hard to see if these were new or added - and not keen on hunting for settings and confirming the logic, so trusting you.

frontend/apps/reader/modules/readercoptlistener.lua

frontend/apps/reader/modules/readerfooter.lua

poire-z · 2024-04-14T08:48:19Z

frontend/apps/reader/modules/readerfooter.lua

-                    separator = separator ~= "" and separator or "none"
-                    return T(_("Item separator: %1"), separator)
-                end,
+                text = _("Maximum lenght for text complications"),


Spelling error: length
Also multiple times below, so please recheck everywhere for this common typo of yours :)

Feels like Maximum length... does not really belong with the 2 page left/progress percentage items, and more with the next ones about layout.

that option is still part of the formatting of the text, much like the one before. but I am happy to move the separator if formal request is put forward.

you are right, all three have the same typo. I copied/pasted them so that is probably why.

Any feedback about the reasoning for the still there separator in yellow?

Yeah, i've been waiting for you to reply to my reply. 😅

Also if you could help me understand this interesting fact about french dashes and underscores:

tiret du 6 vs., tiret du 8

6 or 8 what?

that option is still part of the formatting of the text, much like the one before. but I am happy to move the separator if formal request is put forward.

OK, your explanation also makes sense. No formal request :)

frontend/apps/reader/modules/readerfooter.lua

hius07 · 2024-04-14T09:55:46Z

Is "divider" to name horizontal lines approved?
If yes I'd change for bookmark list

koreader/frontend/apps/reader/modules/readerbookmark.lua

Line 160 in c345de5

text = _("Show separator between items"),

Frenzie · 2024-04-14T10:22:45Z

Is "divider" to name horizontal lines approved?

It's indeed a situation where it should probably be all separator or all divider but keep in mind I'm just quickly typing this on my phone, so I don't have much context.

hius07 · 2024-04-14T10:28:58Z

it should probably be all separator or all divider

In this PR "divider" is a horizontal line dividing the status bar, "separator" is a vertical line separating status bar items.
Following this, the bookmark list can have "dividers".

We do not have any more "separators" in the upper menu.

Commodore64user · 2024-04-14T10:35:15Z

Please no Complications.

what do you propose?

Commodore64user · 2024-04-14T10:49:38Z

I probably also did not check the added checked_func, hard to see if these were new or added - and not keen on hunting for settings and confirming the logic, so trusting you.

don't trust me. go and find it and put it to the test. the check_func is under alternative status bar and it is the battery status one.

There is nothing new, just the check_func and the isTouch ones. Logic for everything else is the exactly the same.

Commodore64user · 2024-04-14T11:17:04Z

it should probably be all separator or all divider

In this PR "divider" is a horizontal line dividing the status bar, "separator" is a vertical line separating status bar items. Following this, the bookmark list can have "dividers".

We do not have any more "separators" in the upper menu.

the word 'separate' is usually used to indicate physically removing something, as in 'separate the wheat from the chaff' or 'the fat was separated from the lean cuts'. 'divider' is used to break something up into smaller pieces, a whole into parts.

all that to say, I think 'divider' is better suited in this context than 'separator'.

I also could not help noticing the use of the word 'items' there, to mean: 'bookmarked passages' I guess... mmm. Do you see what I mean? there are also items in the file browser somewhere to mean something else entirely.

poire-z · 2024-04-14T11:28:24Z

so trusting you.

don't trust me. go and find it and put it to the test. the check_func is under alternative status bar and it is the battery status one.

That was a polite way to say: "I don't want to spend time understanding the logic and test it" :), and to invite others who care to do so, and you to double check.

So, do you mean you just added ONE checked_func ? The one under alt status bar, and all the others were already there and unchanged ?

Commodore64user · 2024-04-14T11:41:39Z

so trusting you.

don't trust me. go and find it and put it to the test. the check_func is under alternative status bar and it is the battery status one.

That was a polite way to say: "I don't want to spend time understanding the logic and test it" :), and to invite others who care to do so, and you to double check.

So, do you mean you just added ONE checked_func ? The one under alt status bar, and all the others were already there and unchanged ?

That is exactly what i mean, everything else was already there.

i also added an extra condition (to grey them out when progress bar not selected) to existing checked_func in the “progress bar” menu to some options i pulled out from a submenu formerly known as ‘style’. Those being ‘show chapter markers’, ‘marker width’ and ‘initial-position marker’.

Frenzie · 2024-04-14T11:48:00Z

@hius07

In this PR "divider" is a horizontal line dividing the status bar, "separator" is a vertical line separating status bar items.

Yeah, I don't think horizontal or vertical matters.

@Commodore64user

the word 'separate' is usually used to indicate physically removing something, as in 'separate the wheat from the chaff' or 'the fat was separated from the lean cuts'. 'divider' is used to break something up into smaller pieces, a whole into parts.

all that to say, I think 'divider' is better suited in this context than 'separator'.

If there ever was anything to this argument it was back in 1970. Microsoft and Apple have both called this concept separator for decades.

That's not an objection to divider, only to that argument, although of course it's hardly a ringing endorsement either. ;-) It might be worth noting that Apple uses divider for a line used to separate "content" and separator for something that's used to divide something list-like. Microsoft refers to the Apple divider as a splitter.

Edit: but in short, separator is the word you'll find in pretty much every UI.

Commodore64user · 2024-04-14T14:19:55Z

If there ever was anything to this argument it was back in 1970. Microsoft and Apple have both called this concept separator for decades.

is that for the end user or programmers? remember, this is the UI here; normal people don't speak programmer talk.

my Mac returns only one result for separator, and that refers to the colon that divide the time 12:30 into hours and minutes. To be fair it also returns nothing for divider so it looks like all of that is just 'programmer talk'.

Nevertheless I don't have a strict opinion, just saying people wouldn't normally use that word in that sense in normal speech, so if you lads want it back to separator is fine.

Frenzie · 2024-04-14T16:11:59Z

is that for the end user or programmers?

Yes. [Edit: that's a programmer joke to be clear, but also true.]

Here's the first search showing how to add or remove them: https://www.youtube.com/watch?v=Kvlm4acVTWM

my Mac returns only one result for separator, and that refers to the colon that divide the time 12:30 into hours and minutes. To be fair it also returns nothing for divider so it looks like all of that is just 'programmer talk'.

Apple has recently decided that spaces and dynamic spaces look cleaner than separators, so that's all you'll find in toolbar customization these days, even though they still have separators for their own use. (I'm inclined to agree with Apple but that's a separate discussion.)

It's the standard user-facing term. Shown below are standard toolbar elements as they've existed for decades. Using visuals is "recent"; I'd say 30 years ago in Windows 9x this stuff was only textual. A statusbar is a toolbar that doesn't have buttons but only indicators. A "real" toolbar can contain both.

(You can see a difference here between Apple using "dynamic space" and just about everybody else using "flexible space," but "expanding space" also exists.)

pazos

Please no complications.

Also a screenshot showing current and new would be awesome.

frontend/apps/reader/modules/readercoptlistener.lua

frontend/apps/reader/modules/readerfooter.lua

Commodore64user · 2024-04-14T21:42:44Z

Please no complications.

Also a screenshot showing current and new would be awesome.

it is a bit difficult for me, as I run this on a kindle 4 and for whatever reason, koreader doesn't capture screenshots there. this is one of the reasons I wrote this on the description

I encourage EVERYONE to download the files and run them on your machines, as that is the only way in which all of these changes will make sense. Read all the menus, play with them, in short; go have fun.

honestly, it will make a lot more sense this way.

Commodore64user · 2024-04-14T21:48:06Z

Question to all, how do I get one of those nice macOS KOReader emulators running on my laptop?

it would make my life a lot easier.

NiLuJe · 2024-05-15T20:28:00Z

Going to look at it tomorrow ;).

In the meantime, making sure it passes the linter would be a good start ;).

    frontend/apps/reader/modules/readerfooter.lua:1021:67: line contains trailing whitespace
    frontend/apps/reader/modules/readerfooter.lua:1022:46: line contains trailing whitespace
    frontend/apps/reader/modules/readerfooter.lua:1023:78: line contains trailing whitespace
    frontend/apps/reader/modules/readerfooter.lua:1024:45: line contains trailing whitespace
    frontend/apps/reader/modules/readerfooter.lua:1025:71: line contains trailing whitespace

Commodore64user

Whitespaces

frontend/apps/reader/modules/readerfooter.lua

NiLuJe · 2024-05-15T21:43:48Z

Which means we now get to my most favorite test in the suite...

spec/front/unit/readerfooter_spec.lua:54: Menu item not found: "Show all at once"!

stack traceback:
        spec/front/unit/readerfooter_spec.lua:54: in function 'tapFooterMenu'
        spec/front/unit/readerfooter_spec.lua:256: in function <spec/front/unit/readerfooter_spec.lua:233>

spec/front/unit/readerfooter_spec.lua:54: Menu item not found: "Auto refresh"!

stack traceback:
        spec/front/unit/readerfooter_spec.lua:54: in function 'tapFooterMenu'
        spec/front/unit/readerfooter_spec.lua:531: in function <spec/front/unit/readerfooter_spec.lua:500>

spec/front/unit/readerfooter_spec.lua:54: Menu item not found: "Show all at once"!

stack traceback:
        spec/front/unit/readerfooter_spec.lua:54: in function 'tapFooterMenu'
        spec/front/unit/readerfooter_spec.lua:702: in function <spec/front/unit/readerfooter_spec.lua:663>

frontend/apps/reader/modules/readerfooter.lua

Commodore64user · 2024-05-16T01:20:57Z

Few questions: what test is this? Why is it your favourite? And more importantly, pardon my french, what the h*ll is going on and how do we fix it?

hius07 · 2024-05-16T06:02:45Z

frontend/apps/reader/modules/readerfooter.lua

-        all_at_once = _("Show all at once"),
-        reclaim_height = _("Reclaim bar height from bottom margin"),
+        all_at_once = _("Show all selected items at once"),
+        reclaim_height = _("Overlap status bar"),
        bookmark_count = T(_("Bookmark count (%1)"), symbol_prefix[symbol].bookmark_count),


If we change to "Annotation count" what will be the abbreviation, instead of "BM"?

I suppose this is in reference to #11822, and you are asking about status bar showing letters instead of icons. the title here would then become "Annotation count" (I guess) so... AC?? is that already used? AN?

does anyone here actually uses the letters instead of icons?

That's for you to decide and fix (c.f., the symbol_prefix.letters table at the top of the file) ;).

we are not changing that here (or at least I am not going to), that is a task for another PR as there are a lot more instances of "Bookmarks" elsewhere that would need changing. one step at a time please

Frenzie · 2024-05-16T08:23:40Z

Why is it your favourite?

Sarcasm, I doubt I'll have time to check until at least Sunday though.

NiLuJe

Nothing much to add besides that initial nit.

Will give it a look see in practice on the emu, and another pass at the raw diff to avoid the comment distraction ;).

Reviewed 1 of 1 files at r13, 1 of 1 files at r28, all commit messages.
Reviewable status: all files reviewed, 81 unresolved discussions (waiting on @Commodore64user, @Frenzie, @hius07, @pazos, @poire-z, and @yparitcher)

frontend/apps/reader/modules/readerfooter.lua line 1453 at r23 (raw file):

Previously, poire-z wrote…

Classic comments please, only 2 dash --, and as it starts a paragraph, start it with an Uppercase (unlike inline comments which are ok lowercase).
Add a blank line before as it starts a logical section.

This line of dashes is still here ;).

frontend/apps/reader/modules/readerfooter.lua line 682 at r28 (raw file):

option_help_text["percentage"] = _("Progress percentage can be shown with zero, one or two decimal places.")
option_help_text["mem_usage"] = _("Show memory usage in MiB.")
option_help_text["reclaim_height"] = _("When status bar is unlocked and hidden, this setting will utilise the entirety of screen real state and will temporarily overlap status bar and text when unhidden.")

nit: I think we tend to prefer en_US, so utilize?

Less of a nit: The locked stated is irrelevant here, so I'd get rid of that mention for clarity (i.e., keep it to hidden/shown).

frontend/apps/reader/modules/readerfooter.lua

NiLuJe · 2024-05-16T22:00:48Z

Nothing jumped out in the practical test & second pass ;).

And this fixes the test:

diff --git a/spec/unit/readerfooter_spec.lua b/spec/unit/readerfooter_spec.lua
index 127f8eb6e..a3af93d84 100644
--- a/spec/unit/readerfooter_spec.lua
+++ b/spec/unit/readerfooter_spec.lua
@@ -253,7 +253,7 @@ describe("Readerfooter module", function()
                         footer.footer_text.text)
 
         -- disable show all at once, page progress should be on the first
-        tapFooterMenu(fake_menu, "Show all at once")
+        tapFooterMenu(fake_menu, "Show all selected items at once")
         assert.are.same('1 / 2', footer.footer_text.text)
 
         -- disable page progress, time should follow
@@ -269,7 +269,7 @@ describe("Readerfooter module", function()
         assert.are.same('0%', footer.footer_text.text)
 
         -- disable battery, percentage should follow
-        tapFooterMenu(fake_menu, "Battery status".." ()")
+        tapFooterMenu(fake_menu, "Battery percentage".." ()")
         assert.are.same('⤠ 50%', footer.footer_text.text)
 
         -- disable percentage, book time to read should follow
@@ -277,15 +277,15 @@ describe("Readerfooter module", function()
         assert.are.same('⏳ N/A', footer.footer_text.text)
 
         -- disable book time to read, chapter time to read should follow
-        tapFooterMenu(fake_menu, "Book time to read".." (⏳)")
+        tapFooterMenu(fake_menu, "Time left to finish book".." (⏳)")
         assert.are.same('⤻ N/A', footer.footer_text.text)
 
         -- disable chapter time to read, text should be empty
-        tapFooterMenu(fake_menu, "Chapter time to read".." (⤻)")
+        tapFooterMenu(fake_menu, "Time left to finish chapter".." (⤻)")
         assert.are.same('', footer.footer_text.text)
 
         -- reenable chapter time to read, text should be chapter time to read
-        tapFooterMenu(fake_menu, "Chapter time to read".." (⤻)")
+        tapFooterMenu(fake_menu, "Time left to finish chapter".." (⤻)")
         assert.are.same('⤻ N/A', footer.footer_text.text)
         readerui:closeDocument()
         readerui:onClose()
@@ -528,7 +528,7 @@ describe("Readerfooter module", function()
         assert.is.same(1, found)
 
         -- disable auto refresh time
-        tapFooterMenu(fake_menu, "Auto refresh")
+        tapFooterMenu(fake_menu, "Auto refresh items")
         found = 0
         for _,task in ipairs(UIManager._task_queue) do
             if task.action == footer.autoRefreshFooter then
@@ -538,7 +538,7 @@ describe("Readerfooter module", function()
         assert.is.same(0, found)
 
         -- enable auto refresh time again
-        tapFooterMenu(fake_menu, "Auto refresh")
+        tapFooterMenu(fake_menu, "Auto refresh items")
         found = 0
         for _,task in ipairs(UIManager._task_queue) do
             if task.action == footer.autoRefreshFooter then
@@ -699,7 +699,7 @@ describe("Readerfooter module", function()
 
         -- test in all at once mode
         tapFooterMenu(fake_menu, "Progress percentage".." (⤠)")
-        tapFooterMenu(fake_menu, "Show all at once")
+        tapFooterMenu(fake_menu, "Show all selected items at once")
         assert.is.same(false, footer.has_no_mode)
         tapFooterMenu(fake_menu, "Progress percentage".." (⤠)")
         assert.is.same(true, footer.has_no_mode)

frontend/apps/reader/modules/readerfooter.lua

poire-z · 2024-05-20T17:41:27Z

Fine with me (not re-reading the whole thing, I had enough of it :))

Still some CI failures:

[  ERROR   ] spec/front/unit/readerfooter_spec.lua @ 233: Readerfooter module should switch between different modes
[  ERROR   ] spec/front/unit/readerfooter_spec.lua @ 500: Readerfooter module should toggle auto refresh time task by toggling the menu
[  ERROR   ] spec/front/unit/readerfooter_spec.lua @ 663: Readerfooter module should support disabling all the modes

Not sure they are the same that @NiLuJe proposed a fix for (where it seems it just needed to get reported back the new menu title strings), but you @Commodore64user need to update spec/front/readerfooter_spec.lua as part of this PR, until we don't see anymore.

Not sure when to merge this, there's a lot of new translatable strings, so if soon we'll have to push a bit next release.
(I also have some fix waiting to readerfooter and readercoptlistener which would conflict with this PR - so holding on on my side - but let's get done with this PR.)

Frenzie · 2024-05-20T17:44:20Z

Not sure when to merge this, there's a lot of new translatable strings, so if soon we'll have to push a bit next release.

I'd push the next back to June unless there's a particular reason to get out an interim release (pre giant base upgrade).

So merging this should be fine.

Commodore64user · 2024-05-20T18:08:28Z

Fine with me (not re-reading the whole thing, I had enough of it :))

Still some CI failures:
[  ERROR   ] spec/front/unit/readerfooter_spec.lua @ 233: Readerfooter module should switch between different modes
[  ERROR   ] spec/front/unit/readerfooter_spec.lua @ 500: Readerfooter module should toggle auto refresh time task by toggling the menu
[  ERROR   ] spec/front/unit/readerfooter_spec.lua @ 663: Readerfooter module should support disabling all the modes
Not sure they are the same that @NiLuJe proposed a fix for (where it seems it just needed to get reported back the new menu title strings), but you @Commodore64user need to update spec/front/readerfooter_spec.lua as part of this PR, until we don't see anymore.

Not sure when to merge this, there's a lot of new translatable strings, so if soon we'll have to push a bit next release. (I also have some fix waiting to readerfooter and readercoptlistener which would conflict with this PR - so holding on on my side - but let's get done with this PR.)

Sorry I didn’t know i had to update that file too, will do so later today.

Commodore64user · 2024-05-21T19:08:29Z

am I still missing anything else that needs doing here?

Frenzie · 2024-05-21T19:15:54Z

If we want to change anything else we'll do it in a follow-up PR(s).

Commodore64user added 9 commits April 11, 2024 01:05

~~alternate~~ alternative status bar

b31284f

textOptionTitles wording changes

4d929bb

more wording changes

ac8f37a

more wording changes

ce5808f

added 'complications' to menu

3b54304

makeover

97abc36

special commit for testing

249d138

checked function added to battery comp. (alt status bar)

5e3013c

final changes to readerfooter

6a49707

yparitcher requested changes Apr 14, 2024

View reviewed changes

poire-z reviewed Apr 14, 2024

View reviewed changes

frontend/apps/reader/modules/readerfooter.lua Outdated Show resolved Hide resolved

typos

be132f7

pazos requested changes Apr 14, 2024

View reviewed changes

pazos reviewed Apr 14, 2024

View reviewed changes

frontend/apps/reader/modules/readercoptlistener.lua Outdated Show resolved Hide resolved

pazos reviewed Apr 14, 2024

View reviewed changes

frontend/apps/reader/modules/readerfooter.lua Outdated Show resolved Hide resolved

Commodore64user requested a review from NiLuJe May 15, 2024 02:14

Commodore64user commented May 15, 2024

View reviewed changes

Apply suggestions from code review

58ff86b

Commodore64user commented May 16, 2024

View reviewed changes

frontend/apps/reader/modules/readerfooter.lua Outdated Show resolved Hide resolved

comma

71552f3

hius07 reviewed May 16, 2024

View reviewed changes

NiLuJe requested review from Frenzie, hius07, poire-z and yparitcher May 16, 2024 21:41

NiLuJe requested changes May 16, 2024

View reviewed changes

Commodore64user commented May 16, 2024

View reviewed changes

frontend/apps/reader/modules/readerfooter.lua Outdated Show resolved Hide resolved

dashes gone

4f769d1

Commodore64user commented May 16, 2024

View reviewed changes

frontend/apps/reader/modules/readerfooter.lua Outdated Show resolved Hide resolved

z for an s

3b45777

Commodore64user commented May 16, 2024

View reviewed changes

frontend/apps/reader/modules/readerfooter.lua Outdated Show resolved Hide resolved

shown replaces unhidden

4a99922

Update readerfooter_spec.lua

04e01c5

Frenzie merged commit e859109 into koreader:master May 21, 2024
3 of 4 checks passed

Commodore64user deleted the status-bar branch May 21, 2024 19:18

[Status bar] Major UI makeover #11678

[Status bar] Major UI makeover #11678

Conversation

Commodore64user commented Apr 14, 2024 • edited by Frenzie

yparitcher left a comment

Choose a reason for hiding this comment

hius07 commented Apr 14, 2024 • edited

poire-z left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

hius07 commented Apr 14, 2024

Frenzie commented Apr 14, 2024

hius07 commented Apr 14, 2024

Commodore64user commented Apr 14, 2024

Commodore64user commented Apr 14, 2024

Commodore64user commented Apr 14, 2024 • edited

poire-z commented Apr 14, 2024

Commodore64user commented Apr 14, 2024 • edited

Frenzie commented Apr 14, 2024 • edited

Commodore64user commented Apr 14, 2024

Frenzie commented Apr 14, 2024 • edited

pazos left a comment

Choose a reason for hiding this comment

Commodore64user commented Apr 14, 2024 • edited

Commodore64user commented Apr 14, 2024 • edited

NiLuJe commented May 15, 2024

Commodore64user left a comment

Choose a reason for hiding this comment

NiLuJe commented May 15, 2024

Commodore64user commented May 16, 2024

Choose a reason for hiding this comment

Commodore64user May 16, 2024 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Commodore64user May 16, 2024 • edited

Choose a reason for hiding this comment

Frenzie commented May 16, 2024

NiLuJe left a comment • edited

Choose a reason for hiding this comment

NiLuJe commented May 16, 2024 • edited

poire-z commented May 20, 2024

Frenzie commented May 20, 2024 • edited

Commodore64user commented May 20, 2024

Commodore64user commented May 21, 2024

Frenzie commented May 21, 2024

Commodore64user commented Apr 14, 2024 •

edited by Frenzie

hius07 commented Apr 14, 2024 •

edited

Commodore64user commented Apr 14, 2024 •

edited

Commodore64user commented Apr 14, 2024 •

edited

Frenzie commented Apr 14, 2024 •

edited

Frenzie commented Apr 14, 2024 •

edited

Commodore64user commented Apr 14, 2024 •

edited

Commodore64user commented Apr 14, 2024 •

edited

Commodore64user May 16, 2024 •

edited

Commodore64user May 16, 2024 •

edited

NiLuJe left a comment •

edited

NiLuJe commented May 16, 2024 •

edited

Frenzie commented May 20, 2024 •

edited