The Qubit Master application is designed with one goal in mind: to allow users to perform any given (repetitive) computer task by giving out a single voice command, key press or menu selection.

*  *  *

Example: Let us assume one wants to log-on to an online banking site. One should only speak out the assigned phrase, e.g. "Log-on to banking", and Qubit Master will perform the following tasks:

1. Open the online banking (log-in) web page in the default browser

2. Wait for the page to load: by looking at the window title, by waiting certain amount of time or by asking for a confirmation when to continue

3. Once page is loaded, it fills the log-in form with predefined text (e.g. user name and password) and presses the log-in button.

At each step of the execution, the animated character can announce what it is doing or confirm what to do next...

*  *  *

In order to reach this goal, certain basic (i.e. elementary) operations are defined and then any task is executed as a sequence of these basic operations.

Basic Operations are:

Opening files (programs or documents)

Opening web sites

Exploring folders

Inserting text

Pressing (keyboard) key combinations

Pressing message-box and dialog-box buttons

Miscellaneous (unclassifiable) operations (e.g. closing or minimizing windows)

Once user defines necessary basic operations, the more complicated tasks are specified as sequences (or groups) of these basic ones. [Examples]

So far we have only talked about 'operations'. Now it is time to introduce the notion of a 'command'. Every command contains an operation, but it also includes some additional data. 

Each command consists of the following elements:

Operation - different types of operations give different types of commands

Name (which should be unique)

Voice command i.e. the phrase associated to the operation

Verification status i.e. whether Qubit Master should double check before execution

Reply phrase - the phrase character speaks once voice command has been recognized

Reply animation - the animation character plays upon execution of the command

Storage location i.e. whether command should be added to the common (shared) commands package or to the currently loaded add-on package

Additional data, which varies with the type of the command.

 

[Proceed to the brief tutorial]