Specifications

• Conversely a configurator may define the licenseApplication entry point without defining the
“ApplicationLicense” property in case it does not need access to the license string outside of
the licenseApplication entry point.
Application discovery
Ideally a third-party application can be configured and used from within Switch immediately
after it is installed, without the need for separately launching the third-party application (for
example, to license it). This is not always feasible and Switch provides several fall-back options,
but the objective is to approach this optimal situation.
Application discovery is implemented in the findApplicationPath entry point.
Windows
The installer for the third-party application should make an entry in the system registry specifying
the full path of the executable (or a folder that contains it). This registry entry should be clearly
documented so that Switch can retrieve the information using the
Environment.findRegisteredApplication() function.
Otherwise the third-party application should be installed somewhere inside the standard “Program
Files” directory, so Switch can search the contents of the “Program Files” directory for the name
of the application using the Environment.findApplicationOnDisk() function.
Mac OS
If the third-party application is in a regular “.app” bundle with an appropriate property list,
Mac OS X will recognize the “.app” and add it to its central registry. Switch can then retrieve the
information using the Environment.findRegisteredApplication() function.
Otherwise the third-party application should be installed somewhere inside the standard
“Applications” folder, so Switch can search the contents of the Applications folder for the name
of the application using the Environment.findApplicationOnDisk() function.
Manual
On both platforms, if Switch does not find the third-party application, the user is offered a
“fall-back” option in the form of a context menu item on the configurator’s icon in the Elements
pane, which allows manually browsing the file system for the application.
Application licensing
Independent
In this option the user licenses the third-party application independently from Switch through
some user interface provided by or with the third-party application. For example, by entering
a license key in a dialog box or on a command line.
Although it violates the objective of allowing the application to be fully controlled from within
Switch, this may be the most logical option for regular interactive applications that offer a rich
user interface aside from the automation capabilities via Switch.
In Switch
Some third-party applications do not have a graphical user interface and are intended mostly
for integration with products such as Switch. Since the user never directly interacts with the
third-party application it is more logical to allow licensing from within Switch.
348
Enfocus Switch 10