IMG Home PageIMG ProductsProduct DownloadsOrdering InformationTechnical Support and Frequently Asked QuestionsDeveloper's Corner and UtilitiesAbout IMG
CustomersIMG ResellersMedia InformationIMG Events / Trade ShowsUseful LinksIMG Contact InformationIMG Information / Policies
Translate



IMG KnowledgeBase & Frequently Asked Questions

IMG Logo



Search FAQ's

Keyword Keyword Search Help
Category Type Product Version

QC2005120226
What is Build-A-Board?

Part of the My-T-Soft® family, Build-A-Board is a suite of utilities that provide tools to create and operate on-screen keyboards, panels, and buttons for creating user interfaces that provide optimal interaction while offering secure levels of operator / user input control. These enhancements allow touchscreen, hand-held, wearable, wireless, ruggedized, tablet and pen-based computer users to operate these systems without the need for a physical keyboard. This results in space saving; reduced hardware costs; quick & low-cost user-training; cleaner machine interfaces; better security; allows enhanced enabling of legacy equipment retrofits; and provides a realization of new & innovative approaches for computer users.

With Build-A-Board, keys, buttons, and panels can be customized as desired, whether to control access, or sized to permit accurate entry even with large gloved hands. Unlike high-level environments and single purpose applications, the native, system-level run-time program can interoperate across all applications. Beyond keyboards, the potential is endless: A complete user interface can be built as a front end to legacy terminal based operations, as an augmentative solution for a disabled individual, or as a custom touchscreen based controller, etc., etc.

Build-A-Board is the evolving culmination of years of experience working with the needs of system providers & their use of IMG's successful My-T-Soft® family of on-screen keyboards. Developed to meet the needs of manufacturers, integrators, developers, and end-users of touchscreen & pen-based systems, it is the Ultimate Tool for anyone with a need for virtual on-screen keyboards & keypads.


Original ID: QC225140
Category: CommonType: Question/Answer Product: Build-A-Board



QC2005120227
Do Build-A-Board layouts work with My-T-Soft® / My-T-Touch® / My-T-Pen®?

Yes. Build-A-Board kbf's (keyboard files) can be used in IMG's OnScreen, My-T-Mouse, My-T-Pen, My-T-Soft, and My-T-Touch products. If you don't have any of these, you can also create a run-time (lite) version of My-T-Soft from within Build-A-Board for Win CE thru thru Windows 7 (including Embedded) to use your layouts.


Original ID: QC225141
Category: CommonType: Question/Answer Product: Build-A-Board



QC2005120228
What is the difference between the Run-Time files and Build-A-Board? How does the licensing work?

The Run-Time files are used on the Target system, which is often different than the development system. For example, if you are developing several keyboard layouts for a Windows CE unit with a MIPS processor, your Run-Time files target would be Windows CE - MIPS. The Run-Time files are licensed separately from Build-A-Board (since they may be placed on 1 or 100 or 10,000 systems). The Build-A-Board Builder (development environment for the keyboard layouts) is the tool used to create, design, modify, and manage keyboard layout files & select different Run-Time targets based on your needs.

Typically a customer would need only 1 or 2 Build-A-Board licenses, since only the developer, integrator, or IT department would be customizing a board or boards. Once it comes to deployment, a license for each run-time system running the keyboard layouts is required.

