Feedback: LightTextInputEditor's embedded keyboard renders smaller/more cramped than the native system keyboard

[wildassoler]

While building a tool that needed text input, I noticed LightTextInputEditor
(and its embedded light-keyboard rendering) looks visibly smaller and more
cramped than the real system keyboard used by native LightOS apps (e.g. the
"Search Contacts" screen) — smaller keys, lowercase-by-default labels, and
noticeable side margins that the native keyboard doesn't have.

I traced it as far as I could on my end: LightEmbeddedLp3Keyboard.kt (in
sdk/ui) doesn't add any side padding of its own, so the difference seems to
come from inside the compiled light-keyboard artifact itself, which I don't
have source access to.

Not sure if this is intentional (e.g. deliberately keeping tools on a
Light-controlled keyboard rather than depending on whatever IME is
installed) or just an unpolished corner. Worked around it for now by using
a plain Compose BasicTextField instead, which does trigger the real system
IME — but figured this visual gap was worth flagging either way.

[dupontgu]

A few things!

1. You do have source access to the keyboard 😄 https://github.com/lightphone/light-keyboard
2. As of Add optional initial capitalization to text input #141 you can pass in a parameter to make the keyboard default to uppercase when it loads
3. Can you send screenshots of what you're seeing? I took a screen shot of LightOS and our UI demo text screen and overlayed them. They're off by a pixel or two on my LP3 but I don't think that's what you mean by "noticeable":

[dupontgu]

ACTUALLY - one thing that might be causing this is the fact that we're now pulling builds from jitpack instead of ones that I published on Github Actions. The ones I published were built on my machine with the font files available locally. Jitpack doesn't have access to those! Will look into that.

[wildassoler]

That would explain it! Attaching two screenshots from my LP3 for
comparison: the first is my tool's screen using LightTextInputEditor
(pulled via jitpack), the second is the native "Search Contacts" screen.
The letters in the first one are noticeably smaller/lighter than the
native one — consistent with a font fallback rather than just a pixel
or two off.

Good to know about the source repo and the uppercase param too, thanks!
For now I worked around it by using a plain Compose BasicTextField
instead of LightTextInputEditor (triggers the real system IME), so not
blocked — just flagging in case the font issue affects other things
built on jitpack too.

[dupontgu]

hmmmm that still looks like akkurat though... Will keep digging. Do you have a commit pushed somewhere? Can try to repro locally later today.

[wildassoler]

Just added you as a collaborator on wildassoler/label-scanner-light —
should be in your invites now.

Relevant commit: def4cee
File: tool/src/main/kotlin/com/wildassoler/scorelight/ManualEntryScreen.kt

That's the version still using LightTextInputEditor (before I switched
to a plain BasicTextField as a workaround). Should reproduce the same
"Scan Health" screen from the screenshots I posted earlier if you check
out that commit and build the tool module.

Let me know if you need anything else to repro