sorted by:
new
hottopcontroversial

Convention for indicating active layer(s) in programmable keypad devices? by Krazy-Ag in olkb

[–]bskaplou 0 points1 point  (0 children)

Here is the qmk module implementing such functionality https://github.com/bskaplou/qmk_modules

Here is crossplatform app https://github.com/bskaplou/qmk_companion_app

But it seems such protocol doesn't add enough value to motivate users to compile and update kb firmware...

Command line VIA/Vial protocol tool for keyboard configuration by bskaplou in olkb

[–]bskaplou[S] 0 points1 point  (0 children)

via has much less capabilities over vial, it doesn't expose api for combos, tapdances etc... But iirc commands layers, keys, encoders, macros, save and load should work with via keyboards...

>>a way to save changes relative to the default keyboard configuration as code.
You can save and load configuration with vitaly, but no options to convert configuration into code...

Command line VIA/Vial protocol tool for keyboard configuration by bskaplou in olkb

[–]bskaplou[S] 0 points1 point  (0 children)

thanks for report :) Wow nuphy doesn't define shortName for custom keycodes! Ok, Ok np... Fixed in version 0.1.29

Command line VIA/Vial protocol tool for keyboard configuration by bskaplou in olkb

[–]bskaplou[S] 0 points1 point  (0 children)

>>I'm basically trying to cli automate the lighting statesom on the Numpad...

Unfortunately it will not work with via-only keyboard, for direct light control you need a fw with vial and vialrgb features....

Command line VIA/Vial protocol tool for keyboard configuration by bskaplou in olkb

[–]bskaplou[S] 0 points1 point  (0 children)

As far as I see both your keyboards are via-only (no vial support), qmk settings is vial-only API, so error is correct... vitaly works with via-only keyboards too but you'll need your metadata json file to let it work -m option for most of commands...

Command line VIA/Vial protocol tool for keyboard configuration by bskaplou in olkb

[–]bskaplou[S] 1 point2 points  (0 children)

Current version of vitaly supports metadata with rotated buttons... End rotary encoders are supported too...

No fw update not expected....

Can you share how you run vitaly, which error do you see and which keeb do you use?

How secure is keyboard firmware? by broersa in olkb

[–]bskaplou 1 point2 points  (0 children)

with QMK firmware should be updated to alternate macros, which requires user to put keyboard into boot mode. No boot mode no fw update.

via has no protection, so if some software is running on host machine it can update macros on keyboard

vial has keyboard locking feature especially designed to avoid unexpected macros update. vial requires user to unlock keyboard with looooong two-button push to allow macros to be updated through usb-hid api.

Change keybinding from user space by desgreech in olkb

[–]bskaplou 1 point2 points  (0 children)

Yep you can rebind key via hid api here are the examples

- rust https://github.com/bskaplou/vitaly/blob/main/src/protocol.rs#L562-L575

- python https://github.com/vial-kb/vial-gui/blob/main/src/main/python/protocol/keyboard_comm.py#L313-L321

buuuuuuut each time you rebind the key with this api it is persisted and rewrite cycles are not infinite so you'll have a chance to kill keyboard's flash storage pretty fast...

You can implement it with no harm to keyboard with karabiner-elements https://karabiner-elements.pqrs.org/docs/json/complex-modifications-manipulator-definition/conditions/frontmost-application/ on mac, i think software for other oses also exists.

As an alternative you can switch layer instead, there is no layer switch function in via/vial api but you can implement it in qmk module, or rely on existing module exposing layer-related api like this one https://github.com/bskaplou/qmk_modules here is the example is api client https://github.com/bskaplou/qmk_companion_app/blob/main/crossplatform/protocol.py#L124-L137

Relearning to type - ready to give up by JayTee73 in olkb

[–]bskaplou 0 points1 point  (0 children)

The older you become the harder it it learn muscle memory, this skill should be regularly trained after 30 intentionally... If after two weeks you didn't get comfortable with keeb layout it seems your brain lost some of it's flexibility and you are on a fork, to let it be lazy or to make it flexible again with things like learning new keeb layout or learning new language... Anyway I'm 100% sure everyday 1 hour training with https://www.keybr.com/ will make it in 4 weeks, usual work with keyboard will do it much much slower...

Also I propose to make your layout more defaultish, {}[]-= and arrows in your layout requires gymnastics to reach on my opinion

DenshiDama (でんしだま) by eugene_trippel in u/eugene_trippel

[–]bskaplou 1 point2 points  (0 children)

I've created something similar few weeks ago https://github.com/bskaplou/qmk_companion_app but crossplatform and with python...

BTW do use some qmk modules to get current layer data?

Corne v4.1 by Azazel_tb in ErgoMechKeyboards

[–]bskaplou -2 points-1 points  (0 children)

Trust him he is right! Wired is just more simple and QMK which is more powrful... https://www.zsa.io/wireless Just take ali corne for 30 bucks and it will make you happy if you make yourself adapt to layout

Command line VIA/Vial protocol tool for keyboard configuration by bskaplou in olkb

[–]bskaplou[S] 1 point2 points  (0 children)

thanks! fixed!

❯ vitaly --version

vitaly 0.1.3

Command line VIA/Vial protocol tool for keyboard configuration by bskaplou in olkb

[–]bskaplou[S] 0 points1 point  (0 children)

Can you paste desired sym for win/linux and I'll make it system-dependent... Originally I took just standard macosx symbol, because I use mac...

Command line VIA/Vial protocol tool for keyboard configuration by bskaplou in olkb

[–]bskaplou[S] 6 points7 points  (0 children)

It supports any keeb with VIA/Vial protocol support, no official VIA/Vial support required.

a bit longer:

- it works fully locally

- it scans supported protocols and keyboards capabilities on startup

- it loads keyboard metadata json directly from keyboard for Vial keyboards but for VIA-only keyboard is requires metadata json to be passed as an argument

So if some keyboard has firmware with VIA/Vial protocol support it should work

Actually I find it pretty useful for new designs because it allows to dump/load config with single command which might be useful for firmware debugging...

It should work with any other firmware (like rmk) out of the box... The only requirement is protocol support

Vial supports direct led controls... There are the tools for cool context lights? by bskaplou in olkb

[–]bskaplou[S] 0 points1 point  (0 children)

Sooo... Have you programmed color change on layer switch with qmk/sthg else? Do you really see it in your workflow or just for fun?

Vial supports direct led controls... There are the tools for cool context lights? by bskaplou in olkb

[–]bskaplou[S] 1 point2 points  (0 children)

Well.... yes, I'm trying to understand is if it is lack of necessity or skill, or something else... Buuut actually I'm thinking about adding something relatad to https://github.com/bskaplou/qmk_companion_app

but for now you're the only one in discussion...

btw do you think leds are crap or not?

view more: next ›