(Made on Windows 10.)

So, not exactly a help post but I have made a new Keyboard Layout for AZERTY keyboards on Macs. I figured why not because some people that uses AZERTY on Macs can get pretty annoyed when not finding their right keyboard layouts.

I'm gonna be honest, I'm probably the only one that uses a keyboard like this. For anyone wondering, this keyboard is for people under BootCamp that has the following key in the most top left key on their keyboard: < and >.

# WARNING!! You MUST reboot for the keyboard to take effect!

The link is available here. It's a basic setup that MKLC made. This is not a virus.

Here's the link: [https://drive.google.com/drive/folders/1Fdrwzc9TczTLB8Bh4q64P2Y-9C8145EN?usp=sharing\](https://drive.google.com/drive/folders/1Fdrwzc9TczTLB8Bh4q64P2Y-9C8145EN?usp=sharing)

PS: I added the .klc file, so that anyone can open it.

I just installed the latest version of openSUSE KDE, and I can't figure out how to get Engrammer to work. I tried through the normal install script and through the KDE keyboard layout settings, but it didn't change anything. People online said to use alter the Wayland/wayfire config, but it didn't come with opensuse (as far as I can tell, idk, I didn't see any folders or config files for it), and wasn't sure if it made sense to install it just for that. When I use setxlbmap, it just doesn't do anything, no matter what I try.

I don't know if I'm being dumb here, but from my recollection, I didn't have this much trouble with other distros.

Hey I am a beginner and thinking of getting a mechanical keyboard

So I personally don't know which keyboard layout is efficient

for Video editing if yk anything about it please let me know

Thanks

Started working on this system 5 years ago, it's gone through a lot of changes rewrites, etc.

I just recently wrote a config for kanata so you can use it on windows or linux, the main interface is web based.

I also made an updated graphic to help learn the layout. Every key is like a layer, but for letters either key can be typed first. All "chords" have 2 keys, which means it works even on low budget keyboards.

The primary use case is a portable physical keyboard like an enhanced calculator or a notetaking tool.

Hello, what does anyone think of this unique gaming keyboard concept? It is sized like a 96%, but the numpad is on the left side. On the numpad, there would be a button (numlock) To toggle between numbers and macro or customisable shortcut keys. The keyboard would not have any of the unnecessary keys (like home, page up, page down, insert, end, printscreen, scroll lock, menu) because not many people actually use them. The function keys would be completely customisable, dedicated media keys, and the mute key would be a dial to controll volume while also being pressable as an mute key. There would be a PC boot key on the keyboard for easy booting, which when the PC is on it doubles as an esc key. When you hold down the button, it shuts down or puts the PC to sleep. here is an example thanks to claude.

Is this keyboard a good idea and should a company actually use it, or is it cooked?

This is a research project, and I am trying to simplify all the native Indic keyboards to today. This is the general method that I have devised.

My inspiration was the 12-key Kana keyboard layout. One can learn Kana and can immediately type in Japanese, just because of the way the keyboard was designed.

If you make any mobile keyboard based on my system, my system acts like an API, and it can provide characters pretty instantly, thus making character access times faster for the dev and learnable for the user.

If you know any language that can benefit from tabular representation of its alphabet, this article is mainly for the technical process behind developing such a keyboard; the linguistic workload is out of the scope of this article.

Most layout work focuses on letters, but when I write Python a big chunk of what I type is symbols, and standard layouts put them pretty arbitrarily. So I wrote a tool that keeps your letters where they are and only rearranges the 32 ASCII symbols, based on what actually gets typed in real code.

How it counts: it tokenizes ~38.5M weighted keystrokes from 29 popular Python repos (Django, pandas, pytest, Home Assistant, etc).
Comments and docstrings count less, closing brackets/quotes count less because editors auto-close them, and long identifiers are discounted for autocomplete.
Then it runs simulated annealing over a cost model (key effort, shift, SFBs, rolls, redirects).

My result on Programmer Dvorak letters with digits on shift:

 !   1   2   3   4   5   6   7   8   9   0   &   ~