With the release of the 2.20 version and support for Mac OS X and Linux, platform licenses are offered that address different deployment options based on locations, number of employees, and platforms needed. All of the platform license options do not have unit based licenses, as deployed run-times are already licensed and royalty-free. Refer to Build-A-Board Standard (Cat. #12402), Single-site (Cat. #12415), Multi-Site (Cat. #12416), Enterprise (Cat. #12417), and Global Enterprise (Cat. #12418). Contact IMG Sales for further details.

For small roll-outs, as an example, if you have 8 forklifts with panel mount touchscreen systems, and need numbers, tab, enter, and backspace, a large customized board might be ideal. In this case, the Build-A-Board Builder Tool + 10 Run-time Licenses, Catalog#: 12403 might be the best choice. If you are prototyping and testing, Build-A-Board Builder Tool, Catalog#: 12401 would be sufficient. If you already have licenses of IMG's My-T-Soft®, My-T-Pen®, or My-T-Touch® installed, and want a custom board, then Build-A-Board Builder Tool License, Catalog#: 12401 is all you need. Please note that there are different license options available based on customer needs, so if you can't find exactly what you want on the web site, please contact us.


Original ID: QC225142
Category: CommonType: Question/Answer Product: Build-A-Board



QC2005120229
What operating system do I need?

To operate Build-A-Board you need: Windows 7 / Vista / XP / 2000.
Run-Time Files will work on: Windows CE or Windows 95/98/Me/NT/2000/XP/Vista/7/8/8.1, Windows Server and Embedded versions. Mac OS X 10.4 and higher, and Linux 32-bit/64-bit. For other platforms, or if you have more specifics, please feel free to contact us.


Original ID: QC225143
Category: CommonType: Question/Answer Product: Build-A-Board



QC2005120230
What about Unix, Linux, or Mac OS X?

With the release of the 2.20 version, Mac OS X and Linux are now available. (Note: For Unix, pre-built run-times are not included, as these types of deployments tend to be customer specific - please contact IMG for further details)


Original ID: QC225144
Category: CommonType: Question/Answer Product: Build-A-Board



QC2010120647
I have Build-A-Board 2.10 license - What are my options with the 2.20 release?
Where is my free upgrade?

With the 2.20 release, there are new licensing options. For 2.10 customers, we will be providing a free upgrade to the builder itself, which can still make ANSI 2.10 layouts. We are waiting, however, for the Release 4 update before formally doing this upgrade (the license manager needs to be created for Linux and Mac OS X). If desired, we can provide the BAB220 serial # at this time, so you can license and work with the current Release 3. Please note that you will still have to license individual run-times. Please contact IMG Customer Service with this request.

The new license options are what we refer to as Platform licensing, and it is based on company size, not # of units. Once you have a Platform license for Windows, Linux, Mac OS X, etc. you will be able to produce licensed versions for the licensed platform that can be imaged or deployed without any run-time/per unit licensing. The Build-A-Board standard upgrade (for 1 platform) from a 2.10 license is US$995 - Catalog # 12406 - this can be ordered on-line (with your BAB210 serial #) with this link:

Upgrade to Build-A-Board 2.20 Standard Platform license

You can then select a platform (Windows/Linux/etc.) and then when you build Unicode 2.20 layouts, the license is automatically embedded in the built layouts, allowing you to deploy without any further license steps. Note that you cannot resell these licenses - these are for you/your company as the end-user. If you wish to distribute / resell licenses, you need an annual distribution license.

To summarize, and hopefully clarify the above, here is what will happen to 2.10 licensees:

1) Free Upgrade to Build-A-Board 2.20/builder - able to use upgraded builder tool, can still make ANSI 2.10 layouts, run-times still licensed separately - Option to license and run Unicode 2.20 layouts by licensing run-time versions
2) Or pay for Upgrade to Platform license (Cat #12406 for Standard - company less than 50 employees)
(There are additional options for site/multi-site/enterprise/global enterprise licenses - please contact IMG Customer Service)
3) for any distributor/reseller and annual distribution license is required.

Category: CommonType: Question/Answer Product: Build-A-BoardVersion: 2.20



QC2010120648
I'm new to IMG's Build-A-Board - what is the high-level / birds-eye view?
How do I implement a custom keyboard in my application [using Build-A-Board]?

You need the Build-A-Board Builder to create or modify layouts, change key properties/actions, and create/build the KBF (Data) file. For the Target (run-time) you need the My-T-Soft program (for the particular platform) on the run-time system. Drop in the KBF data (default KEYBOARD.KBF), and run the My-T-Soft program - the layout will be displayed to the user, and its operation will be defined by the layout properties / Key Actions (which, of course, are modifiable within Build-A-Board).

What is the Builder for?

The Build-A-Board Builder itself is just a front-end designer tool to allow you to drag & drop keys, resize, change properties, etc. It is a user-friendly front end to designing keyboard layouts. When you build, you are creating the single file KBF that can be dropped into a target system (which then contains the Keyboard layout/properties/etc.) The KBF layout is supported on Windows, Windows CE, Linux, Mac OS X, etc.

As much as possible, the implementation is a Program operating on Data concept. The Data (KBF) is created within Build-A-Board. The run-time software (deployed/implemented/installed/located) on the run-time target reads this data, displays the layout to the user, and then processes user actions based on what the user selects. The "Regular" Key Action is to create the down/up events as if a physical key was pressed. This is seen as a keystroke by the underlying application. There are other actions available, including opening a new layout (New KBF command) and running an arbitrary program (Exec command).

