Open msafi opened 3 months ago
Hello, @msafi !
Very interesting suggestion
Once concern I have is collisions between f
and fe
/ s
and se
, which might cause a human error. Can we maybe change specification to fo
/fi
and si
/se
or distinguish them in a more reliable way?
I like the idea, but I need some time to think on the implementation.
@everyonesdesign yeah, your modification makes sense to me
Another suggestion for brainstorming purposes...
Use the following translation between numbers and letters...
1 => q 2 => w 3 => e Etc...
This one also comes somewhat natural to the touch typist since our muscle memory is used to looking for the numbers up there...so maybe it can be learned quickly...
I get that, I also touch type and I can see why these improvements can be useful.
I need to think about the implementation and possible collisions with other move inputs, to make sure it's backward compatible. I'll get back to you on that.
In the meantime feel free to add details to this thread if you have other ideas, I appreciate that!
Hi, I use algebraic notation to make the moves, so
Nb2
. However, typing the number2
(or any other number) is not fun because I have to remove my hands from the home row while touch typing.So in this post I want to propose a more fun way for the touch typist to use this extension: use letters instead of numbers in algebraic notation.
Here's the mapping
1
=>o
2
=>t
3
=>th
4
=>f
5
=>fi
6
=>s
7
=>se
8
=>e
So now instead of typing
Nb2
, I can typeNbt
to achieve the same thing. For touch typing,Nbt
is a lot easier thanNb2
.I would also recommend making the notations more human error tolerant, so
Nbtw
andNbtwo
should also translate toNb2
.Happy to pay a bounty towards this feature. Thanks!