Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[XAP Prereq] info.json layout options #15599

Open
tzarc opened this issue Dec 27, 2021 · 2 comments
Open

[XAP Prereq] info.json layout options #15599

tzarc opened this issue Dec 27, 2021 · 2 comments

Comments

@tzarc
Copy link
Member

tzarc commented Dec 27, 2021

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 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.

@tzarc tzarc added enhancement help wanted xap XAP-related issues/PRs labels Dec 27, 2021
@stale
Copy link

stale bot commented Apr 16, 2022

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.

@stale stale bot added the stale Issues or pull requests that have become inactive without resolution. label Apr 16, 2022
@stale stale bot removed the stale Issues or pull requests that have become inactive without resolution. label Apr 16, 2022
@tzarc
Copy link
Member Author

tzarc commented Jun 18, 2022

Should also take into account whether or not certain layouts "swap out" keys for encoders, and handle those cases as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To do
Development

No branches or pull requests

1 participant