You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any work in this area needs to be discussed with QMK Collaborators first, and in this case primarily with @skullydazed due to their prior work in this area.
The info.json format needs to be modified such that rather than specifying multiple fully defined LAYOUTs, a single layout can be specified with "layout options" that are capable of removing and adding keys depending on the selection.
This enables a much smaller method of defining such layout combinations -- if a keyboard supported:
2U backspace or split backspace
ANSI or ISO Enter
6U, 6.25U, 7U, or Tsangan bottom row
Then under the current format the info.json would need to define 2x2x4=16 layouts. A "base" with "options" would significantly decrease the amount of definitions required, as well as significantly lower the size of the embedded info.json blob for XAP.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.
stalebot
added
the
stale
Issues or pull requests that have become inactive without resolution.
label
Apr 16, 2022
XAP Task Info
Original Issue
Original spec document
Current XAP Definitions
Current XAP Generated Docs
Placeholder PR
Description
Any work in this area needs to be discussed with QMK Collaborators first, and in this case primarily with @skullydazed due to their prior work in this area.
The
info.json
format needs to be modified such that rather than specifying multiple fully definedLAYOUT
s, a single layout can be specified with "layout options" that are capable of removing and adding keys depending on the selection.This enables a much smaller method of defining such layout combinations -- if a keyboard supported:
Then under the current format the
info.json
would need to define2x2x4=16
layouts. A "base" with "options" would significantly decrease the amount of definitions required, as well as significantly lower the size of the embeddedinfo.json
blob for XAP.The text was updated successfully, but these errors were encountered: