mult keyboards with same layout implemenations ideas

[molleweide]

Yo!!!

I have thought about it and it would be nice if you could create a tiny defsrc file for each keyboard you own and then
manage the actual custom layout you use with kmonad in a single file. I start a discussion thread on this here.

For example, in my use case, I use a 3 by 5 minimal layout which means that my layout fits within any keyboard that exists out there, so therefore I am imagining something like this:

# defsrc'es
- macbook_pro_intel_defsrc.kbd
- m1_mac.kbd
- my_wierd_qmk_keyboard.kbd

# main kmonad layout
- main.kbd

Then, the next step is to modify the parser or something in the core that accounts for this.
I am imagining that one sources the main.kbd into each defsrc and you also would have to
specify which positions in the keyboard array that would correspond to the main layout.

I am not so good at haskell still but if I get good enough I want to implement this.
It feels like you'd take the current parser functionality and make it into a two step process kind of.

This idea makes sense, right?? :D

[MuhammedZakir]

IIRC, something like this was discussed previously in an issue. I think this we will be easy to do when the whole code refactor is done (especially the work in tinker branch).

Btw, you can use a shell script to do what you want.

#!/sbin/env zsh

local defsrc="${K_DEFSRC:-$HOME/.config/kmonad/defsrc.kbd}"
local baselayer="${K_BASELAYER:-$HOME/.config/kmonad/ansi_base.kbd}"

# $1 => config
# $2-$n => kmonad args
exec kmonad =(cat "$defsrc" "$baselayer" "$1") "$@[2,-1]"

E.g.

env K_BASELAYER=$HOME/.config/kmonad/iso_base.kbd $HOME/.local/bin/kmonad_m $HOME/.config/kmonad/80keys.kbd

[molleweide]

woaw, I have to try this!!

[tydazzz1]

env K_BASELAYER=$HOME/.config/kmonad/iso_base.kbd $HOME/.local/bin/kmonad_m $HOME/.config/kmonad/80keys.kbd

[molleweide]

@MuhammedZakir if you have time may I ask you for your opinion on this because I am unsure if this will work or not.

I have been looking for a while now at your code snippet above and re-read the tutorial.kbd, and my question is how I specify where in the defsrc that my sublayout should be mapped to. As an example I have provided my own layouts that I want to use
below. First comes my three hardware keyboards into which I want to map my minimal layout which is located at the bottom.
I have replaced all chars with XXs and underscores to make it easy to see how things should fit together.
Will this work, and if so would you please mind explaining to me how I can map the minimal layout into the three above.
I am not sure if I am asking for too much here but hopefully it will be helpful for others as well.

I also realize above that the laptop keyboards have 5 bottom row keys and the ergodox has 6, therefor I am mapping
both inner thumbs to space in order to have the same muscle memory everywhere . So in the ideal case I'd like to
ignore one of the inner-thumb-keys on the laptop layouts.

;; 1. Below, are my three hardware keyboard layouts.
;; I have replaced the keys that are supposed to be replaced
;; by my 5 by 3 layout with underscores to make it easy to see
;; what I am trying to achieve.

(deflayer BASE_ERGODOX
  XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX
  XX   _    _    _    _    _    XX   XX   _    _    _    _    _    XX
  XX   _    _    _    _    _              _    _    _    _    _    XX
  XX   _    _    _    _    _    XX   XX   _    _    _    _    _    XX
  XX   XX   _    _    _                        _    _    _    XX   XX
                           XX   XX   XX   XX
                                XX   XX
                      XX   XX   XX   XX   XX   XX
)

;; in the layouts below, which are my standard lapo keyboards, I have shifted
;; `zxcvb` one step to the left in order to achieve a more comfortable 3 by 5
;; layout

(deflayer BASE_MACBOOK_PRO_SWE
  XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX
       XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX
  XX   _    _    _    _    _         _    _    _    _    _    XX   XX   XX
  XX   _    _    _    _    _         _    _    _    _    _    XX   XX
  XX   _    _    _    _    _    XX   _    _    _    _    _    XX   XX
  XX   XX   _    _              _              _    _    XX   XX   XX
)

(deflayer BASE_MACBOOK_AIR
  XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX
  XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX   XX
  XX   _    _    _    _    _         _    _    _    _    _    XX   XX   XX
  XX   _    _    _    _    _         _    _    _    _    _    XX   XX
       _    _    _    _    _    XX   _    _    _    _    _    XX   XX
  XX   XX   _    _              _              _    _    XX   XX   XX
)

;; 2. And now follows my minimal layout. that should go into the layouts
;; above. 

(deflayer MINIMAL_SUBLAYOUT
    XX    XX    XX    XX    XX         XX    XX    XX    XX    XX
    XX    XX    XX    XX    XX         XX    XX    XX    XX    XX
    XX    XX    XX    XX    XX         XX    XX    XX    XX    XX
                XX    XX    XX         XX    XX    XX
)

[MuhammedZakir]

I usually search using symbols rather than keywords. In this case, <(. Searching using a partial sequence usually get better results.

[MuhammedZakir]

Which version of KMonad are you using?

[molleweide]

nice yeah I have started to understand that searching like that is good. which search engine to do you mostly search for code when you learn?

kmo version = 0.4.1, commit 1e432897dd5b7f8b2c2202e577ef22c58fdc5e5a

[MuhammedZakir]

nice yeah I have started to understand that searching like that is good. which search engine to do you mostly search for code when you learn?

I use DuckDuckGo and Startpage.

kmo version = 0.4.1, commit 1e432897dd5b7f8b2c2202e577ef22c58fdc5e5a

master branch or keycode-refactor branch?

[molleweide]

Master branch

[manna-harbour]

Here's a work around using a macro processor: #435.

[molleweide]

Cool i'll check it out!! I think I saw this project or similar before when I got my first qmk keyboard. It is interesting to shift the keyb up and use mult thumb keys!

[molleweide]

Here's a work around using a macro processor: #435.

Does miryoku implement mouse keys? And if so, to what extent?

[manna-harbour]

The mapping with the shifted rows does work, and you can use it, but it is very weird. You might use it if you've completely forgotten how to use a normal keyboard and you suddenly had no choice. But there are a couple of other options included. The"lite" mapping keeps the traditional home positions and adds only alphas, home row mods, and the Nav layer, so that should be completely usable. But I think the main use would be on non-programmable ergo boards, or if you're considering a programmable ergo board but want to try the keymap out first.

On other Miryoku implementations I used macro to map the keymap onto different physical layouts, but in KMonad that's not needed as defsrc does the same thing.

Miryoku KMonad uses mouse keys on the host for the mouse layer, but I might add some alternatives from #370.

[molleweide]

Cool, i am using a 5x3 layout already. I will see if I can try this layout with my setup.

Are the host mouse keys on macos hard coded to the chars as per the docs or can one reprogram the keys? Ideally I am learning haskell so that I can add some good mouse keys myself.

[manna-harbour]

You can use the Miryoku KMonad makefile directly with any keymap, so you could use it to add conditional defsrc to your existing keymap. And as your keymap is 3x5+3, you could even recreate it with Miryoku Babel and apply it to the other Miryoku implementations, then you can use it on any supported keyboard and firmware.

I've only used the X11 mouse keys. I believe the other OSs use the same bindings, but I don't know if any support changing them. The functionality is a bit limited though, so one of the other mouse keys implementations might be better.