Preparing to Create Support for a Custom Toolkit

You can extend UFT support for any toolkit containing classes that extend java.awt.Component or org.eclipse.swt.widgets.Widget.

When you create a custom toolkit support set for each custom toolkit, the first step is to determine the set of classes that comprise your custom toolkit. For the purpose of Extensibility, a custom toolkit is a set of classes that extend the basic user interface component of the same native toolkit.

This does not prevent you from creating support for a toolkit containing classes that extend java.awt.Component, as well as those that extend org.eclipse.swt.widgets.Widget. Such a toolkit is simply seen as two separate custom toolkits, and you must create support separately for each set of classes.

Similarly, if you have user interface control classes that extend the basic user interface component of the same native toolkit, and are packaged in separate Java archives or class folders, you can treat them as one custom toolkit. This means you can create a single custom toolkit support set for all those classes.

Within a custom toolkit, you extend UFT support for each control (or group of similar controls) separately. You do this by creating custom support classes for the different custom control classes in the toolkit. (In this guide, custom support classes are also referred to as support classes.)

Before you extend UFT support for a custom control make sure you have full access to the control and understand its behavior. You must have an application in which you can view the control in action, and also have access to the class that implements it.

You do not need to modify any of the custom control's sources to support it in UFT, but you do need to be familiar with them. Make sure you know which members (fields and methods) you can access externally, the events for which you can listen, and so forth. You use this information when you design the support class. To implement the interface between UFT and the custom class, the support class uses custom class members. The support class can only access the members of the custom class that are defined as public.

In addition, you need access to the compiled classes in a Java archive or class folder because you add them to the classpath when compiling the support classes.