we need inbuild keymap switcher as commoditie

[trixie]

@kas1e

There is bunch of limitations then:

Of course, but to quote Steven: "Keep it simple and leverage what is already provided by the OS. Fancier features like flag graphics, etc. can be added later. The first version should just get the job done."

That env thingy imho fuzz from nothing

That's not completely true. A global environmental variable for the current keymap would be useful, and not just for the keymap switcher. The Locale Library already uses similar variables for the current language and charset.

[kas1e]

@Trixie

Of course, but to quote Steven: "Keep it simple and leverage what is already provided by the OS. Fancier features like flag graphics, etc. can be added later. The first version should just get the job done."

Then yep, right Imho those "flags" indication really cool and nice looking. Btw , what you think, is it possible later to make it like this: user running amigaos, at top bar nice flag are already appear as default, then user just press some combo and flag changes (together with keymap itself), and if user dbl-click on it (or one click, not so matter imho), then it spawn some menu where user choice keymap by mouse and settings, i.e. like this:



?

[trixie]

@kas1e

is it possible later to make it like this: user running amigaos, at top bar nice flag are already appear as default, then user just press some combo and flag changes (together with keymap itself), and if user dbl-click on it (or one click, not so matter imho), then it spawn some menu where user choice keymap by mouse and settings

Yes this is exactly how I want it to behave. However, neither the actual behaviour, nor making the commodity itself are a problem here. The problem is where and how to put the keymap indicator stuff. So unless this is agreed upon, I can't (and won't) start working on the code.

[kas1e]

@Trixie

Seems Amidock is good enough , just need some fixes there and there, but ! What we need, its just write concept of "top-bar" dockies and make it kind of "standard" and put it to Wiki article (so , when any programmer will ask : how to make topbar docky? we will point on that article).. I.e. something like

How to write top-bar dockys.

Top-bar dockys are the usual docky with only one exception that it is placed on top right of wb screen (usually it is top bar of wb screen, or, if topbar is disable by user it will be placed just at 0,0 top/right). The moment which you should note when write top-bar dockyis:

1. size of the docky indicator should be X,Y. Not bigger, not smaller, just to fit it to top-bar dock right (and your design will be by default mean that) (that one need to think about as well, because resolutions different, etc, maybe just that "top-bar" panel we can setup to some standard scaling, and that will be no problem).

2. you should add a name of the top-bar doc [there need to think about, if it will be some default os4 top-bar docky, then it should have some name, to which devs can connect their top-bar dockys]

3. ... etc..etc..some...crap..about..how...to...make...good...top-bar dockyes...

.. balbllab..

The problem is where and how to put the keymap indicator stuff. So unless this is agreed upon, I can't (and won't) start working on the code.

My bet is to have in mind that we will have standard top-bar docky , with common name like "top-bar docky" , so, any docks which want to be "top-bar" ones, should use that dock. So, indicator stuff will renders to that docky (those images-flags or whatever for start). And that all. When we will have it like this, we at least can:

1). click on it (then will think what to do next)
2). it will be docky in some panel
3). can works without topbar if it disabled by some (it will be placed just where topbar should be, and still will works and be visibly, etc).
4). and all the stuff which we discuss

Why it can be better to do it right from beginning: because print env on top bar and making docky which reacts fine are 2 different progs imho. Putting is not to docky will be bad because it will not fits to that "top-bar docky panel" , it will then again the same kind of hack like digiclock (no standard way of making top bar dockys => mess).

ps. check also plz another topic about "we need top-bar plugins/modules": Abalaban there bring few ideas as well, maybe also can help.

[Amigo1]

@kas1e

is it possible later to make it like this: user running amigaos, at top bar nice flag are already appear as default, then user just press some combo and flag changes (together with keymap itself), and if user dbl-click on it (or one click, not so matter imho), then it spawn some menu where user choice keymap by mouse and settings

Yes this is exactly how I want it to behave. However, neither the actual behaviour, nor making the commodity itself are a problem here. The problem is where and how to put the keymap indicator stuff. So unless this is agreed upon, I can't (and won't) start working on the code.