What are the project files? What should I open? What is PROJECT.TXT?

The project files are simple text files that describe in human readable form the layout & keyboard properties. They are an interim step towards a complete database of layouts. The zip format is just to compress & reduce disk space. If you see both a PROJECT.TXT and a zip, open the PROJECT.TXT, as this means the Project is "Open" (i.e. unzipped) and may have modifications that haven't been "zipped" up again (File | Close Project). We recommend you use the front-end display of layouts to get around the whole project file issue - just pick a layout, and go with it.

When I "F9 - Build" what am I creating? An EXE somewhere?
You are creating the KBF file (KeyBoard File). This is a singe file representation of the layout that can be used by the run-time software. Because it is now cross-platform, this is the "Data" part of the Program & Data concept (like a .DOC file contains the "document"). You "get" the keyboard you just created by loading the KBF in the run-time software. When you select a target platform, it also copies over install/run-time files - so theoretically you could take these over to the platform, install the run-time files, run the My-T-Soft binary/executable (e.g. MYTSOFT.EXE on windows) and then get the display / operation of the KEYBOARD.KBF (default KeyBoard File). For a Windows target, refer to the MSWIN32 folder (Shift-F11 to view) to see the "run-time" files - these are what gets deployed on a Windows system (and similarly for other platforms).
What is required for the target system? What does Run-time mean? How do I integrate it with my application?

Here is a quick run-down - refer below for further details, and use the Product Guide for even more details.

  1. Create or Modify a layout in the builder.
  2. Select Target in the Run-Time menu (e.g. Windows 32)
  3. Build (& execute to test)
  4. Install the Target (run-time) files on your deployment target
  5. Run My-T-Soft at a system level, or at application start (Shell/Exec/etc.)
  6. Use Developer's Kit Tools (or concepts) to move keyboard window on-screen when needed/off-screen when not
  7. Use an iterative approach to get the custom keyboard layout integrated into your application

Here is a more technical overview

  1. The approach to the user interface is to have the executable display a topmost window that presents a keyboard (or arbitrary button display) to the user. It handles input focus issues so any virtual keystrokes are seen as standard keystrokes to the application. This is the My-T-Soft program, sometimes referred to as the "Build-A-Board run-time". For example, on windows, when you run MYTSOFT.EXE it reads the KBF (KeyBoard File - KEYBOARD.KBF) and displays the layout as designed and built in Build-A-Board.
  2. The run-time software is an EXE (or program/binary process based). As such, it should be running at a system level, or at application startup (see more below)
  3. The user interface aspect is separated from the actions. All external Key Actions are handled by the MacroBat process (Macro Batch Processor). This is implemented as a separate process. So the 2 processes (My-T-Soft and MacroBat) must both be on the run-time target to read the Data (KBF file), display the layout to the user, and process the actions when a button is pressed. Note that with the CMD:EXEC any arbitrary process can be launched when the user initiates this action by pressing a button on the layout. New layouts can be opened with the CMD:NKBF command - a common approach for user control is to have a single button layout that opens the full layout, and then a minimize button that returns to the single button layout.
  4. In general, we recommend you run the keyboard (e.g. MYTSOFT.EXE in Windows) at system start, or application start - then during the life of your application, you can control access with the "MoveWindowMTS" function/concept - move it off-screen to remove it from the user, move it on-screen to display it for the user at the X/Y location you want. This keeps the process running, and you don't have any shut-down or startup delays. If done at the system level, StartUp group is typical, and if handled in the application, a Shell or Exec type function is typical.
  5. The most effective way to handle "on/off" is to move on-screen/off-screen. Using the New KBF (CMD:NKBF) the user can select different layouts. Refer to the MoveWindowMTS function (MOVEWMTS.EXE for windows, etc.) See the DEVKTDOC folder to open the Developer's Kit Documentation.

For a more detailed view & terminology, refer the Quick Usage Notes in the Product Guide.

Category: CommonType: Question/Answer Product: Build-A-BoardVersion: 2.20

Notes:



IMG Home PageIMG ProductsProduct DownloadsOrdering InformationTechnical Support and Frequently Asked QuestionsDeveloper's Corner and UtilitiesAbout IMG
CustomersIMG ResellersMedia InformationIMG Events / Trade ShowsUseful LinksIMG Contact InformationIMG Information / Policies