status bar #11605
Replies: 6 comments 72 replies
-
The status bar is a manageable mess. The key concept to keep it manageable and thus maintained is to prevent new "complications" and encourage users to freely patch their own status bar with their own userpatches. New features should be quarantined for a while and get upstreamed after a careful consideration of usefulness vs spaguetti code ratio :) Just my two cents |
Beta Was this translation helpful? Give feedback.
-
I rather suspect someone purposefully refactored it from something like that into what it is to make it easier to read. ;-) That being said I don't really understand the question since you already give the answer yourself. |
Beta Was this translation helpful? Give feedback.
-
that snippet doesn’t work, which why I am asking for help getting to work. it is a rather feeble argument to say that the menus look like an alphabet soup because it is slightly easier to read some code, i do hope that is not what you’re all hinting. |
Beta Was this translation helpful? Give feedback.
-
Quite the contrary, the alphabet soup is caused by a bunch of proudly contributors implementing what they want to extend the program :) After years we figured out the best thing to do is set a scope, reject new features that are not deemed useful (or require a bunch of work for what is worth) and encourage further hacking using patches and plugins. It is a good thing that you want to improve the "alphabet soup". That improvement requires a disccusion*. What you want to change in the status bar menus?
|
Beta Was this translation helpful? Give feedback.
-
No issue with reorganizing stuff. Also, there's some mixed wording styles: I can somehow guess who among us wrote a menu item :) (I must have worded 30% to 50% of our menu items). There are some from others that I still find odd (ie. |
Beta Was this translation helpful? Give feedback.
-
since the unless there are objections... |
Beta Was this translation helpful? Give feedback.
-
since @poire-z and @Frenzie think it would be a good idea to discuss changes in menus first, I propose, following #11549 to re-organise the status bar... next?. Any thoughts? I haven't actually consider the final layout so have nothing to show yet but would love to know if it would be welcomed or not.
The only thing I have done so far is group all the "items" into their own setting (which incidentally I would like to rename to
complications
, like in horology, but for reading) but I have a problem...How do I turn this:
koreader/frontend/apps/reader/modules/readerfooter.lua
Lines 1973 to 1975 in fbd3e82
into something like this, or anything that works:
Beta Was this translation helpful? Give feedback.
All reactions