Jesse Vincent

It should be possible to assign "win-tab" or "alt-tab" to a key in Kaleidoscope or Chrysalis without a custom macro

2

This is a little bit complicated because the behavior we need is "hold down the modifier, tap tab, release the modifier" And to make it really fluid, we likely want...

Lift LEDControl to the plugins directory

4

LEDControl, originally a plugin, has gotten its hooks into the Kaleidoscope core. We should lift it back to the plugins directory, now that that's a thing agian.

The glossary file needs to include all the concepts inside Kaleidoscope and their names. It may be sensible to start off by describing all the things and listing the names...

Duplicating KALEIDOSCOPE_INIT_PLUGINS in a sketch leads to indecipherable errors

1

Which confuse users.

this will save about a second of runtime if the image is already current and let us run the build verbosely to make it clearer what's going on

We need a Kaleidoscope plugin that flashes the avr keyscanner firmwares when triggered.

7

Right now, updating the avr keyscanner firmware requires flashing a custom tool onto the Model 01. That tool is small enough to become a Kaleidoscope plugin we could ship as...

Move a UI pattern making a Submit button into a "full width" item into /Elements/Submit

4

This moves a bunch of style markup into a common location and should not result in noticeable rendering changes.

Color-picker UI needs cleanup

1

The color picker should have only the palette squares, ideally laid out in a more symmetrical configuration (2 rows of 8, maybe). There should be a separate button to open...

There should be a heading above the per-layer settings that reads something like "Layer NAME Key #N", to make it clear that the settings below apply to a specific key...

The layer summary for the selected key should have its second column read something like "Key code/action" instead of "Key #N". There could be a heading that reads something like...