As I see it, unless someone from the "higher ups" :op speaks a word, you have the following possibilities and for the user comfort to set it how they like, you have to implement all of them: :-S

1) Option to have a flag icon or shortened keyboard language (eng, rus, etc) shown in Toolbar (just provide the ENV-Variable and the user should put it there himself with Workbench prefs.) Sadly, this prevents the users to see the active keyboard-language in a separate screen. And cha05e90 (and all other users which have the toolbar disable in prefs) to see it even from the Workbench screen.

2) Docky which displays the current Keyboard setting but with the possibility to be configurable in size. Since some like a Big sized Dock, others a 48x48 pixel dock and it really looks messy if different sized "icons" are in one and the same dock. Sadly this prevents the user to see the active keyboard in a different screen too unless AmiDock get enhanced to follow the screens.

3) a borderless(?) always on top(?) window which appears wherever the users sets its coordinates to appear, which -possibly automatically- follows the front-most-screen. BTW wasn't there a FRONTMOST tooltype to be set in some commodities once? But it would then just open in the front most screen. No FOLLOWFRONTMOST would be the right Tooltype to set.

4) a Window (commodity) which pops up temporarily on the front most screen by a key-combo, can be sticky or not, lets you select or cycle through the preset keyboard locales, and disappears again.

I think you are going to need 8 months for this.. I would need more most certainly.. :-p

[kas1e]

@Amigo1

Option to have a flag icon or shortened keyboard language (eng, rus, etc) shown in Toolbar

That one for sure can come later. For begining can be just flag icon, or just shorten keyboard language, not big deal and easy details imho. Just they should be in amidock, but look can be changed later.

Docky which displays the current Keyboard setting but with the possibility to be configurable in size

I assume that when it is in the docky, can be just used "scaled icon" options in amidock itself.

a borderless(?) always on top(?) window which appears wherever the users sets its coordinates to appear, which -possibly automatically- follows the front-most-screen. BTW wasn't there a FRONTMOST tooltype to be set in some commodities once? But it would then just open in the front most screen. No FOLLOWFRONTMOST would be the right Tooltype to set.

If indicator will be docky, there will be no needs for that imho. I mean, no need for coordinate, as coordinates will be your top-bar docky. As for follow to another screens : yep, that BZ entry which i will do , that need to be new option in amidock.

a Window (commodity) which pops up temporarily on the front most screen by a key-combo, can be sticky or not, lets you select or cycle through the preset keyboard locales, and disappears again.

Idea is to switch by combo between 2 keymaps which you set in settings, as well as dbl-click on the indicator which will give you ability to select it via mouse. Settings window also can be choicen from clicking on indicator, or just by exchange "show interface" and that usual commodity stuff.

[javierdlr]

@kas1e

is it possible later to make it like this: user running amigaos, at top bar nice flag are already appear as default, then user just press some combo and
...
The problem is where and how to put the keymap indicator stuff. So unless this is agreed upon, I can't (and won't) start working on the code.

Hi, well if it's a commodity it can be showed up in WB Tools menu (appmenuitem or whatever its called) with submenus with the keymaps (and IIRC you can add flag image too).

The workbench screenbar title has a Tool menu option and could look like this:
Tools
Restart
Keymap > EN <english flag image> <hotkey>
............ RU <russian flag image> <hotkey>
............ SP <spanish flag image> <hotkey>

[trixie]

@Amigo1

I think you are going to need 8 months for this.. I would need more most certainly.. :-p

Nah, docky stuff would probably take some time but a plain commodity is a weekend's job, really.

[abalaban]

After having experienced with my first docky (X1kTemp.docky) and played a bit with an (unreleased yet) Caps-lock indicator docky stuffs are not that time consuming once you've understood the basis (which I'm sure you already have . Feel free to ask me privately if you need.

[chris]

Hi, well if it's a commodity it can be showed up in WB Tools menu (appmenuitem or whatever its called) with submenus with the keymaps (and IIRC you can add flag image too).

Technically you could, but I don't think the AppMenu interface supports it.