The uninstall actions never ran because the working directory given was
invalid. Also fixed: the success/failure message is presented by the
caller rather than down in the depths of the call.
Relates to #5992 (part 1 of 2 - part 2 updates the kmn min version in
the compiler).
Updates package fileVersion property to be minimum keyboard version, to
avoid issues with app crashing if functionality is not supported.
As far as I can tell, only Keyman for Windows currently checks the
package fileVersion.
This could be quite nasty, except that the online keyboard repository
build process also extracts the min Keyman version from the keyboard
.kmx and .js, and records it in the .keyboard_info, preventing older
versions of Keyman from seeing unsupported keyboards in the cloud
repository.
Thus, the only gap is for peer distributed keyboards. So we should fix
this gap but it is less urgent than it might otherwise be.
As of Keyman Developer 15, we no longer need to install
keymanengine.msm, so it should be able to co-exist with any version of
Keyman for Windows. Remove the .msm to make this so!
1. Renamed form UfrmNGrokOptions to UfrmServerOptions
2. Renamed kmdev-server to just plain server
3. Tidied up npm versioning to use VERSION_WITH_TAG
This last point should help avoid confusion as now only CI release
builds will ever generate a package.json with a.b.c, a.b.c-alpha or
a.b.c-beta. Local and test builds will always have the corresponding
-test or -local environment appended. This also helps avoid issues if
we accidentally publish an incorrect version.
Relates to https://github.com/npm/cli/issues/2921
This issue arises after moving from npm 6.x to 7.x or later. As the
build agents are still on 6.x, we have not yet seen this issue there.
As part of the release build for Keyman Developer, we bundle up some
files and do some work in a temp folder to prepare folders for release.
Even though we are only working with `dependencies` (e.g. using `npm
install --production`), packages under `devDependencies` are still
wrongly being checked by NPM. As we have two modules present in
`devDependencies` that are only available when in the repo path, we need
to remove them before attempting to continue. Yuck!
ref: https://github.com/npm/cli/issues/3975#issuecomment-985305678
ref: https://github.com/npm/cli/issues/2921
Initial commit for Keyman Developer Server, running on Node.
Supports web debugger only at this point.
Extensive rewrite of web debugger, much of it more modern standards,
significantly improved UX:
1. Drop keyboards, packages, fonts, models onto debug page to load them
2. Websocket for instant reload of recompiled keyboards, packages,
models.
3. API for interacting with debug server.
4. Cache of recently used items.
5. Integration with ngrok for public access as desired.
6. Tray icon (currently default icon) for control of server.
7. Server can live after TIKE closes, supports multiple TIKE instances.
8. UI of debug host page rewritten with Bootstrap.
9. Packages downloads integrated into main page, and download link for
Keyman supports all platforms (Linux is just a link to
instructions...)
10. Avoids file locking and contention by managing all files internally.
11. Not yet tested, but should run cross-platform.
Adds ngrok configuration dialog and processes for downloading, updating
and setting up ngrok.
It is likely this will change with a refactor of the web debugger into a
standalone node module in the future. This will add support for multi-
instance Keyman Developer and be another step towards a cross-platform
IDE.
This commit adds x64 build for the imsample.dll.
It also fixes the a invalid memory access error that
occured when UnloadRules was called when a Keyboard
had been created but the rules not yet loadeded.
KeymanIMReloadConfig function returned a invalid
code excution point this was fixed by addeding it
to the imsample.def
Initial integration of ngrok into Keyman Developer web debugger
experience, so that the user can access their web debug session from
another device without significant configuration. By default, ngrok is
switched off, but when it is enabled and configured (user must register
an email address online I think), then Keyman Developer will start an
ngrok tunnel in the background and make it the default link in the list
of available addresses.
This also adds an option to hide the list of local addresses, which is
probably clearer for users when ngrok is active. However, as local
addresses will be faster if configured, it may be less sensible to do
this.
If the user has ngrok installed and in use already, then it is
recommended that they simply open a tunnel via the ngrok interface for
the debugger web host, rather than relying on Keyman Developer's
internal integration, as Keyman Deveoper does not do handle multiple
ngrok sessions.
The user may choose to make the ngrok tunnel window visible, which will
be helpful in error scenarios.
If Keyman Developer crashes, the ngrok tunnel may be left running, and
will need to be manually killed.
