The Wavelink Keyboard Editor application is designed for creating custom keyboards that you can use on the Wavelink Terminal Emulation (TE) Client for Android and iOS devices. Keyboards created using this application can then be exported to devices and used in place of the default TE Client keyboards.
Custom keyboards are created, edited, and exported as part of a project. Before you can create and edit individual keyboards, you must first create a project in which to contain your keyboards. Custom keyboards and templates are created and their behaviors and presentations are controlled within a project.
Each keyboard consists of a template, or a layout of keys with predefined labels, values, positions, and sizes. Custom keyboards created from a template inherit all of the template's traits, including key layout and any preassigned key labels and values. Even after creating a custom keyboard, you can still edit the layout and size of keys through the Template Editor, as described in Editing Templates. In addition to editing the layout of keys on a keyboard, the color of each key and the font style of their labels are customizable through the Style Editor. For a list of all possible style options, see Using the Style Editor.
A project can contain multiple keyboards that you can edit and switch between. Through the Keyboard Editor application, you can assign multiple values to keys and associate them with states, such as a shifted or long press state. At the key level, alphanumeric characters or HEX codes are supported for special actions like function keys. At the keyboard level, orientation viewing modes, key styles, and templates are supported for increased control over keyboard use. For information on how to perform these actions, see Understanding the Console.
Keyboards are exported and imported as bundles, or groups of keyboards. When creating a bundle, the Keyboard Editor creates a .zip file containing the keyboards as an .xml file, along with all scripts, images, and other resources needed to use the keyboards. When importing keyboards to a project, you can either import a single local custom keyboard or a keyboard bundle created in another existing project.
Once a keyboard bundle is exported, the .zip file is deliverable to devices using the TE Client either by manually placing it on an Android device's hard drive, or by using a mobile device management (MDM) software like Wavelink Avalanche to deliver it to both iOS and Android devices. If your devices aren't managed by Avalanche, you can use the application to create QR codes to scan and download keyboard payloads. With devices managed by Avalanche, you can create hands-free payloads that will deliver directly to devices. For alternate MDMs other than Avalanche, you can use the Wavelink Configurator to create a configuration file that is then usable on another MDM software to deliver custom keyboards. For more information, see Distributing Keyboards.
Was this article useful?
The topic was:
Not what I expected