NickelMenu: An integrated launcher for Kobo eReaders

[geek1011]

NickelMenu v0.4.0

This release adds an experimental configuration option to change the main menu label and has some more internal refactoring and cleanup. There should not be any noticeable change for users.

• There is now support for an experimental `experimental:menu_main_15505_label` configuration option to set the main menu label on the new 4.23.15505+ bottom nav. This option is experimental and may be removed or changed at any time.

See the release on GitHub for more details.

[jackie_w]

Just some feedback ...

Everything seems to be working OK for me with v0.4.0 but the pop-up info display from one of my config options is no longer as "neat" as it used to be.

I'm using this option to completely delete any existing screenshots from the Kobo followed by disabling the screenshot option

menu_item : main : * Screenshots del/off : cmd_output : 500:rm -v /mnt/onboard/screen_*.png
  chain_success : nickel_misc    : rescan_books
  chain_always  : nickel_setting : disable : screenshots

Let me stress, it still works OK, but the pop-up display of removed .pngs is now shown as one long string. It used to neatly display one .png per line, which was easier to read (if I wanted to). I know it's only cosmetic but I'm passing it on anyway ...

I'm not sure which earlier version had the one-per-line display.

[geek1011]

Originally Posted by jackie_w

Just some feedback ...

Everything seems to be working OK for me with v0.4.0 but the pop-up info display from one of my config options is no longer as "neat" as it used to be.

I'm using this option to completely delete any existing screenshots from the Kobo followed by disabling the screenshot option

menu_item : main : * Screenshots del/off : cmd_output : 500:rm -v /mnt/onboard/screen_*.png
  chain_success : nickel_misc    : rescan_books
  chain_always  : nickel_setting : disable : screenshots

Let me stress, it still works OK, but the pop-up display of removed .pngs is now shown as one long string. It used to neatly display one .png per line, which was easier to read (if I wanted to). I know it's only cosmetic but I'm passing it on anyway ...

I'm not sure which earlier version had the one-per-line display.

That's...odd. It's certainly not a change in NickelMenu itself. Does it show multiple lines if you use "echo test; echo test" as the command?

[jackie_w]

Originally Posted by geek1011

That's...odd. It's certainly not a change in NickelMenu itself. Does it show multiple lines if you use "echo test; echo test" as the command?

I'm quite happy to test any suggestion but you'll need to spell it out. What, exactly, did you want me to delete/add? My NickelMenu foo is very basic.

[bajillioneer]

Can someone please give me a sample code for creating a menu for koreader and plato? Thanks.

[Alan_S]

They are in instructions.

[geek1011]

Originally Posted by bajillioneer

Can someone please give me a sample code for creating a menu for koreader and plato? Thanks.

@NiLuJe's one-click install packages has them.

If you use kfmon, you can use "generator:main:kfmon". If you want to launch it directly, see the KOReader wiki.

[jackie_w]

Originally Posted by geek1011

That's...odd. It's certainly not a change in NickelMenu itself. Does it show multiple lines if you use "echo test; echo test" as the command?

I think I may have figured out what you meant. The following menu item results in a pop-up display shown in the screenshot.

menu_item : main : * PGtest : cmd_output : 500:echo test1; echo test2; echo test3

[geek1011]

Originally Posted by jackie_w

I think I may have figured out what you meant. The following menu item results in a pop-up display shown in the screenshot.

menu_item : main : * PGtest : cmd_output : 500:echo test1; echo test2; echo test3

OK, thanks. I guess it's an issue in the way the output is shown. I'll look into that as soon as I have time (feel free to open an issue on GitHub).

P.S. What's up with the grey background on the navigation? Are you working on something with the CSS?

[NiLuJe]

I see that our good friend Aaa Zzz has been busy ;p.

[jackie_w]

Originally Posted by geek1011

OK, thanks. I guess it's an issue in the way the output is shown. I'll look into that as soon as I have time (feel free to open an issue on GitHub).

As long as you don't think it's frivolous! I wouldn't have mentioned it were it not for the fact that an earlier release (3.2 maybe???) displayed it neater.

Originally Posted by geek1011

P.S. What's up with the grey background on the navigation? Are you working on something with the CSS?

Kind of. It's not meant to be pretty. It's my experimental Kobo, aka the sacrificial goat.

When I'm trying to figure out what the various nickel .qss resource files do, I need to colour in the backgrounds in various shades of grey to see where one widget ends and the next one starts. It's just as well my screenshot was the Home screen rather than the MyBooks list which looks like a patchwork quilt!

Anyway, I blame you for all this. Once you'd provided the resource names for each of what used to be approx. 200 anonymous amorphous blobs of CSS, it became worthwhile (to me, not a sensible person) to go through them systematically trying to piece together the GUI jigsaw.

[Terisa de morgan]

A totally frivolous question: is there any way to group options in the menu, using bolder lines or something like that? It's aesthetical but... if I don't ask....

[PeterT]

Any way to define the same action in multiple locations other than replicating the line but changing the location?

[geek1011]

For anyone who hasn't noticed yet, I made a webpage for NickelMenu a few weeks ago. It's basically the information from the first post plus some screenshots, a documentation popup, a nicer design, and a few other minor improvements.
___

Originally Posted by Terisa de morgan

A totally frivolous question: is there any way to group options in the menu, using bolder lines or something like that? It's aesthetical but... if I don't ask....

Not currently, but it wouldn't be too hard to implement. I'll probably try adding an experimental "menu_separator" config entry type for the next version (which I'll start working on after I get around to finishing the dictutil stuff) which makes the separator bolder (or something equivalent).

Originally Posted by PeterT

Any way to define the same action in multiple locations other than replicating the line but changing the location?

Not currently. I might consider that for the future, most likely in the form of new "group_item" and "menu_include" config entry types.

[Terisa de morgan]

Originally Posted by geek1011

Not currently, but it wouldn't be too hard to implement. I'll probably try adding an experimental "menu_separator" config entry type for the next version (which I'll start working on after I get around to finishing the dictutil stuff) which makes the separator bolder (or something equivalent).

Thank you very much, I know it's a minor detail but I'm a bit picky with these things.