Skip to content

Qwerty layout split 3x5 keyboard with 3 thumb keys each#4

Open
peterjc wants to merge 1 commit into
lucmazon:masterfrom
peterjc:split_3x5_3
Open

Qwerty layout split 3x5 keyboard with 3 thumb keys each#4
peterjc wants to merge 1 commit into
lucmazon:masterfrom
peterjc:split_3x5_3

Conversation

@peterjc
Copy link
Copy Markdown

@peterjc peterjc commented Feb 14, 2025

As per #2, I wanted to try your heatmap tool with a Qwerty layout. I didn't really fancy defining a full staggered layout so went for a smaller orthogonal design instead.

(This is perhaps too niche to consider merging, but I'll leave that up to you.)

Typically small split keyboards like this use assorted key combinations to access additional symbols, numbers, or navigation keys like cursors. Very often this includes tap-vs-hold behaviour, whereby for example a thumb key might be space if tapped, but shift if held. That complexity seems beyond what this keyboard heatmap tool attempts to display.

Therefore the layout here as been simplified to just use two modifiers, left-shift on a left-thumb key, and AltGr on a right-thumb key. Then:

  • Base layer, lower case Qwerty
  • Shift layer, upper case Qwerty
  • AltGr layer, ANSI number row symbols along top, digits on middle row, and misc other punctuation from right side on bottom row including tab and escape.
  • Shift+AltGr layer, misc symbols including those top left/top right on ANSI/ISO (like back-tick, minus, equals) and currency symbols as the top row, and a vi-style row of cursors. Rest unused.

The thumb keys have been simplified to just left-shift, backspace, delete (on left) and then enter, space, AltGr (on right).

This means there is no ctrl, nor meta/command/windows, nor left-alt. i.e. This would not actually be practical for real use as standard keyboard shortcuts would be impossible. However, the goal was mainly to visualise the Qwerty part of the keyboard - and everything else tends to be highly personalised in the ergonomic keyboard community.

Example output using your provided heatmap.json (which includes lots of accented characters which are not supported on this layout):

Base layer, lower case Qwerty:

Screenshot 2025-02-14 at 11 32 53

Shift layer, upper case Qwerty:

Screenshot 2025-02-14 at 11 33 00

AltGr layer, main symbols and numbers:

Screenshot 2025-02-14 at 11 33 09

Shift+AltGr layer, misc symbols and cursors (no counts shown):

Screenshot 2025-02-14 at 11 34 12

Note initially the thumb keys are not rotated, but I can see how to add that level of polish.

Typically small split keyboards like this use assorted key combinations
to access additional symbols, numbers, or navigation keys like cursors.
Very often this includes tap-vs-hold behaviour, whereby for example a
thumb key might be space if tapped, but shift if held. That complexity
seems beyond what this keyboard heatmap tool attempts to display.

Therefore the layout here as been simiplified to just use two modifiers,
left-shift on a left-thumb key, and AltGr on a right-thumb key. Then:

* Base layer, lower case Qwerty
* Shift layer, upper case Qwerty
* AltGr layer, ANSI number row symbols along top, digits on middle
  row, and misc other punctuation from right side on bottom row
  including tab and escape.
* Shift+AltGr layer, misc symbols including those top left/top right
  on ANSI/ISO (like back-tick, minus, equals) and currency symbols
  as the top row, and a vi-style row of cursors. Rest unused.

The thumb keys have been simplified to just left-shift, backspace,
delete (on left) and then enter, space, AltGr (on right).

This means there is no ctrl, nor meta/command/windows, nor left-alt.
i.e. This would not actually be practical for real use as standard
keyboard shortcuts would be impossible. However, the goal was mainly
to visualise the Qwerty part of the keyboard - and everything else
tends to be highly personalised in the ergonomic keyboard community.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant