Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Break changes with the v0.8 (brackets) #101

Closed
antoinentl opened this issue Jan 24, 2023 · 6 comments · Fixed by #105
Closed

Break changes with the v0.8 (brackets) #101

antoinentl opened this issue Jan 24, 2023 · 6 comments · Fixed by #105

Comments

@antoinentl
Copy link

I try the 0.8 version, and I discovered a change for typing the brackets []{}:

  • v0.6:

Capture d’écran du 2023-01-24 15-54-24

  • v0.8 (or v0.8.1):

Capture d’écran du 2023-01-24 15-54-15

For me it's something like a break changes.
Is it an intentional change? If so, is it possible to keep the old way for the brackets?

@fabi1cazenave
Copy link
Owner

fabi1cazenave commented Jan 24, 2023

It is an intentional change, yes.

TL;DR: do you really prefer getting these brackets with a dead key rather than with AltGr+ASDF ?

Now the long story…

In the very early days, one of the project goals was to make the AltGr key optional. So there’s always been a way to get those brackets {[]} and <> signs without AltGr, even on an ANSI keyboard. I think getting <> on dead key + ZX was okay-ish, but to me, these brackets on a same-pinky combo has always seemed the most unnatural thing ever.

Lafayette’s main goal is to bring a better QWERTY. Having {[]} on the home row (with AltGr+ASDF) is a big part of it; and the whole AltGr layer is designed to make things like ->, =>, </, />, (0), [1], ("") as fluid as possible… and I thought, maybe some users have missed that because there was another way to get those brackets — which would be a sign of bad design (poor self-discoverability).

So with 0.8, I’m proposing to split the project in two parts:

  • the classic Lafayette layout, requiring 3 dead keys and an AltGr key;
  • the Lafayette42 variant, requiring a single dead key and featuring an even better but really optional AltGr layer.

If neither layout suits your needs, I’d be interested in reading your feedback.

@fabi1cazenave fabi1cazenave pinned this issue Jan 24, 2023
@fabi1cazenave
Copy link
Owner

Pinning this issue, hoping to see as many replies as possible on this.

@fabi1cazenave
Copy link
Owner

@antoinentl your feedback would be interesting here. ;-)

  • Do you really prefer getting these brackets with a dead key rather than with AltGr+ASDF ?
  • If this is the case, isn’t the Lafayette42 variant best suited for you than Lafayette v0.6 ?

I’m not against keeping the old behavior per se, but I’d like to make sure I understand the use case.

@fabi1cazenave
Copy link
Owner

Thinking out loud, would this be a better default view to introduce Qwerty-Lafayette ?

image

@antoinentl
Copy link
Author

@fabi1cazenave Thanks a lot for the explanation and the historic description, very interesting and useful! The clarification help me to understand the original goals and my misunderstood of the tool. I think I was not using QWERTY Lafayette at its full power, and your explanation made me understand it. I will learn to type AltGr+ASDF, it's more concise 🚀 + ⌨️ Go ahead with the v0.8, and the Lafayette42 variant is a possible alternative if that new version doesn't suite with my needs. (And if I want I can always go back to the v0.6.)

By the way the default view just above seems better!

You can close that issue when you want.

@fabi1cazenave
Copy link
Owner

Thanks for your contribution, that’s really appreciated. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants