Very nice. There some bugs when selecting keys, but this is very good and helpful!
["Esc",{x:1},"F1","F2","F3","F4",{x:0.5},"F5","F6","F7","F8",{x:0.5},"F9","F10","F11","F12",{x:0.5},"PrtSc","Scroll Lock","Pause\nBreak",{x:0.5},"","","",""],
[{y:0.5},"~\n`","!\n1","@\n2","#\n3","$\n4","%\n5","^\n6","&\n7","*\n8","(\n9",")\n0","_\n-","+\n=",{w:2},"Backspace",{x:0.5},"Insert","Home","PgUp",{x:0.5},"Num Lock","/","*","-"],
[{w:1.5},"Tab","Q","W","E","R","T","Y","U","I","O","P","{","}",{w:1.5},"|\n\\",{x:0.5},"Delete","End","PgDn",{x:0.5},"7\nHome","8\n↑","9\nPgUp",{h:2},"+"],
[{w:1.75},"Caps Lock","A","S","D","F","G","H","J","K","L",":\n;","\"\n'",{w:2.25},"Enter",{x:4},"4\n←","5","6\n→"],
[{w:2.25},"Shift","Z","X","C","V","B","N","M","<\n,",">\n.","?\n/",{w:2.75},"Shift",{x:1.5},"↑",{x:1.5},"1\nEnd","2\n↓","3\nPgDn",{h:2},"Enter"],
[{w:1.25},"Ctrl",{w:1.25},"Win",{w:1.25},"Alt",{w:6.25},"",{w:1.25},"Alt",{w:1.25},"Win",{w:1.25},"Menu",{w:1.25},"Ctrl",{x:0.5},"←","↓","→",{x:0.5,w:2},"0\nIns",".\nDel"]
Definitely make a way to save and suggest layouts.
Can we change the base color of the keyboard?
Also, check my signature for the ABS color chip scanning project, it's open to everyone who wants to use it. In addition to the web versions of the colors, maybe display the actual photos of the color chips on the screen?
The biggest thing I would love to see from a functional keyboard layout editor is a way to export a functioning firmware for teensy based projects. If this would be possible myself and I'm sure a lot of people here would love you forever. Another nice option on that front would be to have a basic layout of said firmware for a hardwired matrix just showing which keys are in the same columns.
Melvang
Edit: Although the firmware export function would take some of the "hack" out of Geekhack.
The biggest thing I would love to see from a functional keyboard layout editor is a way to export a functioning firmware for teensy based projects.
The biggest thing I would love to see from a functional keyboard layout editor is a way to export a functioning firmware for teensy based projects. If this would be possible myself and I'm sure a lot of people here would love you forever. Another nice option on that front would be to have a basic layout of said firmware for a hardwired matrix just showing which keys are in the same columns.
Melvang
Edit: Although the firmware export function would take some of the "hack" out of Geekhack.
It's not online, and it's not the newest, fanciest firmware but I found this to be very interesting
http://geekhack.org/index.php?topic=35322.0
Nothing to see here: http://www.keyboard-layout-editor.com/#/layouts/3318ba90120b061ffa159aec097c0165
Nothing to see here: http://www.keyboard-layout-editor.com/#/layouts/3318ba90120b061ffa159aec097c0165
So close to HHKB, why didn't you do the 1.5x and 1x mods on the bottom row?
* Switched to a new JSONL parser; generates better error messages, and doesn't
get hung up on strings with colons in them.
* Increased the number of font-sizes available; now 1-9. New sizes are more
linear (for DSA profile).
* Support a 3rd (middle) row of text on the keycaps, to support some layouts
(e.g., German) that have lots of different legends.
* Support both a primary & secondary font-size on the caps.
* Primary is used for the first label; secondary for everything else.
* HRs now rendered in key legends if used.
* Added tooltips for most of the editor fields.
* Added support for 'stepped' keycaps.
* Added a 'stepped caps-lock' to the 'Add Key' dropdown.
* Split the 'Load Preset' menu into two sections.
* The first section is for true "presets"---standard layouts without much
customization that serve as a base for the user.
* The second section is for "samples"; these are layouts with more extensive
changes, to serve as examples of what is possible in the editor.
* Added a couple more samples to the list.
* Fixed the usual smattering of bugs, and no doubt introduced a bunch more...
* Updated editor with new Signature Plastics color swatches.
* ABS colors updated; PBT colors added.
* Colors were sampled from actual plastic chips using an X-Rite ColorMunki,
and then converted to sRGB (D65) using the formulas on Bruce Lindbloom's
website.
* Colors are accurate is your monitor is calibrated to sRBG!
* More accurate (?) colors for the tops of the keycaps.
* Previously, the color you entered would be used directly on the top of
the cap, and then "darkened" for the sides.
* However, our colors were sampled from the "smooth" part of the chip.
* Since the sides of a cap are usually smooth, and the top of the cap is
usually matte (which tends to reflect more light, appearing brighter), it
made sense to switch things around.
* Now using the color verbatim on the *sides* of the cap, and using a
"lighter" color for the top of the cap.
* Computing the "lighter" color in LAB space (instead of RGB space).
* Tweaked the gradients for DSA/DCS, and updated the various samples and
default colors to work better with the new rendering.
* Added a little "indicator" to the palette to indicate which color is
being used for the keycap (and label).
* Also, printing the currently-selected color name beside the color-editor
fields.
* Added a button to swap the keycap and label colors; should make creating
some color schemes (e.g., CCnG) really easy.
* Sanitizing any HTML tags entered into key labels.
* I wasn't so much worried about my site since there's no server-side
component to attack, I don't use cookies, passwords, or personal-data for
anything, and XSS rules should prevent anything too egregious.
* But (in theory, at least) users could be given a link to a "malicious"
keyboard layout, and then maybe tricked into doing something bad.
* Adding "SPACE" to the profile field will now render spacebars with a
vertical gradient (so long as the profile is supported). e.g., the profile
string should read something like this: "DCS SPACE R1" (or similar).
* Stepped keycaps are a little more user-friendly.
* When first creating a stepped cap, I automatically modify the widths to
make it obvious what's going on.
* The secondary width/height fields are no longer force-synced for stepped
caps.
* Added a link to the GitHub issues page, so users can submit bug reports.
* Added a new sample: Televideo TS-800a
* Fixed the usual smattering of bugs, and no doubt introduced a bunch more...
* Added support for rotated key clusters.
* Each key has a rotation angle and center-of-rotation.
* Keys with the same angle/CoR are grouped together into a "custer" for the
purposes of sorting the keys, and in the serialized format; e.g.,
navigating to the next/previous key will go through all the keys in the
current cluster before moving on to the next cluster.
* Crosshairs-indicator displays in the editor to let you know where your
center-of-rotation is.
* Keyboard: Ctrl+Arrows to modify the center-of-rotation; PgUp/PgDn to
modify the rotation angle.
* __CAUTION:__ it's really easy to get confused, and end up with keys
outside the visible area; I recommend setting your center-of-rotation
_before_ rotating the keys. But you can always "undo" if you mess up.
* Added rendering rules for the SA keycap profile.
* Currently renders exactly like DSA.
* Fixed the rendering of profile-gradients on non-rectangular keys.
* Works perfectly on DCS profile.
* Works about as well as possible on DSA/SA. Doesn't look jarring, at least.
* Added a "center-stepped" key to the "Add Key" dropdown menu.
* Some performance improvements.
* Added a new preset: ErgoDox
* Added a new sample: Symbolics PN 364000
* Fixed the usual smattering of bugs, and no doubt introduced a bunch more...If you could somehow work in an option to spit out a ready made firmware to load into a teensy 2.0 that would be primo. Even without that this is some amazing work.
It's a wonderful too, I dig it. (Maker badge nomination, amirite?)
If this is by design, it seems to give misleading impression of what the keyboard will actually look like.I don’t think the point is to give an accurate picture of what a keycap will look like. Think of the results as just diagrams.
If this is by design, it seems to give misleading impression of what the keyboard will actually look like.I don’t think the point is to give an accurate picture of what a keycap will look like. Think of the results as just diagrams.
Adding a disclaimer about the colour is the easiest option to implement, though.
- Ability to copy/clone an existing layout or make it a personal preset
- Ability to copy/clone an existing layout or make it a personal preset
You can download the JSON of any layout, and import it again, to have your own variant. Not as easy as a clone button, but not too bad, either.
I'd be interested in collaborating on a standard for the JSON format, so that more tools can use the gist directly. I'm maintaining my own version of swill's legacy code (http://github.com/skullydazed/kb_builder) and I have my own tool for generating EAGLE scripts to aid PCB development (http://github.com/skullydazed/kalerator). I'm also working on a QMK configuration tool (https://github.com/skullydazed/qmk_configurator), but that project is still a WIP and on hold while I wrap a few other things up.
Shoot me an email at info@clueboard.co, or you can also find me on the keyboard community slack. Unfortunately I got too many PM's and couldn't keep track of them to make sure everyone got an answer. :/
OK, I missed that :-[ .
Maybe it would be better to preset the large (today minimum standard) ISO 105 keyboard.
Maximum 105? Not even 108 (plus Sleep Wake and Power)? And there are keyboards with media buttons.
...
OK. I do not quite understand the phrase "knock yourself out". Not even the explanation in the "urbandictionary".
I do not know if the "Add Key" feature helps me.
I do not want to rewrite an existing keyboard.
I may want to build an experimental "keyboard".
Not useable. Except with a magnet on your fingertip, or a magnet stylus. But that is not the intended purpose.
The theoretical purpose is controversial, and can lead to incitement and insult.
I had the idea on the basis of an article (rather scientific essay) by Professor dr. Eckhard Kruse (computer science with specialization in physics and doctorate in the field of robotics and image processing).
With an old keyboard (electronics only) and reed contacts.
For this I need a new keyboard layout for Windows.
And if possible also for Android (more mobile).
knock oneself out
To make a great effort, to apply oneself to the point of exhaustion. [do this a lot. Keep adding keys in your case]
This hyperbolic expression, alluding to knocking oneself unconscious with extreme effort...Tobias Claren
I thought you wanted more then 105 keys.
1. Start with the 105 key preset (from the menu)
2. Click the "Add Key" button 3 times. Now you have a 108 key keyboard.
"But it's not the layout I want" (I think I hear you say.)
3. Click on a single key, say the "Z". Use the up, down, left, right arrows on your keyboard to move the key image somewhere you want it.
4. Repeat for any other keys that are in the "wrong" place.
Done
:thumb:Code: [Select]knock oneself out
To make a great effort, to apply oneself to the point of exhaustion. [do this a lot. Keep adding keys in your case]
This hyperbolic expression, alluding to knocking oneself unconscious with extreme effort...
Hyperbole is the use of exaggeration for effect. I don't mean make yourself unconscious, I mean make as many keys or keyboards as you like.
Perhaps, i have to open my own topic...