search

keymanapp / keyman

Keyman cross platform input methods system running on Android, iOS, Linux, macOS, Windows and mobile and desktop web
https://keyman.com/
Other
399 stars 112 forks source link

feat(oem/fv): Decouple FV releases from Keyman release cycles #11115

Open darcywong00 opened 7 months ago

darcywong00 commented 7 months ago

From Slack discussion where @hopsandhops noted the FV mobile apps weren't displaying the current FV keyboard versions (see #11102)

Currently, the following manual updates need to happen for the mobile apps to pick up keyboard updates:

Then a stable build of Keyman / FV needs to be released.

@mcdurdin suggested

I think it might be sensible to decouple the FV App release cycle from the Keyman App release cycle, longer term. This would allow the FV App to be rebuilt and released at any time, and we could update the engine in it to the latest Keyman Engine release at a time that was convenient to you as well.

Linking it in to the same repository made more sense when we were starting out, but now we have an established process for using a published version of the engine, so that tightly coupled dependency no longer really applies.

The FV team will also discuss internally how to proceed...

mcdurdin commented 7 months ago

Relates to #11114

darcywong00 commented 7 months ago

More thoughts from @mcdurdin about maintenance:

My thinking there is to try and convert that keyboards.csv into a more manageable format, and then only include the information that is not already in the .keyboard_info files --> we have version number etc there, I think it may only be region that is missing?

We need Region and language info for each keyboard

wonder about working with scriptoria to deploy play store + app store apps such as fv keyboards, and others. Probably not the Keyman apps themselves but that could make it easier for us to do other keyboard apps in the future

e.g. could do keyman browser as well in that route. Play store and app store add a lot of friction at present.

mcdurdin commented 5 months ago

Moving to A18S11 so we can review with FPCF first

darcywong00 commented 4 months ago

I had copied a minimal keyboards.csv to the keyboards repo (for maintaining) in keymanapp/keyboards#2755

It's still a performance hit on the mobile app startup having to parse kmp.json and merge in the regions from keyboards.csv.

I wonder if we can optimize later in the fv_all.kmp build step of handling the merge of region info. Maybe merge into a separate regions.json file (that contains keyboard ID, name, language ID, language name, version, region) the mobile apps can consume...