Settings: Keybindings

[Melber]

I'm sorry, but that is so image is so ugly that I'm looking at an alternative. Check this LO table, for instance, that I have only half finished; need to fill in rest of keys, color-code modifiers, etc.. Could be used as a PDF, image, etc.

Changing the font from monospace to something else won't rescue it?

OK, no problem, eye of the beholder...I personally have issues with serif fonts, wrong way round side labels and uneven column widths

Undecided what the best format is.
Not so sold on the idea of using pdf/image files. Presuming the aim is that, once finalised, the list won't be changed too often, but if it does need to be updated somebody then needs to go through and create new pdfs/images for all the translations.
If it's just a text file, what's the advantage over just opening the keys file directly?

Maybe I could look at making a yad form to get it looking table like...

Just as a test, I ran it through DeepL as a PDF -- BTW, DeepL now allows us with our Pro account to download that as a Word doc, suggesting the option of providing that so the user could change to individual settings, maybe with a button to edit on the GUI (?)

Needs to be editable, there's stuff in there that needs to be corrected, eg. Press != Presse in this context, Print Key != Taste drucken, Windows not translated...somebody is going to have to go over the translations to at least correct the nonsensical stuff.

[Jerry3904]

OK, no problem, eye of the beholder...I personally have issues with serif fonts, wrong way round side labels and uneven column widths

Fonts and widths easy to change, I like the labels but...

Not so sold on the idea of using pdf/image files. Presuming the aim is that, once finalised, the list won't be changed too often, but if it does need to be updated somebody then needs to go through and create new pdfs/images for all the translations.

True, but I personally don't foresee a need for our changing these common bindings

If it's just a text file, what's the advantage over just opening the keys file directly?

Because it's nearly unreadable for a new user!

Anyway, it's just an idea. If anyone wants to play around, I've attached the completed draft.

[Jerry3904]

Saturday morning and a lot of coffee have produced another ("just an") idea:

--top: "This tool provides convenient access to keyboard shortcuts, called "keys" in Fluxbox."
--Button 1: "View commonly used shortcuts"
--Button 2: "View or edit the config file"
--Help: maybe a short dedicated vid?

I'm done.

[siamhie]

IMHO best have a launcher on the panel to a pic/ image or even text file with the fluxkey combinations.

Couldn't the user just add an entry to the tint2 panel to open the keys file? I quickly threw this together and it seems to work.

Found an icon that closely represents key-bindings.

key-binding.png

Then opened tint2 settings and added a button. Now when I click on the button it opens the fluxbox keys file.



Just thinking out loud.

[Jerry3904]

Sure. But as I wrote in the top post in this thread: 1) we like to keep the default panel uncluttered, and 2) the keys file is not an easy read.

This thread is about the "what and how" of a user-friendly app into the Settings dashboard...

[Melber]

@Jerry3904
next attempt with yad...this time as a form with side tabs

230909-keybindings.png

Still too ugly?
(nb. text formatting will vary a bit depending on font style and size)

Script attached if you want to try it out

mxfb-keybindings-230909.tar

[Jerry3904]

That looks much better! Let me give it some testing and look closely at the source file b/c I made a number of changes for me table that I thought might be an improvement.

[siamhie]

Sure. But as I wrote in the top post in this thread: 1) we like to keep the default panel uncluttered, and 2) the keys file is not an easy read.

OK. Will this eventually change the menu entry for the keys file?

Code: Select all

[exec] (Keys) {exo-open ~/.fluxbox/keys}

[Jerry3904]

I think not.

[Jerry3904]

@Melber I've spent some time on your terrific rewrite--it works very well and looks much nicer.

I looked long and hard at the GUI and went through the code. I incorporated my changes into the attached file, and include a diff file so you can see what I've altered.

quickshot_230909_165516.png

My changes include:
--correction (e.g. of the keys file itself: move does not need, or work with, the Alt)
--text revision (TEXT1)
--text format (e.g., use of bold on tabs)
--clarification (e.g., replacing "KP" with "on keypad" inside the first column)
--simplification (e.g., removing clusters of letters/numbers) << I find them unnecessary, confusing and difficult to translate
--minor code change (e.g., adding a "gettext" to TEXT1).

Hope this is useful--see what you think.