…Show Image(https://i.imgur.com/EJyRmUI.png)
…
…Show Image(https://i.imgur.com/EJyRmUI.png)
…
Mixing bash scripts syntax in the images with keycaps with drive letters (a drive mounting mechanism used by operating systems of old, and which only survives in Windows, and for not good reasons) strikes me as just plain wrong.
Unix FTW.
- DSA profile is out - It appears Signature Plastics can't/won't do reverse dye subbing or otherwise don't allow light legends on dark caps. KAT/KAM profile is probably the only way forward. My inclination is towards KAM for the intended aesthetic but KAT is proving more popular.
Mixing bash scripts syntax in the images with keycaps with drive letters (a drive mounting mechanism used by operating systems of old, and which only survives in Windows, and for not good reasons) strikes me as just plain wrong.
Unix FTW.
I can understand the reasoning for all the :\ _ symbols, but having them appear repeatedly on adjacent keys makes them look highly redundant, and makes the board look cluttered. Just the choice of colours should get the idea across effectively enough for those with sufficient experience.
Mixing bash scripts syntax in the images with keycaps with drive letters (a drive mounting mechanism used by operating systems of old, and which only survives in Windows, and for not good reasons) strikes me as just plain wrong.
Unix FTW.
My PDP-11 runs both RSX-11 (with _double_ drive letters), Unix v7 and 2.11 BSD. What now? :))
Hey folks, small update. Here is a possible alternate set for those who dislike the >:\cmd_ style keys, inspired by terminal highlighting:
Thoughts?
Hey folks, small update. Here is a possible alternate set for those who dislike the >:\cmd_ style keys, inspired by terminal highlighting:Show Image(https://i.imgur.com/FVJa6hh.png)Show Image(https://i.imgur.com/kHmfxVu.png)
Thoughts?
Hey folks, small update. Here is a possible alternate set for those who dislike the >:\cmd_ style keys, inspired by terminal highlighting:I wonder how a solid block of colour after the text in the style of a terminal caret/cursor would look instead? I love this concept but I'm really not keen on the lack of horizontal padding but as Pyk_ said you l they may become difficult to fit all some mods if you make them even wider.Show Image(https://i.imgur.com/FVJa6hh.png)Show Image(https://i.imgur.com/kHmfxVu.png)
Thoughts?
Very cool! Just a little inconsistent that only the mods get the text highlights? What about Del, Pg Up, Pg Dwn etc.
Woah, amazing! One question, does that keyboard in the renders actually exist? Looks really nice with the keyset...
set looks good hoping more kits for split backspace and iso users, Would like to see support for tsangan bottom.
is the kam going to be matte or glossy?
Awe man... I like the mint green way more. I wish that was the color way that you stuck with. :/
Is there a chance to offer different accent color options?
This is a great idea. I have been waiting for something like this for a while. I spend quite a bit of time in vscode and on the cli in linux so these keys would be right up my alley. As far as the colors I think you are on the right track... the old school phosphorous green screen theme is cool looking and fun, but it isn't easy on the eyes. These colors resemble a theme you would see in a modern text editor.
The font is looking good. The only thing that throws me is the legends on the modifiers a little. Probably just cause I changed mine long ago to a custom one. There are a lot of variants of command line prompt and indicators you might want to play with. This is of course because it can be so easily customized. I like how it is now but try playing around with it or looking at old terminal screenshots and you might find something you like more. I will put some off the top of my head below. The highlighted option looks nice as well. Good luck I hope this goes all the way I would definitely be in. Keep it up!
enter key examples:
[execute:~]$
[~]$:execute_
[~]:>execute_
[execute]:>_
[~]$:enter
** edit: you can tell I like brackets :)
How'd you manage to design a set that is exactly what my goddamn terminal emulator colorscheme is set up like? Are you a mindreader? I'll be buying.
Personally I like the set option here [1] and am not interested in the overly decorated modifiers (i.e. >:/alt_).
Curious about the thinking beind the overly decorated keys - I do a lot of scripting in bash and am a linux user - what is this syntax:
>:/execute_
Does that represent the prompt ">:" and then a file at location "/execute_" that you're executing?
[1] https://i.imgur.com/FVJa6hh.png
But it's basically prompt ">:" location "/" (but without an actual directory cos that would take up far too much space) command "execute" and cursor "_". It's a balance between accuracy, what looks good and what fits on the keys :)
But it's basically prompt ">:" location "/" (but without an actual directory cos that would take up far too much space) command "execute" and cursor "_". It's a balance between accuracy, what looks good and what fits on the keys :)
That's a valid compromise. The current implementation looks really strange to me, though, and I've been using Linux/Unix and other lesser-known operating systems for more than 30 years. Usually, the prompt after which you enter your command is clearly identified by a specific single character; the most common being >, $ and #. Optionally, is it preceded by information like the current working directory. MS-DOS had "C:\>" (the colon here is part of the disk drive name, not the prompt symbol), Linux/Unix has prompts like "[hostname] / >". That's why I'd recommend using the format "something > command_" simply for its recognition factor.
I really appreciate the desire to cater to multiple prompt users, but I think that may have just caused the symbols to be a bit abstract/nonsensical.
[~]# execute_
:/# execute_ (most similar to current execution - I do like the :/)
:~# execute_
[~]/>execute_ (geewhiz is this what you were suggesting?)
The su button should already be a special case without the # since it's a bit stupid to switch to root when are already root :P so it would be say :/$ su_
I'm unsure if any of the above are distro specific, something I'm keen to avoid as it'll just turn some people off because it's different from what they use.
I think they're all okay, just the colon seems superfluous. But hey, the symbol seems to have grown on you and you're the creator, so it's fully your call. :)
Also for the arrow/cursor keys, maybe consider a kit with h j k l instead of left/right/etc for the vim reference
Also for the arrow/cursor keys, maybe consider a kit with h j k l instead of left/right/etc for the vim referenceLove this idea, at the very least, some stylised hjkl keys as part of a novelty kit would be awesome
I think they're all okay, just the colon seems superfluous. But hey, the symbol seems to have grown on you and you're the creator, so it's fully your call. :)
So after some testing the clear winners are:
[~]/>execute
and
[~/]>execute
If I'm understanding correctly the 2nd option should be more accurate. Cos you're taking away the hostname and user for space reasons, but you're working in some unspecified directory below the home directory and then the prompt. Whereas in the first one the / is part of the prompt and doesn't really do anything?
These sadly don't fit on anything smaller than 1.5u but it's workable.
I don't recall ever seeing the '>' char in a prompt but as I said if you think it looks good that matters too.
> execute_
$ execute_
I don't recall ever seeing the '>' char in a prompt but as I said if you think it looks good that matters too.
Windows command prompt, power shell, almost every REPL for scripting languages (python, nodejs), prompts for various clients to server applications (mysql, for instance). All by default of course, you can change your prompt. I would say > is a pretty broad and agnostic choice so could be good, I'm personally partial to $ but if it were my call I think I'd still choose >. Honestly IMO everything but the last char is too busy and I actually think going with just:Code: [Select]> execute_
would look good and convey the idea that it's a command being executed at a prompt or if one wants to go more *nix-y then:
Code: [Select]$ execute_
The basic design is awesome, I would hope for something more interesting with the F1-F12 keys though since they stick out like sore thumbs. If not some kind of novelties, then staying with the aesthetic maybe just \\f1 \\f2 etc in same font style as the mods
Is it going to be ABS KAM (a la KAM Starry Night) or PBT KAM (a la KAM Wraith)?
Is it going to be ABS KAM (a la KAM Starry Night) or PBT KAM (a la KAM Wraith)?
There are mold pbt shiny (starry night and Little pilot) and mold matte (First set kam Wraith). Honestly, for this set i prefer mold pbt shiny
I think they're all okay, just the colon seems superfluous. But hey, the symbol seems to have grown on you and you're the creator, so it's fully your call. :)
So after some testing the clear winners are:
[~]/>execute
and
[~/]>execute
If I'm understanding correctly the 2nd option should be more accurate. Cos you're taking away the hostname and user for space reasons, but you're working in some unspecified directory below the home directory and then the prompt. Whereas in the first one the / is part of the prompt and doesn't really do anything?
These sadly don't fit on anything smaller than 1.5u but it's workable.