|Build-A-Board®: for Windows; The Next Generation of Onscreen Keyboards; Version 2.20 Release 5; User's Guide|
|Prev||Chapter 2. Getting Started||Next|
1. Does the My-T-Soft Keyboard work with all Windows Applications?
2. Does the My-T-Soft Keyboard for Linux work with GNOME, or KDE, or only certain distributions?
The run-time software for Linux is written at the XLib level, which means just about all newer Linux Distributions (and many older distros), running GNOME / KDE / or other similar Window Manager, will have no issues with the run-time My-T-Soft for Linux.
3. What is the difference between the builder and the run-time keyboards?
The builder is the development tool that allows you to customize layouts, and choose targets. For actual End-Users that just need to use the keyboard layout, only the run-time software (installed on the target system) is required. Your layout will be a .KBF file (KeyBoard File with a file extension of KBF), and if only one layout is used, the default KEYBOARD.KBF needs to be on the run-time target system. For multiple layouts, each layout's name needs to be available, along with the default opening layout (named KEYBOARD.KBF). Currently the Builder can only run within Windows, while the keyboards (as targets) can run in any supported platform, including Windows, Android, Linux, and Mac OS X.
4. Why would I need/want a platform license?
When working with the builder, layouts built and deployed may contain license information. The type of license contained in the layout (.KBF file) determines the operation on different platforms (e.g. Windows, Android, Linux, etc.). If there is no license (or a free license) in place when a layout is created/deployed, the run-time target software will need to be licensed to allow normal operation with that layout (.KBF). By obtaining and building layouts with a platform license, operation on specified platforms (e.g. Android) will be licensed and no additional steps/licensing is required for those specified licensed platforms. In other words, layouts built with a platform license can be deployed to any device on that platform and will run in a licensed fashion. For individuals with a few systems, a platform license may not be needed, but if you are building for your company to deploy on dozens or hundreds of devices, a platform license will be highly desirable.