Fixes#6320.
Part 1 of moving from lerna to a simpler, maintained monorepo solution,
using TypeScript Projects and NPM Workspaces.
There is more work to be done here. At this point, KeymanWeb builds and
runs without errors, but the built file is substantially different,
mostly in include order.
Using TypeScript Projects, we move away from the need to run build
scripts in various locations for almost all the Typescript modules.
TODO: Embedded versions and tests have not been verified.
TODO: developer/server is not yet verified.
TODO: developer/js (needs a rename!) is not yet verified.
TODO: Currently, the predictive-text folder needs refactoring to move
the construction of the worker wrapper out of the Predictive Text build
and into the final assembly of keymanweb.js (as it should be valid to
run it as a separate .js anyway).
TODO: Most of the `<reference>` paths need to be re-verified. Ideally
there should be no references outside the current module for any given
.ts.
TODO: The embedded vs browser vs node (headless) builds should be tidied
up for consistency so that it's obvious what depends on what. This is
currently messiest in the predictive-text folder, where the output names
diverge from the filenames and the various files are mixed in the same
folder (as evidenced by the exclusions listed in each tsconfig.json).
TODO: `npm install` should be removed from most build scripts and
instead `npm ci` (#6196) should be run only once from the top-level
folder for any given build. I've had eliminated side-effects from the
`install` action for npm, which makes it easier to reason about state.
TODO: verify_npm_setup and related functions can probably be eliminated.
TODO: most of the build scripts should be largely eliminated for web.
TODO: several ts projects use inconsistent output folders.
TODO: it may be possible to generate a .d.ts for models/types so that
we can use a consistent reference for those as well.
TODO: build.sh, tsconfig.json should always be in the module's top-level
folder, not in a subfolder such as src (e.g. see input-processor/src,
keyboard-processor/src, web/source).
TODO: resources/web-environment should be in common/web.
TODO: other js node_modules imports should be wrapped like es6-shim.
TODO: fix up the publish code for npm modules
TODO: eliminate version numbers from package.json if possible?
Whew, that's most of the stuff I noticed!
Fixes#5353.
I made the promise usage consistent in the relevant addKeyboards
functions, instead of mixing promise and async/await style code, which
made it easier to spot the place(s) where promises had not been returned
as we needed.
Relates to #949.
* Adds optional `displayName` property to keyboard stubs: if present,
this will override the name on the spacebar.
* Adds optional `spacebarText` member to `keyman.options`. This defaults
to `SpacebarText.LANGUAGE_KEYBOARD`, and can be one of:
```
SpacebarText.LANGUAGE
SpacebarText.KEYBOARD
SpacebarText.LANGUAGE_KEYBOARD
SpacebarText.BLANK
```
* Sets the display pattern for LANGUAGE_KEYBOARD to be
"language - keyboard" instead of "language (keyboard)", which
reduces the number of parentheses visible on the spacebar.
There are a number of changes here to improve the performance of
KeymanWeb and the toolbar and reduce unnecessary requests:
1. (kmwbase.ts and kmwkeyboards.ts) Added option `setActiveOnRegister`,
default `'true'`; if set to `'false'` then will never attempt to
activate the first registered keyboard. Note that this property is a
string because the `options` object currently supports only string
types, which is not ideal, but out of scope for this PR.
2. (kmwuitoolbar.ts) fixed issue with toolbar not matching correctly on
full BCP 47 code (line 960) after keyboard change notification.
3. (kmwuitoolbar.ts) fixed issue with toolbar not showing active
keyboard if the keyboard is activated before init is complete
(see `ui.lastSelectedKeyboard` references).
4. (kmwuitoolbar.ts) avoided re-entrancy for `ui.changeKeyboardEvent`
by ensuring that `ui.selectKeyboard` does not attempt to set the
active keyboard again for keymanweb; note that this was being caught
by the event dispatcher in keymanweb but it was still not ideal.
5. (kmwuitoolbar.ts) with above changes, able to remove appalling two
second timeout on load (yay!)
These changes will be useful immediately with keymanweb.com.
