-
Notifications
You must be signed in to change notification settings - Fork 0
Supplementary macro keyboard ideas with five rows of four (with knobs) #3
Comments
On reflection if the keyboard reprogramming supports layers, the final scroll wheel could toggle between the above lower-case romaji layout, a number pad, punctuation and the 6 missing English letters. The Update: Or perhaps |
Entry of the following composite kana is be possible in at least two ways with this reduced keyboard (here assuming ki plus small kana: きゃ : kixya / kya きぁ : kixa ← combination not used? gi plus small kana: ぎゃ : gixya / gya ぎぁ : gixa ← combination not used? ku plus small kana: くゃ : kuxya / qya ← won't have Q くぁ : kuxa / kwa / qa / gu plus small kana: ぐぁ : guxa / gwa shi plus small kana: しぁ : sixa / sya / sha zi plus small kana: じゃ : zixya / zya / ja じぁ : zixa ← combination not used? su plus small kana: すぁ : suxa / swa Likewise with ta-row (won't have So I think everything has a three-letter version the 20 key macropad could type, except くゃ くゅ くょ where lack the Q (so would need 5 letters here). |
As noted on #1 (comment) this is almost the M-type layout right hand 3x5 block plus the 1x5 home row from the left hand. |
My 20-key and 4-wheel keyboard arrived from AliExpress (as per the image earlier). macOS says: ❯ system_profiler SPUSBDataType
...
Composite Device:
Product ID: 0x2107
Vendor ID: 0x4132
Version: 0.00
Speed: Up to 12 Mb/s
Location ID: 0x01112000 / 9
Current Available (mA): 500
Current Required (mA): 100
Extra Operating Current (mA): 0
... Karabiner Elements recognises it as a keyboard:
Decimal 8455 = hex 0x2107 as the product ID, and decimal 16690 = hex 0x4132 as the vendor ID (presumably KeySilk as per the discrete branding on the front edge). i.e. HID 4132:8455 KeySilk Using Karabiner Elements EventViewer or just typing, the default behaviour is:
So 20 simple keys, and four knobs each able to send 5 different keys, making 40 potentially unique signals. The knobs are stiff to press though. Note the default layout duplicates a/b/c/d on the main keys and on the main knob control. That is extremely unfortunate as it means you have to reconfigure the keyboard - if they were all different by default I could remap everything in software 😢 The only documentation it came with was in Chinese, mostly QR codes to the KeySilk website including https://www.keysilk.com.cn/download.html which offers Windows and Mac downloads. The P.S. There are two tiny slide switches just above the USB-C socket (above the "4" key), on/off, and LEDs on/off. The LEDs do some apparently rainbow effect - each key lights up for about 1s when pressed down. P.P.S. If you wanted to use this as a 4x5 split keyboard (four rows of five), the most natural positioning is with the knobs above and the USB wire on the left. You could turn this round, and have the knobs at the front and the USB wire on the right, and type over the knobs with a suitable wrist rest. However, using my right hand the thumb rests on the large corner knob and can easily scroll it - but pressing the knob with my thumb is not comfortable. This blocks using the corner key as thumb button ("j" on the default layout). I can also tuck in my thumb to scroll the middle large knob, but again not press it. I can also accidentally scroll the small knob in the other corner with my palm/wrist (sometimes accidentally), but I can easily press it. As a left-hand split keyboard with the knobs at the bottom it works slightly better. The suggested orientation (20 keys on the left, knobs on the right, USB wire at the top) makes me think of a number-pad, and Japanese entry experiments aside, I will probably use it that way. |
The provided app works on an older Intel Mac, it has an English language setting but is only partially translated. I can at least see the default configuration as level 1: The "Help" link goes to http://www.coideakey.com/t/20 suggesting this is a "Coidea Smart keyboard". Page http://www.coideakey.com/t/10 is particularly helpful once translated (I think this was one of the QR code links). Double clicking a key should bring up the menu to choose the new action, but in English mode I just get these almost empty menus: Switching back to Chinese it works - although the menu listing is a little different, but the first is basic keys (pretty clear, and mostly in English anyway), and last is back (exit menu): The third set is media controls - see http://www.coideakey.com/t/12 but I recognise some from Japanese kanji and could confirm the rest by experiment and translating my guesses to simplified Chinese:
I'm inferring the second to bottom section is layer switching (I recognize the above/below/one/.../ten kanji). [Update: Yes, layer change confirmed] Note that when sending the multimedia actions, Karabiner Elements cannot see the events. TODO: Explore the mouse options (I want to map the main knob to the mouse-wheel for scrolling), and shortcuts (e.g. switching tabs/windows with a knob). |
The block above "Procreate" are predefined short cuts, e.g.
I'm trying 左标签 and 右标签 on one of the wheels for switching tabs. Another block are track-pad shortcuts matching 安卓 (Android) or 苹果 (Apple) for 上划 (swipe up) etc. |
The first physical prototype of the RomajiPad works! This used paper printed inserts for the key labels using relabelable keycaps (two parts, a black base and a translucent cover). The numbers and arrows reflect the alternative number-pad layer. In initial testing the Japanese full stop was wanted far more than the small key (which is not needed for small ya/yu/yo when entered as composite kana). Also explicit support for chording would be intuitive ( |
Brain dump:
Issue #2 looked at 15 keys macro keyboards with three rows of five (or five rows of three), but here's one sold on Ali Express with 20 keys and even more knobs on the right:
We could combine the romaji-based Godan キーボード 15 key flick-keyboard with an idea from #1, and give explicit keys to everything with a ten-ten version (adding G, Z, D, and B) or maru (adding P) as a fourth column:
a
/あ
m
/ま
k
/か
g
/が
i
/い
y
/や
s
/さ
z
/ざ
u
/う
r
/ら
t
/た
d
/だ
e
/え
w
/わ
n
/な
p
/ぱ
o
/お
x
/l
/小
h
/は
b
/ば
This re-ordering of the middle columns is based on Japanese vertical sorting top to bottom, right to left (a, ka, sa, ta, na, ma, ya, ra, wa), but with
h
/は
moved to have it next to it's modified forms.This eliminates almost all of the swipe actions needed with godan for typing basic Japanese, the rest handled punctuation, numbers, and the remaining English letters for international use (not important if this is to be a supplementary keyboard).
Essentially this would be just a remapped subset of A-Z in a mostly logical layout for typing romaji - although chording could be done with the left hand taking the first column, and the right hand taking the other three (and the keyboard placed centrally on a diagonal). That only seems useful if the OS doesn't have Japanese input setup, then we could sent raw unicode hex for the desired kana?
So, a cut down set of just 20 out of 26 English letters able to type the romaji for almost every kana.
This doesn't include any Japanese punctuation, nor the letter
V
needed for the rare ゔ/ヴ, entered as "va"/"VU" in romaji. The other letters are in fact not needed -Q
isn't used in any romanizations, whileC
,F
andJ
are specific to the Hepburn system to better match English pronunciation. Note computer entry of romaji treats the prefixX
andL
(little) the same.However, perhaps the
小
key which just needs to send the prefixx
orl
for making a small kana (where supported), might also work as a shift? e.g. Tap once to sendl
, but hold to turn the other keys into punctuation?As discussed on #1, the user would also need some additional keys to interact with the kanji selection (IME software). The clickable scroll wheels should cover the essentials once remapped, perhaps:
Main wheel:
Second wheel:
Third wheel:
That would leave a small wheel on the four-knob device pictured available for mainstream controls like volumn/mute, prev/next/pause, or zoom/reset-zoom.
Note this doesn't have a shift key to explicitly select katakana, for which the IME would have to be used.
The text was updated successfully, but these errors were encountered: