-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
chore(core): remove km_core_keyboard_load
API
#12769
chore(core): remove km_core_keyboard_load
API
#12769
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll have to let the FCITX guys know that they will have to change their code for v18
@@ -40,16 +40,18 @@ namespace | |||
} // namespace | |||
|
|||
km_core_status | |||
keyboard_load_from_blob_internal( | |||
km_core_keyboard_load_from_blob( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, removing keyboard_load_from_blob_internal
means that we'll have to initialize a std::vector
twice when called from WASM. Don't know how much overhead that has.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well— could retain keyboard_load_from_blob_internal
passing in the vector?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, we don't have the load from blob code in epic/web-core, is that right? Happy for a refactor back if that makes sense, but as it isn't landing in 18.0, I thought we could cleanup the source here at this point, given the km_core_keyboard_load_from_blob was literally a wrap-in-vector and call internal two liner.
|
Test ResultsI tested this issue with the attached Keyman 18.0.152-alpha-local build in the Windows, Ubuntu, KeymanDeveloper, and macOS environments. Here is my observation.
It works well.
It works well.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good once @ermshiperete comments are accepted!
@@ -40,16 +40,18 @@ namespace | |||
} // namespace | |||
|
|||
km_core_status | |||
keyboard_load_from_blob_internal( | |||
km_core_keyboard_load_from_blob( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well— could retain keyboard_load_from_blob_internal
passing in the vector?
@dinakaranr, did you install keyman or keyman developer for this test? |
@ermshiperete ready for re-review |
Changes in this pull request will be available for download in Keyman version 18.0.154-alpha |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
even though already mereged :)
Fixes: #12497
User Testing
TEST_WINDOWS: With Keyman for Windows, Test any Keyman keyboard, that it loads successfully and can be used in apps.
TEST_MAC: With Keyman for macOS, Test any Keyman keyboard, that it loads successfully and can be used in apps.
TEST_LINUX: With Keyman for Linux, Test any Keyman keyboard, that it loads successfully and can be used in apps.
TEST_DEVELOPER: Load a keyboard .kmn file into the debugger, and verify that the keyboard can be used in the keyboard debugger.