Discovery

[06:40] As I was writing the 100th log for #SecSavr Suspense [gd0105], I discovered this on the front page of Keyboard Builders' Digest:

Now I had actually found out about Tapio a bit after I finished up the draft version of ZEV-XS. The thing was that it was explained to me as a left or right handed layout. As it turns out, it's like Tetent where you can have both. The trick is to actually stagger the taps on each hand, whereas for Tetent, I was expecting myself to tap all 6 Tetrinsics at the same time. Another difference is that the layout is mirrored in Tapio (see below), whereas for Tetent it was alway going to go from left->right on both sides (similar to how I've done the numbers in the number layer on the ZEV-XS layout).

I remember seeing the left-hand variant and saying "Yeah I'd but the e on this side and the t on that side... and perhaps see what other things I could transfer from ZEV-XS..." and it turns out that the creator says that it's all mostly personal preference and that moving keys around seems to be encouraged:

The really interesting stuff is these videos of him using varying layouts (but the same idea):

Considering this layout is 1 character per hand, I've got some hope that I'd be able to at least hit 200wpm when Tetent can do up to 3 characters. Remember, I've still got to contest with the mental overhead. Perhaps Tapio's onto the right strat by having each hand out of phase with each other, because then I only need to mentally track 3-4 haptic events at one point in time instead of 6-8.

[12 Aug]

I've tried to take taipo.h from this current Taipo PR to QMK, but for starters, it's about 3K bytes and so it and Vial won't fit into the Pro Micro. From this experience (and reading about the development issues for the OS3M Mouse), I'm now always going to avoid microcontrollers with less than 64KB of flash. Anyway, I spent the long process of copying my layout into the FW itself and set it up such that Taipo was enabled when Vial was disabled (hence just a stock standard QMK firmware). At least the good news is that I've implemented the unicode characters directly instead of Vial macros. 

Unfortunately, while the code compiles and the CAPS_LOCK leds light up, a lot of other stuff broke and I can't type anything under the 2nd row.

This is my most recent code.

I should also mention that Vial currently only supports 16 custom keycodes (so trying to add the 20 Taipo keycodes wasn't going to work), though it seems that the fix will be in some future release.

[13 Sep] Future logs about the Airberries can be found here.