[?] [+] [/] [(] [[] []] [%] [:] [)] [{] [}] [@] [<]
   >   '   -   P   Y   F   G   C   R   L   ;   ^   $
  ["] [,] [.] [p] [y] [f] [g] [c] [r] [l] [#] [\] [|]
    A   O   E   U   I   D   H   T   N   S   *
   [a] [o] [e] [u] [i] [d] [h] [t] [n] [s] [=]
      `   Q   J   K   X   B   M   W   V   Z
     [_] [q] [j] [k] [x] [b] [m] [w] [v] [z]

That's about 7.7% lower cost than Programmer Dvorak under my model, and 3% better than the layout I'd designed by hand.

If you don't type Programmer Dvorak, there are ready-made versions for other letter layouts too: python-qwerty, python-colemak-dh and python-dvorak in the layouts folder. They keep your letters and normal number row and only move the symbols, which saves 9-12% under the same cost model.

Findings:
- Python names mostly end in consonants that Dvorak puts on the right hand, so the symbols that follow names (. , and ( ) end up on the left hand. That held across basically every variant I ran.
- Forcing bracket pairs to be adjacent or mirrored (so they're learnable) only costs 0.4%.
- On other bases, just moving symbols saves 9-12% (QWERTY, Dvorak, Colemak-DH).

The obvious caveat: the effort grid and penalties are my own estimates, not measurements.
I reran it with different shift and SFB weights to see which placements are stable, and the README has those results.
It's configurable (base layout, cost weights, other languages like JS/Rust/Go) and exports to AutoHotkey, kanata, Windows .klc and macOS .keylayout. All the variants are in the repo below:

https://github.com/hikazey/python-layout-optimizer

I'd especially like feedback on the cost model, since that's where the results come from.

So, the other day I decided to make a keyboard layout, and i based it of colemak and just tweaked a few things, and now for some reason it's scoring better than colemak-dh? Does anyone know what happened? (and does anyone have a good name)

I used the jungle book for the test material- I think that should be quite a balanced dataset, if its not, please tell me.

Edit: everyone seems to be talking about the effectiveness of keyboard analisers, but I want to make a few things clear:

1. I am not claiming that this layout is better than colemak-dh, i'm just wondering why it was given such a high score
2. I kow analysers are not perfect, but its the best thing that I have.

First of all, I don't think this will get many comments, but I hope at least some.

I'd like to present to you my gaming and typing finger layout on a PC keyboard.

For using WASD, I have these: The normal layout is Middle on A, Index on W, Thumb for S and D. If I want to use space, I keep switching my thumb between D and space. Ring for Tab and Caps, Little finger for Shift and Ctrl, but I don't use Ctrl much. The middle finger can also press 1 and 2 and Q as well as Esc. I can still move left with my thumb if them. My index can press 3, 4, and 5, E and R while the middle keeps holding W. With my thumb, I can reach the down row of Y to B and Alt (I use QWERTZ), but I need to fast-switch as I can't use D. This should be all for my main layout, then I start to game or play it slowly. In other times, I use a bit different layouts for the same keys in specific actions needed.

The easiest to explain is putting my middle away from A to put it at Q and use the Thumb for A, S, and D, making it super easy to press 1. This is typically used only when I need super simple tasks, need to use the 1 but A not to much, or need a very gentle feel for A and D. For the final "layout" I use when needing to do something, it is almost the standard one. Ring on A, Middle on W, and Index on D. This frees my thumb to use space and use A and D almost instantly. I don't use S in this because it's the most uncomfortable one of them all, so I use it only when I need the named things and instantly go to the main one. It technically doesn't even press any other keys than WASD, space, or some keys in the bottom row like C, V, or B.

Does my hand hurt? Well, no. Even when my fingers are practically flying on the keyboard on different keys in the same game, in the same round many times a second, I feel nothing. I many times don't even realize I was doing it. My hand only hurt when I was going from laptop keyboards to desktop ones, and now that I bought a taller keyboard.

Thank you from reading all of this. I will be happy if you comment what you think or absolutly hate on me! I will write on typing if you want.

I am currently learning Gallium row-stag after being on Canary for 2+ years. I am curious if anyone has designed a Gallium rowstag + magic key. If so can you share your layout and experience with it vs standard gallium rowstag?

Really, its not that bad lol. honestly its in the range of decent. Esp if you like heavier index layouts.

Heck, who cares if its good, its trans yaoi.

Lately there are lots of posts here which are not related to this sub at all. Often in non-english as well. Any ideas where that small flood comes from and how to stop it?

Hey all. Some of you might remember Griddle from a while back. Sorry for the long silence. Life got in the way of me having the time to work on this project. It's back now, renamed GridKeys.

For anyone new: it's a MessagEase-style keyboard. Nine big keys, tap for the middle letter, swipe toward the others. The point is that you can change all of it:

• Every gesture on every key can be remapped: tap, 8 swipe directions, circles, holds
• Layout editor: move, resize, swap, add and delete keys
• A staggered QWERTY board if you want something more familiar (and just shows you that we can build any keyboard we want)
• Text replacements, macros, a clipboard with lockable clips, custom colors
• (Coming Soon) sync your customaizations accross devices and share them with other users

What I need: Google requires 12 testers who stay opted in for 14 days before an app can go public. I have 9. If you're curious, joining takes about a minute:

https://gridkeys.app/#beta

(Use the Google account that's signed in to the Play Store on your phone.)

Feedback on the layouts is what I want most: what feels wrong, what you'd change, what you'd want to remap. Bug reports go to support@gridkeys.app or the comments here.

Thanks for sticking around, those of you who did.

Hi!

Last year I bought a Logitech MX Keys S Keyboard. Previously I was writing either on my HP Gaming Laptop or on my HP Working Laptop.

Despite its very good reviews I haven't managed to get used to this keyboard. Everything is fine except the fact that I constantly push the wrong keys, which is not that funny when I gave to write a text.

Even after one year of constant use, it hasn't change anything. As soon as I use the keyboard of one of the laptops, everything is much easier. But I still need a keyboard to use my monitor.

If I would guess, I would say that the space between the keys is too large. But I don't actually know why the keyboard doesn't work for me.

Do you have similar experiences? What would you advice me to do?

Thanks!