me: I need to make a simple web-app for a projectalso me: I need to learn some react basics for a job interview
-
What obvious layout am I missing?
I updated it a bit.
(I should add ĄŽERTY just in case I ever flirt with any Lithuanian tranfems)
-
What obvious layout am I missing?
@foone Dvorak, but with the original number ordering
-
I updated it a bit.
(I should add ĄŽERTY just in case I ever flirt with any Lithuanian tranfems)
@foone I wonder if it’s possible to determine the layout from a single keypress of a specific key the app tells you to press (by position)
-
I updated it a bit.
(I should add ĄŽERTY just in case I ever flirt with any Lithuanian tranfems)
@foone I mean, I might argue that you should flirt with some Lithuanian transfems in order to use ĄŽERTY.
-
What obvious layout am I missing?
@foone what languages is this for?
i know neo exists for german but i have no idea how many people actually use it. i'd also consider swedish qwerty and american qwerty fairly different.
-
What obvious layout am I missing?
@foone@digipres.club ŜĜERTŬ, the Esperanto layout /jk
-
I updated it a bit.
(I should add ĄŽERTY just in case I ever flirt with any Lithuanian tranfems)
@foone are you focusing only on Latin script? Cos there’s JCUKEN (Russian layout) – https://en.wikipedia.org/wiki/JCUKEN
-
I updated it a bit.
(I should add ĄŽERTY just in case I ever flirt with any Lithuanian tranfems)
@foone
Swedish and other Nordic layouts (including Dvorak versions - "svorak" for Swedish). Turkish. I'm sure many others.How important is it for you to know the physical layout of the keyboard? Could you get away with a subset of keys? Let it be user configurable?
-
okay so my first attempt at writing any react code resulted in a hydration error and also my UI elements are rendered black on black, making them invisible
@foone, sounds ideal for a Disaster Area stunt ship.
-
I updated it a bit.
(I should add ĄŽERTY just in case I ever flirt with any Lithuanian tranfems)
I've accidentally put it next.js into an infinite loop
it's constantly trying to recompile the typescript -
okay so my first attempt at writing any react code resulted in a hydration error and also my UI elements are rendered black on black, making them invisible
@foone i don't know what a hydration error is and i never want to know from the sounds of this whole thread
-
@chrisjrn handedness is handled (no pun intended) at a different layer
-
I've accidentally put it next.js into an infinite loop
it's constantly trying to recompile the typescriptokay I think I'm gonna give up on getting autocomplete to work for now.
There's like half of a result on google for the error I'm getting
-
What obvious layout am I missing?
@foone Linotype?
-
@foone Linotype?
@AMS oh I've got one of those

-
okay I think I'm gonna give up on getting autocomplete to work for now.
There's like half of a result on google for the error I'm getting
or maybe I just need to clientside render the whole thing
-
What obvious layout am I missing?
@foone Canadian multilingual standard.
-
I updated it a bit.
(I should add ĄŽERTY just in case I ever flirt with any Lithuanian tranfems)
@foone only the most used transfem language
KEYSMASH
-
@foone only the most used transfem language
KEYSMASH
(that's what this is: an app for cataloging transfem keysmashes)
-
What obvious layout am I missing?
@foone obvious answer from me is "abcde"
Which is the annoying one that has the letters in order, as seen on some consumer devices aimed at non-tech-savvy folk