Custom preonic layout optimised for programming

[AlexDaigre]

Layout Images

Don Gato's programming Layout

The default Preonic layout is suited to general english typing but not very convent to program on. This is my custom layout to re-optimise the keyboard for programming tasks.
I have been programming with this keyboard layout at work and I found it much faster and easier to adjust to than the default layout.

• Removed keys on the RAISE, LOWER, and ADJUST layers that duplicated keys on the main QWERTY layout.
• Moved the control, alt, and gui keys to a more natural position.
• Added the Caps-lock key on RAISE and LOWER in its position on a standard keyboard.
• Moved {}[], -_, and | (on RAISE and LOWER) to be close to to similar keys on the QWERTY layout to make them easier to remember. They are kept as close as possible to their locations on a standard layout so users won't have to ADJUST their muscle memory much.
  • (), {}, and [] are all on the 9 and 0 keys. This is where () are placed naturally, so it is easy to find all of your braces.
  • -_ are moved to the += key. Now you can remember that -, +, and = are all together. The keys are also right next to each-other on a standard layout, so it is a very small move.
  • \ and | have beeb moved to the /? key. Easy to remember as / and \ are together.
• Moved backspace to make room for +=.
• Added delete to the backspace key on RAISE / LOWER
• Removed backlight and added an ADJUST key. As the Massdrop kits don't come with backlighting default, I think this is more useful for most users.
• I have left the Colemak and Dvorak alternate layouts, but they won't map up as conveniently to the other layers.
• I have included the keyboard layouts so that those wishing to make modifications or new versions of this layout can quickly update their images.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[drashna]

The only issue I see here, is that we generally prefer to have the keymap folder name match the github user account name. This isn't a hard requirement, but heavily preferred.

Otherwise, looks great!

[stale]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[noroadsleft]

The only issue I see here, is that we generally prefer to have the keymap folder name match the github user account name. This isn't a hard requirement, but heavily preferred.

I too would prefer if the keymap name matched the GitHub username, but otherwise this looks good.

@AlexDaigre please advise if you'd like this merged as-is, or update the PR and I'll merge it after that happens.

[AlexDaigre]

@noroadsleft Thank you for the feedback. I have updated the keymap name. Let me know if there are any other issues.

[noroadsleft]

@AlexDaigre Looks good. Sorry for the late response.