feat: new sil_ipa gestures (first draft) #2521
Conversation
|
Note: this should not be merged until 17.0 is released. |
jahorton
force-pushed
the
feat/ipa_gestures
branch
from
ffc5f27 to
03e3e4a
Compare
|
No rush here; this is partly a fun thought experiment. That said, it may make a good keyboard to use as an example for flick-gesture use, and it would be nice to have a couple of early examples to point people toward when talking about the new gestures landing in Keyman 17.0. So yeah, I thought I'd try adding gesture support to the IPA keyboard - it seems like it could be a fantastic case for use of the new flick gesture type. Since there do seem to be just four "main modifiers" (
You two are far more "expert" in this field... and are listed as the original authors for the keyboard... so I feel I should leave the ball in your court on this. Feel free to reject this idea or to modify things to better suit what you believe would be most needed for end users. |
|
Noting that subscript numerals are getting added in #2587 . It might be nice on the numeric layer to also add those (convert superscript and subscript numerals to flicks?) |
|
Mostly I like it. The flicks on the uppercase layer are kind of irritating because when I was trying different flicks on SHIFT it kept reverting to the default layer rather than staying with SHIFT. Maybe I wasn't typing it correctly. I'm wondering about the keyboard automatically going to default anyway since this is IPA does it make sense to default back to the default layer? I know you didn't make that change and I cannot remember at what point we added that (It looks like it's been that way since I created the mobile layout. Since no one has complained maybe that's not an issue.) |
|
@jahorton is this a PR that's now ready to process or was it replaced with something else? |
Oh, uh... if you feel like the keystroke layout I went with is fine, I suppose it's ready to process. I was kind of expecting there to be a few layout change requests before proceeding further. |
|
I like this a lot. The flicks make sense and one could easily get used to it. There is the issue of diacritics being quite small and having no dotted circle, but I think Marc has said that that's work to be done outside of specific keyboards. |
|
@MattGyverLee do I understand that you, as a user, would be happy for us to merge this in to the keyboard? (Yes, the font issue is a separate issue. I have no idea when we can address that) |
|
Yes, of course, with some added documentation for the mobile version. Flicks are now in Keyman stable, right? The mobile version was usable before this, but I agree that this is 1) a step in the right direction toward usability, 2) it would be a great example to instruct future developers wanting to see a practical example of flicks, and 3) won't confuse the existing 70,000 users (I hope you have statistics for how many are on mobile) because this feature is below the surface. |
|
I just explored the shift issue Lorna mentioned. Flicks seem to work but Longpresses on the SHIFT layer look like they're sometimes only giving their lowercase equivalents. Oddly, Flick down on G gives ɢ for example, but it's not in the longpress on G. Maybe this is an isolated issue. I'm not sure if longpress on a capital letter should include lowercase variants since IPA is predominantly lowercase, but for people not using shift, I believe all lowercase and uppercase options should be in the lowercase longpress. Does that make sense? |
sil_euro_latin and khmer_angkor are two other keyboards with great flick usage.
Why? What would we do with those stats? |
|
I'm not sure if longpress on a capital letter should include lowercase
variants since IPA is predominantly lowercase, but for people not using
shift, I believe all lowercase and uppercase options should be in the
lowercase longpress. Does that make sense?
When I added a mobile layout I added the longpresses based on what the
modifier key+cased key was on desktop. It doesn't make sense for me to have
done that for mobile. I could probably add all those to long press on the
lowercase keys. I'm not sure if I should remove them or not from the
uppercase. Marc has started making us aware we don't want a regression in
keyboard behavior, just enhancements. But, since no one intuitively knows
where they are, it's probably fine for me to move them AND document the
mobile layout at the same time. That's a longstanding issue I've been
ignoring.
…On Wed, Mar 19, 2025, 7:54 PM Marc Durdin ***@***.***> wrote:
2. it would be a great example to instruct future developers wanting
to see a practical example of flicks
sil_euro_latin and khmer_angkor are two other keyboards with great flick
usage.
3. (I hope you have statistics for how many are on mobile)
Why? What would we do with those stats?
—
Reply to this email directly, view it on GitHub
<#2521 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV6RI2CU3BRPRW3OTLYQVD2VIGUFAVCNFSM6AAAAABZJTACQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZYG4YDCMBYGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: mcdurdin]*mcdurdin* left a comment (keymanapp/keyboards#2521)
<#2521 (comment)>
2. it would be a great example to instruct future developers wanting
to see a practical example of flicks
sil_euro_latin and khmer_angkor are two other keyboards with great flick
usage.
3. (I hope you have statistics for how many are on mobile)
Why? What would we do with those stats?
—
Reply to this email directly, view it on GitHub
<#2521 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV6RI2CU3BRPRW3OTLYQVD2VIGUFAVCNFSM6AAAAABZJTACQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZYG4YDCMBYGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
A public link for anyone wanting to try out this draft: https://jahorton.github.io/sil_ipa.kmp
General rules of thumb:
<key>+<=> left flick (includes shifted versions)<key>+>=> right flick (includes shifted versions)<key>+==> down flick (includes shifted versions)the superscript version of a default-layer key: up flick
qs variants are based on?instead, supporting glottal stops and similar characters.Qas per the standard pattern, though.!-based clicks: accessible as flicks on SHIFT+P following the patterns set above, with!as up flick.p+=flick is still rooted on the default layerpper the rules above.the velarized/darkened version of a consonant: shift layer's up flick (if not otherwise defined)
if a
|variant for a key exists and the shifted key's up-flick is still otherwise undefined, I used that instead of leaving the spot empty.adds hints for some less-obvious subkeys (such as glottal stops being on the q)
The 'clicks' are all available from
p(down) and shift+p(with hardware-keyboard's!base as shift+pup-flick).The glottal-stop variants are all available from
qand shift+q.Aside from that, the patterns involved should be quite consistent, though there is some regrettable conflict between velarization and a few of the super-script variants.