Puts dev manual on website and links to it from new & noteworthy
diff --git a/documentation/developerManual/clientAPI/ch02s01.html b/documentation/developerManual/clientAPI/ch02s01.html
new file mode 100644
index 0000000..efe24e2
--- /dev/null
+++ b/documentation/developerManual/clientAPI/ch02s01.html
@@ -0,0 +1,87 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.1. The general idea</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="clientAPI.html" title="Chapter 2. Writing UI tests via API">
+<link rel="prev" href="clientAPI.html" title="Chapter 2. Writing UI tests via API">
+<link rel="next" href="ch02s02.html" title="2.2. General steps to take and class overview">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">2.1. The general idea</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="clientAPI.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 2. Writing UI tests via API</th>
+<td width="20%" align="right"> <a accesskey="n" href="ch02s02.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="clientAPI.html">Writing UI tests via API</a></span> > <span class="breadcrumb-node">The general idea</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id294369"></a>2.1. The general idea</h2></div></div></div>
+<div class="figure">
+<a name="api-idea"></a><div class="figure-contents"><div class="mediaobject"><img xmlns:d="http://docbook.org/ns/docbook" src="../images/api-idea.png"></div></div>
+<div class="figure-title">Figure 2.1. Idea behind the API</div>
+</div>
+<br class="figure-break"><p>
+ The main idea behind Jubula's client API is to allow the execution of
+ Test Steps (CAPs) from within arbitrary Java code e.g. JUnit test cases
+ (see <a class="xref" href="ch02s01.html#api-idea" title="Figure 2.1. Idea behind the API">Figure 2.1, “Idea behind the API”</a>). At the same time of shifting the paradigm to target a developer
+ audience we've tried to stick to our principles:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>offer high-level test steps that are equivalent to the ones
+ available in the ITE: all test steps that are being executed via
+ the API behave 1:1 the same as the ones executed by the ITE.
+ </p></li>
+<li class="listitem"><p>an API for all toolkits: the client API is available for all
+ toolkits supported by the ITE like JavaFX, AWT/Swing,
+ SWT/RCP/GEF, iOS, HTML, Win and WinApps.
+ </p></li>
+<li class="listitem"><p>
+ offer toolkit abstraction layer to keep your tests UI toolkit
+ independent: the usage of the API will also allow you to specify
+ your tests in a toolkit neutral way. Please note that for all of
+ the concrete toolkit wrapper types abstracted super types are
+ provided e.g. to address a
+ <span class="emphasis"><em>javafx.scene.control.CheckBox</em></span>
+ we provide the wrapper type containing its test steps
+ <span class="emphasis"><em>org.eclipse.jubula.toolkit.javafx.components.CheckBox
+ </em></span>
+ but the underlying abstracted toolkit conceptual component is
+ <span class="emphasis"><em>org.eclipse.jubula.toolkit.concrete.components.ButtonComponent
+ </em></span>
+ .
+ </p></li>
+<li class="listitem"><p>de-couple tests and real UI widgets: you still have to create
+ an object mapping (via the ITE and export it) to keep the
+ information that are required to determine which widget to address
+ during runtime independent from your test specification.
+ </p></li>
+<li class="listitem"><p>separation of test and AUT runtime environments: the JVM
+ executing the tests is a separate one (and may also e.g. run on
+ a different machine) from the one the AUT gets executed in. It's
+ communicating with the AUT VM via a TCP/IP connection.
+ </p></li>
+<li class="listitem"><p>the AUT-Agent manages the lifecycle of AUTs: starting /
+ stopping / restarting of AUTs is still done by instructing the
+ AUT-Agent to do so and may also be extended by the usage of
+ autrun to launch applications externally.
+ </p></li>
+</ul></div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/clientAPI/ch02s02.html b/documentation/developerManual/clientAPI/ch02s02.html
new file mode 100644
index 0000000..5795021
--- /dev/null
+++ b/documentation/developerManual/clientAPI/ch02s02.html
@@ -0,0 +1,71 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.2. General steps to take and class overview</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="clientAPI.html" title="Chapter 2. Writing UI tests via API">
+<link rel="prev" href="ch02s01.html" title="2.1. The general idea">
+<link rel="next" href="ch02s03.html" title="2.3. Exporting the Object Map in the ITE">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">2.2. General steps to take and class overview</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="ch02s01.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 2. Writing UI tests via API</th>
+<td width="20%" align="right"> <a accesskey="n" href="ch02s03.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="clientAPI.html">Writing UI tests via API</a></span> > <span class="breadcrumb-node">General steps to take and class overview</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id293975"></a>2.2. General steps to take and class overview</h2></div></div></div>
+<div class="figure">
+<a name="api-classes"></a><div class="figure-contents"><div class="mediaobject"><img xmlns:d="http://docbook.org/ns/docbook" src="../images/api-classes.png"></div></div>
+<div class="figure-title">Figure 2.2. The most important classes and their methods</div>
+</div>
+<br class="figure-break"><p> Taking this as a basis, a normal execution of test steps via the
+ client API requires - in general - the following steps:
+ </p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>Connect to an already running instance of the AUT-Agent.
+ </p></li>
+<li class="listitem"><p>Instruct it to start an AUT or retrieve a list of all
+ currently known AUT identifier.
+ </p></li>
+<li class="listitem"><p>Connect to the AUT by using the AUT identifier.
+ </p></li>
+<li class="listitem"><p>
+ Execute an arbitrary amount of CAPs (<span class="strong"><strong>C</strong></span>omponent
+ <span class="strong"><strong>A</strong></span>ction
+ <span class="strong"><strong>P</strong></span>arameter also known as Test steps) on this established
+ connection to an AUT. Note: there is no result
+ processing implemented.
+ </p></li>
+<li class="listitem"><p>Disconnect from the AUT.
+ </p></li>
+<li class="listitem"><p>Stop the AUT.
+ </p></li>
+<li class="listitem"><p>Disconnect from the AUT-Agent.
+ </p></li>
+</ol></div>
+<p>
+ <a class="xref" href="ch02s02.html#api-classes" title="Figure 2.2. The most important classes and their methods">Figure 2.2, “The most important classes and their methods”</a>
+ allows to get a general overview of the toolkit neutral parts of the
+ client API.
+ </p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/clientAPI/ch02s03.html b/documentation/developerManual/clientAPI/ch02s03.html
new file mode 100644
index 0000000..b3614e9
--- /dev/null
+++ b/documentation/developerManual/clientAPI/ch02s03.html
@@ -0,0 +1,70 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.3. Exporting the Object Map in the ITE</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="clientAPI.html" title="Chapter 2. Writing UI tests via API">
+<link rel="prev" href="ch02s02.html" title="2.2. General steps to take and class overview">
+<link rel="next" href="creating-cap-instances.html" title="2.4. Creating CAP instances">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">2.3. Exporting the Object Map in the ITE</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="ch02s02.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 2. Writing UI tests via API</th>
+<td width="20%" align="right"> <a accesskey="n" href="creating-cap-instances.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="clientAPI.html">Writing UI tests via API</a></span> > <span class="breadcrumb-node">Exporting the Object Map in the ITE</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id294096"></a>2.3. Exporting the Object Map in the ITE</h2></div></div></div>
+<div class="figure">
+<a name="export-om"></a><div class="figure-contents"><div class="mediaobject"><img xmlns:d="http://docbook.org/ns/docbook" src="../images/export-om.png"></div></div>
+<div class="figure-title">Figure 2.3. Object Mapping Editor export function</div>
+</div>
+<br class="figure-break"><p>
+ In order to create an executable CAP instance (see <a class="xref" href="creating-cap-instances.html" title="2.4. Creating CAP instances">Section 2.4, “Creating CAP instances”</a>) you require a valid
+ <span class="emphasis"><em>org.eclipse.jubula.tools.ComponentIdentifier</em></span> instance. To get that, you need to
+ </p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>Start the ITE, open the project and the Object Mapping Editor for the AUT you wan't to export the Object Map for. (Or, if you are starting from scratch, firstly create a new project and do the object mapping there.)
+ </p></li>
+<li class="listitem"><p>Choose "Export Object Mapping for use in API" from the context menu of the editor as shown in <a class="xref" href="ch02s03.html#export-om" title="Figure 2.3. Object Mapping Editor export function">Figure 2.3, “Object Mapping Editor export function”</a>.
+ </p></li>
+<li class="listitem"><p>Decide whether you wan't to use a plain properties file or a Java class with static fields.
+ Both formats will then contain all necessary information (one mapping for each mapped logical component name) to address the UI widget when the test gets executed.
+ </p></li>
+<li class="listitem"><p>Place this resource on the classpath of your test project.
+ </p></li>
+<li class="listitem"><p>If you're using the properties file format you can load the mapping and its identifier by using <span class="emphasis"><em>MakeR.createObjectMapping(...).get("logicalComponentName")</em></span>.
+ Otherwise you can simply access the static fields of the exported class.
+ </p></li>
+</ol></div>
+<p xmlns:d="http://docbook.org/ns/docbook"><table>
+<colgroup>
+<col>
+<col>
+</colgroup>
+<tbody><tr>
+<td><img align="bottom" width="102" height="89" src="../images/img1.jpg"></td>
+<td class="topbotline"><span class="strong"><strong>Currently the structure and information used to address a component (the mapping value itself) is not part of the API itself. Hence you still have to maintain this information within the ITE.
+ </strong></span></td>
+</tr></tbody>
+</table></p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/clientAPI/ch02s05.html b/documentation/developerManual/clientAPI/ch02s05.html
new file mode 100644
index 0000000..86a61dd
--- /dev/null
+++ b/documentation/developerManual/clientAPI/ch02s05.html
@@ -0,0 +1,82 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.5. General setup information</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="clientAPI.html" title="Chapter 2. Writing UI tests via API">
+<link rel="prev" href="creating-cap-instances.html" title="2.4. Creating CAP instances">
+<link rel="next" href="ch02s06.html" title="2.6. Sample setup of the API usage">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">2.5. General setup information</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="creating-cap-instances.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 2. Writing UI tests via API</th>
+<td width="20%" align="right"> <a accesskey="n" href="ch02s06.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="clientAPI.html">Writing UI tests via API</a></span> > <span class="breadcrumb-node">General setup information</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id295608"></a>2.5. General setup information</h2></div></div></div>
+<p>The following section describes where to find the relevant JARs / artifacts to use the API.
+ The provided API has a miminum required runtime environment of <span class="strong"><strong>Java 6</strong></span>.</p>
+<p>In general the usage of the client API falls apart into three categories of JARs / maven artifacts
+ / OSGi bundles:</p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p>Each project requires dependencies to <span class="strong"><strong>all</strong></span> of the <span class="strong"><strong>toolkit neutral parts</strong></span>
+ of the API:</p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>org.eclipse.jubula.client.api</p></li>
+<li class="listitem"><p>org.eclipse.jubula.client.api.commands</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.api</p></li>
+<li class="listitem"><p>org.eclipse.jubula.tools</p></li>
+<li class="listitem"><p>org.eclipse.jubula.communication</p></li>
+</ul></div>
+</li>
+<li class="listitem">
+<p>Each project requires dependencies to <span class="strong"><strong>indiviual</strong></span> parts of the <span class="strong"><strong>toolkit specific elements</strong></span>
+ dependent from the used toolkit of the API:</p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>org.eclipse.jubula.toolkit.base.api</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.concrete.api</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.javafx.api</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.swt.api</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit...TOOLKIT_ID...api</p></li>
+</ul></div>
+<p>Please keep in mind that <span class="strong"><strong>toolkits are derived</strong></span> from each other. So if you're e.g. setting up a JavaFX projects it is also
+ necessary to include the direct dependency to the specific toolkit artifact "org.eclipse.jubula.toolkit.javafx.api" itself as well as the toolkits its based upon:
+ "org.eclipse.jubula.toolkit.concrete.api" and its base "org.eclipse.jubula.toolkit.base.api".</p>
+</li>
+<li class="listitem">
+<p>Each project also requires dependencies to <span class="strong"><strong>all</strong></span> of the <span class="strong"><strong>3rd party dependencies</strong></span>
+ of the API:</p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>Apache Commons Lang 2.4</p></li>
+<li class="listitem"><p>Apache Commons Codec 1.4</p></li>
+<li class="listitem"><p>SLF4j API</p></li>
+<li class="listitem"><p>XStream 1.3.1</p></li>
+<li class="listitem"><p>XPP3 min 1.1.4c</p></li>
+<li class="listitem"><p>xmlpull 1.1.3.4a</p></li>
+</ul></div>
+</li>
+</ol></div>
+<p>You can find the artifacts in different shapes (plain JAR, maven artifact and OSGi bundles) within
+ the <span class="emphasis"><em>ITEInstallationFolder/development/api</em></span> folder.</p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/clientAPI/ch02s06.html b/documentation/developerManual/clientAPI/ch02s06.html
new file mode 100644
index 0000000..54fff62
--- /dev/null
+++ b/documentation/developerManual/clientAPI/ch02s06.html
@@ -0,0 +1,52 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.6. Sample setup of the API usage</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="clientAPI.html" title="Chapter 2. Writing UI tests via API">
+<link rel="prev" href="ch02s05.html" title="2.5. General setup information">
+<link rel="next" href="../toolkitExtension/toolkitExtension.html" title="Chapter 3. Creating toolkit extensions for custom UI widgets">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">2.6. Sample setup of the API usage</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="ch02s05.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 2. Writing UI tests via API</th>
+<td width="20%" align="right"> <a accesskey="n" href="../toolkitExtension/toolkitExtension.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="clientAPI.html">Writing UI tests via API</a></span> > <span class="breadcrumb-node">Sample setup of the API usage</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id295851"></a>2.6. Sample setup of the API usage</h2></div></div></div>
+<div class="figure">
+<a name="start-aut"></a><div class="figure-contents"><div class="mediaobject"><img xmlns:d="http://docbook.org/ns/docbook" src="../images/start-aut.png"></div></div>
+<div class="figure-title">Figure 2.6. Starting the RCP-SimpleAdder AUT via API</div>
+</div>
+<br class="figure-break"><p>A fully executable example setup for the RCP toolkit showing a basic SimpleAdder AUT start - see <a class="xref" href="ch02s06.html#start-aut" title="Figure 2.6. Starting the RCP-SimpleAdder AUT via API">Figure 2.6, “Starting the RCP-SimpleAdder AUT via API”</a> -
+ and test run - see <a class="xref" href="ch02s06.html#test-execution" title="Figure 2.7. Exectuing a first test">Figure 2.7, “Exectuing a first test”</a> - can be found in the git-Repository contained within every ITE installation. It's located in
+ <span class="emphasis"><em>ITEInstallationFolder/development/git/org.eclipse.jubula.core.git</em></span>. Simply create a clone
+ of that repository and checkout the Eclipse project <span class="emphasis"><em>org.eclipse.jubula.qa.api.rcp</em></span>.
+ You still have to adjust the path to the local maven repository within the pom.xml of that project and point to the
+ one included in the installation: <span class="emphasis"><em>ITEInstallationFolder/development/api/m2-repo</em></span>.</p>
+<div class="figure">
+<a name="test-execution"></a><div class="figure-contents"><div class="mediaobject"><img xmlns:d="http://docbook.org/ns/docbook" src="../images/test-execution.png"></div></div>
+<div class="figure-title">Figure 2.7. Exectuing a first test</div>
+</div>
+<br class="figure-break"><p>However the usage of maven is not mandatory - you can also simply setup a plain Java project using the artifacts as plain JARs on the classpath.</p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/clientAPI/clientAPI.html b/documentation/developerManual/clientAPI/clientAPI.html
new file mode 100644
index 0000000..7457c81
--- /dev/null
+++ b/documentation/developerManual/clientAPI/clientAPI.html
@@ -0,0 +1,45 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter 2. Writing UI tests via API</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="../index.html" title="Jubula Developer Manual">
+<link rel="prev" href="../introduction/introduction.html" title="Chapter 1. Introduction">
+<link rel="next" href="ch02s01.html" title="2.1. The general idea">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">Chapter 2. Writing UI tests via API</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="../introduction/introduction.html">Prev</a> </td>
+<th width="60%" align="center"> </th>
+<td width="20%" align="right"> <a accesskey="n" href="ch02s01.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-node">Writing UI tests via API</span>
+</div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="clientAPI"></a>Chapter 2. Writing UI tests via API</h1></div></div></div>
+<div class="toc"><dl class="toc">
+<dt><span class="section"><a href="ch02s01.html">2.1. The general idea</a></span></dt>
+<dt><span class="section"><a href="ch02s02.html">2.2. General steps to take and class overview</a></span></dt>
+<dt><span class="section"><a href="ch02s03.html">2.3. Exporting the Object Map in the ITE</a></span></dt>
+<dt><span class="section"><a href="creating-cap-instances.html">2.4. Creating CAP instances</a></span></dt>
+<dt><span class="section"><a href="ch02s05.html">2.5. General setup information</a></span></dt>
+<dt><span class="section"><a href="ch02s06.html">2.6. Sample setup of the API usage</a></span></dt>
+</dl></div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/clientAPI/creating-cap-instances.html b/documentation/developerManual/clientAPI/creating-cap-instances.html
new file mode 100644
index 0000000..9850b63
--- /dev/null
+++ b/documentation/developerManual/clientAPI/creating-cap-instances.html
@@ -0,0 +1,60 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.4. Creating CAP instances</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="clientAPI.html" title="Chapter 2. Writing UI tests via API">
+<link rel="prev" href="ch02s03.html" title="2.3. Exporting the Object Map in the ITE">
+<link rel="next" href="ch02s05.html" title="2.5. General setup information">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">2.4. Creating CAP instances</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="ch02s03.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 2. Writing UI tests via API</th>
+<td width="20%" align="right"> <a accesskey="n" href="ch02s05.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="clientAPI.html">Writing UI tests via API</a></span> > <span class="breadcrumb-node">Creating CAP instances</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="creating-cap-instances"></a>2.4. Creating CAP instances</h2></div></div></div>
+<div class="figure">
+<a name="toolkit-factories"></a><div class="figure-contents"><div class="mediaobject"><img xmlns:d="http://docbook.org/ns/docbook" src="../images/tk-factories.png"></div></div>
+<div class="figure-title">Figure 2.4. JavaFX-Toolkit component factory usage to create an instance for a CheckBox</div>
+</div>
+<br class="figure-break"><p>In order to create executable instances of a <span class="emphasis"><em>org.eclipse.jubula.communication.CAP</em></span> (Test Step) you have to use the corresponding
+ factory methods available for each toolkit and pass a valid and fitting ComponentIdentifier:</p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>org.eclipse.jubula.toolkit.javafx.JavafxComponents - see e.g. the <a class="xref" href="creating-cap-instances.html#toolkit-factories" title="Figure 2.4. JavaFX-Toolkit component factory usage to create an instance for a CheckBox">Figure 2.4, “JavaFX-Toolkit component factory usage to create an instance for a CheckBox”</a></p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.swing.SwingComponents</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.html.HtmlComponents</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.swt.SwtComponents</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.ios.IosComponents</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.winapps.WinappsComponents</p></li>
+<li class="listitem"><p>org.eclipse.jubula.toolkit.win.WinComponents</p></li>
+</ul></div>
+<p>On these UI component placeholder instances you can call methods that will return
+ an executable CAP that, when being executed on the AUT connection,
+ performs the specified test step:</p>
+<div class="figure">
+<a name="cap-factory-methods"></a><div class="figure-contents"><div class="mediaobject"><img xmlns:d="http://docbook.org/ns/docbook" src="../images/cap-factory-methods.png"></div></div>
+<div class="figure-title">Figure 2.5. Creating a CAP instance</div>
+</div>
+<br class="figure-break">
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/functions/functions.html b/documentation/developerManual/functions/functions.html
new file mode 100644
index 0000000..2833e86
--- /dev/null
+++ b/documentation/developerManual/functions/functions.html
@@ -0,0 +1,46 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter 5. Creating ITE functions</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="../index.html" title="Jubula Developer Manual">
+<link rel="prev" href="../gefToolkitExtension/gefreference.html" title="4.2. Accessibility plug-in example">
+<link rel="next" href="../keyboardLayout/keyboardLayout.html" title="Chapter 6. Adding keyboard layout files">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">Chapter 5. Creating ITE functions</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="../gefToolkitExtension/gefreference.html">Prev</a> </td>
+<th width="60%" align="center"> </th>
+<td width="20%" align="right"> <a accesskey="n" href="../keyboardLayout/keyboardLayout.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-node">Creating ITE functions</span>
+</div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="functions"></a>Chapter 5. Creating ITE functions</h1></div></div></div>
+<p>
+ Functions represent program code that is evaluated during test
+ execution. In order to define a new function, you will need to
+ create an extension for the extension point
+ <span class="emphasis"><em>org.eclipse.jubula.client.core.functions</em></span>, which
+ can be found in the bundle
+ <span class="emphasis"><em>org.eclipse.jubula.client.core</em></span>. This bundle
+ also contains reference implementations of the extension point.
+ </p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/gefToolkitExtension/creating-an-accessibility-plug-in.html b/documentation/developerManual/gefToolkitExtension/creating-an-accessibility-plug-in.html
new file mode 100644
index 0000000..8021987
--- /dev/null
+++ b/documentation/developerManual/gefToolkitExtension/creating-an-accessibility-plug-in.html
@@ -0,0 +1,41 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>4.1. Creating an accessibility plug-in</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="creating-gef-toolkit-extensions.html" title="Chapter 4. Creating GEF toolkit extensions">
+<link rel="prev" href="creating-gef-toolkit-extensions.html" title="Chapter 4. Creating GEF toolkit extensions">
+<link rel="next" href="setting-up-your-workspace.html" title="4.1.1. Setting up your Workspace">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">4.1. Creating an accessibility plug-in</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="creating-gef-toolkit-extensions.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 4. Creating GEF toolkit extensions</th>
+<td width="20%" align="right"> <a accesskey="n" href="setting-up-your-workspace.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="creating-gef-toolkit-extensions.html">Creating GEF toolkit extensions</a></span> > <span class="breadcrumb-node">Creating an accessibility plug-in</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="creating-an-accessibility-plug-in"></a>4.1. Creating an accessibility plug-in</h2></div></div></div>
+<div class="toc"><dl class="toc">
+<dt><span class="section"><a href="setting-up-your-workspace.html">4.1.1. Setting up your Workspace</a></span></dt>
+<dt><span class="section"><a href="walkthrough.html">4.1.2. Walkthrough</a></span></dt>
+</dl></div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/gefToolkitExtension/creating-gef-toolkit-extensions.html b/documentation/developerManual/gefToolkitExtension/creating-gef-toolkit-extensions.html
new file mode 100644
index 0000000..47bd29e
--- /dev/null
+++ b/documentation/developerManual/gefToolkitExtension/creating-gef-toolkit-extensions.html
@@ -0,0 +1,59 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter 4. Creating GEF toolkit extensions</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="../index.html" title="Jubula Developer Manual">
+<link rel="prev" href="../toolkitExtension/extensionExamples.html" title="3.4. ITE and remote control extension examples">
+<link rel="next" href="creating-an-accessibility-plug-in.html" title="4.1. Creating an accessibility plug-in">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">Chapter 4. Creating GEF toolkit extensions</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="../toolkitExtension/extensionExamples.html">Prev</a> </td>
+<th width="60%" align="center"> </th>
+<td width="20%" align="right"> <a accesskey="n" href="creating-an-accessibility-plug-in.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-node">Creating GEF toolkit extensions</span>
+</div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="creating-gef-toolkit-extensions"></a>Chapter 4. Creating GEF toolkit extensions</h1></div></div></div>
+<div class="toc"><dl class="toc">
+<dt><span class="section"><a href="creating-an-accessibility-plug-in.html">4.1. Creating an accessibility plug-in</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="setting-up-your-workspace.html">4.1.1. Setting up your Workspace</a></span></dt>
+<dt><span class="section"><a href="walkthrough.html">4.1.2. Walkthrough</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="gefreference.html">4.2. Accessibility plug-in example</a></span></dt>
+</dl></div>
+<p>
+ Although the identification and testing of GEF components is
+ supported out-of-the-box, it is highly recommended that application
+ developers enhance this support by implementing an accessibility
+ plug-in for their application. Such a plug-in makes identification
+ of GEF components more robust and allows tests to reference
+ additional components, such as connection anchors.
+ </p>
+<p>
+ Apart from the general description for creating toolkit extensions
+ in this manual, we give further information for extending
+ the GEF toolkit. The following sections explain how to develop a GEF
+ accessibility plug-in.
+ </p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/gefToolkitExtension/gefreference.html b/documentation/developerManual/gefToolkitExtension/gefreference.html
new file mode 100644
index 0000000..e9500d0
--- /dev/null
+++ b/documentation/developerManual/gefToolkitExtension/gefreference.html
@@ -0,0 +1,54 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>4.2. Accessibility plug-in example</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="creating-gef-toolkit-extensions.html" title="Chapter 4. Creating GEF toolkit extensions">
+<link rel="prev" href="walkthrough.html" title="4.1.2. Walkthrough">
+<link rel="next" href="../functions/functions.html" title="Chapter 5. Creating ITE functions">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">4.2. Accessibility plug-in example</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="walkthrough.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 4. Creating GEF toolkit extensions</th>
+<td width="20%" align="right"> <a accesskey="n" href="../functions/functions.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="creating-gef-toolkit-extensions.html">Creating GEF toolkit extensions</a></span> > <span class="breadcrumb-node">Accessibility plug-in example</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="gefreference"></a>4.2. Accessibility plug-in example</h2></div></div></div>
+<p>
+ A sample accessibility plug-in for certain elements of the Logic
+ Diagram sample plug-in project (contributed from the GEF plug-ins
+ to Eclipse's New Project Wizard) are included in the installation.
+ A default implementation can be found in the directory
+ <span class="input">examples/development/gef</span>
+ . There you will find a
+ zip-file containing a full accessibility plug-in example.
+ </p>
+<p>
+ You can import the sample accessibility plug-in into an Eclipse
+ workspace in order to examine the general structure.
+ The Java documentation of the source code, which is included in the
+ target platform definition, contains information about
+ <span class="input">IEditPartIdentifier</span>
+ from the package named <span class="emphasis"><em>org.eclipse.jubula.rc.rcp.gef.identifier</em></span>.
+ </p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/gefToolkitExtension/setting-up-your-workspace.html b/documentation/developerManual/gefToolkitExtension/setting-up-your-workspace.html
new file mode 100644
index 0000000..ff0f237
--- /dev/null
+++ b/documentation/developerManual/gefToolkitExtension/setting-up-your-workspace.html
@@ -0,0 +1,63 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>4.1.1. Setting up your Workspace</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="creating-an-accessibility-plug-in.html" title="4.1. Creating an accessibility plug-in">
+<link rel="prev" href="creating-an-accessibility-plug-in.html" title="4.1. Creating an accessibility plug-in">
+<link rel="next" href="walkthrough.html" title="4.1.2. Walkthrough">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">4.1.1. Setting up your Workspace</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="creating-an-accessibility-plug-in.html">Prev</a> </td>
+<th width="60%" align="center">4.1. Creating an accessibility plug-in</th>
+<td width="20%" align="right"> <a accesskey="n" href="walkthrough.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="creating-gef-toolkit-extensions.html">Creating GEF toolkit extensions</a></span> > <span class="breadcrumb-link"><a href="creating-an-accessibility-plug-in.html">Creating an accessibility plug-in</a></span> > <span class="breadcrumb-node">Setting up your Workspace</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="setting-up-your-workspace"></a>4.1.1. Setting up your Workspace</h3></div></div></div>
+<p>
+ Although you can use the IDE of your choice to develop your
+ accessibility plug-in, this guide will use Eclipse with PDE
+ plug-ins.
+ </p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>
+ Once you have created your new workspace, change that
+ workspace’s <span class="strong"><strong>Target
+ Platform</strong></span> by using the description mentioned in
+ this manual, as well as all plug-ins that make up
+ your AUT.
+ </p></li>
+<li class="listitem"><p>
+ Create a new <span class="strong"><strong>Plug-in
+ Project</strong></span>. The default values proposed by the
+ wizard are acceptable, so simply enter a name for your new
+ accessibility project and complete the wizard without
+ additional modifications.
+ </p></li>
+<li class="listitem"><p>
+ You now have a workspace with a properly configured target
+ platform as well as a new plug-in project. You can now begin
+ developing your GEF toolkit extension.
+ </p></li>
+</ol></div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/gefToolkitExtension/walkthrough.html b/documentation/developerManual/gefToolkitExtension/walkthrough.html
new file mode 100644
index 0000000..ef4f6ea
--- /dev/null
+++ b/documentation/developerManual/gefToolkitExtension/walkthrough.html
@@ -0,0 +1,113 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>4.1.2. Walkthrough</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="creating-an-accessibility-plug-in.html" title="4.1. Creating an accessibility plug-in">
+<link rel="prev" href="setting-up-your-workspace.html" title="4.1.1. Setting up your Workspace">
+<link rel="next" href="gefreference.html" title="4.2. Accessibility plug-in example">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">4.1.2. Walkthrough</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="setting-up-your-workspace.html">Prev</a> </td>
+<th width="60%" align="center">4.1. Creating an accessibility plug-in</th>
+<td width="20%" align="right"> <a accesskey="n" href="gefreference.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="creating-gef-toolkit-extensions.html">Creating GEF toolkit extensions</a></span> > <span class="breadcrumb-link"><a href="creating-an-accessibility-plug-in.html">Creating an accessibility plug-in</a></span> > <span class="breadcrumb-node">Walkthrough</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="walkthrough"></a>4.1.2. Walkthrough</h3></div></div></div>
+<p>
+ The first step for implementing your accessibility plug-in is to
+ create identifiers for each type of GEF component that you wish
+ to make accessible for tests. An identifier is a Java class that
+ implements <span class="input">IEditPartIdentifier</span> from the package
+ named
+ <span class="emphasis"><em>org.eclipse.jubula.rc.rcp.e3.gef.identifier</em></span>
+ and provides additional and/or more precise information about a
+ specific <span class="input">EditPart</span> from the package named
+ <span class="emphasis"><em>org.eclipse.gef</em></span>. The granularity of your
+ identifier classes will depend on the class hierarchy of the
+ edit parts in the AUT. For example, if many of the edit parts
+ share a common superclass, then you can write a single
+ Identifier for that superclass that will be able to provide
+ accessibility for all edit parts that inherit from that
+ superclass. See the example in <a class="xref" href="gefreference.html" title="4.2. Accessibility plug-in example">Section 4.2, “Accessibility plug-in example”</a>, which
+ shows a sample implementation.
+ </p>
+<p>
+ The next step is to create an adapter factory. This extension
+ provides information regarding which identifier to use for each
+ edit part.
+ </p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>
+ Open the <span class="input">plugin.xml</span> file from your
+ accessibility plug-in and select the
+ <span class="strong"><strong>Extension</strong></span> tab.
+ </p></li>
+<li class="listitem"><p>
+ Add an instance of the
+ <span class="emphasis"><em>org.eclipse.core.runtime.adapters</em></span>
+ extension.
+ </p></li>
+<li class="listitem"><p>
+ Add a <span class="strong"><strong>factory</strong></span> to the new
+ extension for each type of GEF component for which you wish
+ to provide accessibility. Each factory must implement
+ <span class="input">IEditPartIdentifier</span> from the package named
+ <span class="emphasis"><em>org.eclipse.jubula.rc.rcp.e3.gef.identifier</em></span>
+ to provide adapters from the GEF component that implements
+ <span class="input">EditPart</span> from
+ <span class="emphasis"><em>org.eclipse.gef</em></span>.
+ </p></li>
+<li class="listitem"><p>
+ Once you have defined your adapter factory, you will need to
+ implement it. Your adapter factory, which must implement
+ <span class="input">IAdapaterFactory</span> from the package named
+ <span class="emphasis"><em>org.eclipse.core.runtime</em></span>, provides
+ appropriate instances of your created identifiers for a
+ given edit part. See <a class="xref" href="gefreference.html" title="4.2. Accessibility plug-in example">Section 4.2, “Accessibility plug-in example”</a> for a sample
+ implementation.
+ </p></li>
+<li class="listitem">
+<p>
+ Once you have created your identifiers<br xmlns:d="http://docbook.org/ns/docbook"> and adapter
+ factories, you can export and deploy your plug-in to use it
+ in your AUT.
+ </p>
+<p xmlns:d="http://docbook.org/ns/docbook"><table>
+<colgroup>
+<col>
+<col>
+</colgroup>
+<tbody><tr>
+<td><img align="bottom" width="100" height="91" src="../images/img2.jpg"></td>
+<td class="topbotline"><span class="strong"><strong>
+ When starting your AUT after adding
+ or replacing your accessibility plug-in, it is recommended
+ that the AUT starts with the <span class="input">-clean</span>
+ parameter.
+ </strong></span></td>
+</tr></tbody>
+</table></p>
+</li>
+</ol></div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/images/api-classes.png b/documentation/developerManual/images/api-classes.png
new file mode 100644
index 0000000..e82faab
--- /dev/null
+++ b/documentation/developerManual/images/api-classes.png
Binary files differ
diff --git a/documentation/developerManual/images/api-idea.png b/documentation/developerManual/images/api-idea.png
new file mode 100644
index 0000000..a6622d7
--- /dev/null
+++ b/documentation/developerManual/images/api-idea.png
Binary files differ
diff --git a/documentation/developerManual/images/cap-factory-methods.png b/documentation/developerManual/images/cap-factory-methods.png
new file mode 100644
index 0000000..668bf86
--- /dev/null
+++ b/documentation/developerManual/images/cap-factory-methods.png
Binary files differ
diff --git a/documentation/developerManual/images/export-om.png b/documentation/developerManual/images/export-om.png
new file mode 100644
index 0000000..07871e9
--- /dev/null
+++ b/documentation/developerManual/images/export-om.png
Binary files differ
diff --git a/documentation/developerManual/images/img1.jpg b/documentation/developerManual/images/img1.jpg
new file mode 100644
index 0000000..c9afc81
--- /dev/null
+++ b/documentation/developerManual/images/img1.jpg
Binary files differ
diff --git a/documentation/developerManual/images/img2.jpg b/documentation/developerManual/images/img2.jpg
new file mode 100644
index 0000000..ee85bf1
--- /dev/null
+++ b/documentation/developerManual/images/img2.jpg
Binary files differ
diff --git a/documentation/developerManual/images/start-aut.png b/documentation/developerManual/images/start-aut.png
new file mode 100644
index 0000000..ca8296a
--- /dev/null
+++ b/documentation/developerManual/images/start-aut.png
Binary files differ
diff --git a/documentation/developerManual/images/test-execution.png b/documentation/developerManual/images/test-execution.png
new file mode 100644
index 0000000..9f9b68e
--- /dev/null
+++ b/documentation/developerManual/images/test-execution.png
Binary files differ
diff --git a/documentation/developerManual/images/tk-factories.png b/documentation/developerManual/images/tk-factories.png
new file mode 100644
index 0000000..fae11ab
--- /dev/null
+++ b/documentation/developerManual/images/tk-factories.png
Binary files differ
diff --git a/documentation/developerManual/index.html b/documentation/developerManual/index.html
new file mode 100644
index 0000000..05ae778
--- /dev/null
+++ b/documentation/developerManual/index.html
@@ -0,0 +1,85 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Jubula Developer Manual</title>
+<link rel="stylesheet" type="text/css" href="../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="index.html" title="Jubula Developer Manual">
+<link rel="next" href="introduction/introduction.html" title="Chapter 1. Introduction">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">Jubula Developer Manual</th></tr>
+<tr>
+<td width="20%" align="left"> </td>
+<th width="60%" align="center"> </th>
+<td width="20%" align="right"> <a accesskey="n" href="introduction/introduction.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs"></div>
+<div class="book">
+<div class="titlepage">
+<div><div><h1 class="title">
+<a name="developerManual"></a>Jubula Developer Manual</h1></div></div>
+<hr>
+</div>
+<div class="toc">
+<div class="toc-title">Table of Contents</div>
+<dl class="toc">
+<dt><span class="chapter"><a href="introduction/introduction.html">1. Introduction</a></span></dt>
+<dt><span class="chapter"><a href="clientAPI/clientAPI.html">2. Writing UI tests via API</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="clientAPI/ch02s01.html">2.1. The general idea</a></span></dt>
+<dt><span class="section"><a href="clientAPI/ch02s02.html">2.2. General steps to take and class overview</a></span></dt>
+<dt><span class="section"><a href="clientAPI/ch02s03.html">2.3. Exporting the Object Map in the ITE</a></span></dt>
+<dt><span class="section"><a href="clientAPI/creating-cap-instances.html">2.4. Creating CAP instances</a></span></dt>
+<dt><span class="section"><a href="clientAPI/ch02s05.html">2.5. General setup information</a></span></dt>
+<dt><span class="section"><a href="clientAPI/ch02s06.html">2.6. Sample setup of the API usage</a></span></dt>
+</dl></dd>
+<dt><span class="chapter"><a href="toolkitExtension/toolkitExtension.html">3. Creating toolkit extensions for custom UI widgets</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="toolkitExtension/requirements.html">3.1. Requirements</a></span></dt>
+<dt><span class="section"><a href="toolkitExtension/iteExtension.html">3.2. ITE extension</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="toolkitExtension/creating-the-toolkit-plug-in.html">3.2.1. Creating the toolkit plug-in</a></span></dt>
+<dt><span class="section"><a href="toolkitExtension/deploying-the-toolkit-plug-in.html">3.2.2. Deploying the toolkit plug-in</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="toolkitExtension/deploying-the-toolkit-plug-in.html#create-an-update-site-for-the-toolkit-feature">3.2.2.1. Create an update site for the toolkit feature</a></span></dt>
+<dt><span class="section"><a href="toolkitExtension/deploying-the-toolkit-plug-in.html#install-the-toolkit-feature-from-the-update-site">3.2.2.2. Install the toolkit feature from the update site</a></span></dt>
+</dl></dd>
+</dl></dd>
+<dt><span class="section"><a href="toolkitExtension/remoteControlExtension.html">3.3. Remote control extension</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="toolkitExtension/creating-the-fragment.html">3.3.1. Creating the fragment</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="toolkitExtension/creating-the-fragment.html#creating-an-adapter">3.3.1.1. Creating an adapter</a></span></dt>
+<dt><span class="section"><a href="toolkitExtension/creating-the-fragment.html#creating-a-tester-class">3.3.1.2. Creating a Tester Class</a></span></dt>
+<dt><span class="section"><a href="toolkitExtension/creating-the-fragment.html#creating-an-container-adapter">3.3.1.3. Creating an container adapter</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="toolkitExtension/deploying-the-fragment.html">3.3.2. Deploying the fragment</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="toolkitExtension/extensionExamples.html">3.4. ITE and remote control extension examples</a></span></dt>
+</dl></dd>
+<dt><span class="chapter"><a href="gefToolkitExtension/creating-gef-toolkit-extensions.html">4. Creating GEF toolkit extensions</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="gefToolkitExtension/creating-an-accessibility-plug-in.html">4.1. Creating an accessibility plug-in</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="gefToolkitExtension/setting-up-your-workspace.html">4.1.1. Setting up your Workspace</a></span></dt>
+<dt><span class="section"><a href="gefToolkitExtension/walkthrough.html">4.1.2. Walkthrough</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="gefToolkitExtension/gefreference.html">4.2. Accessibility plug-in example</a></span></dt>
+</dl></dd>
+<dt><span class="chapter"><a href="functions/functions.html">5. Creating ITE functions</a></span></dt>
+<dt><span class="chapter"><a href="keyboardLayout/keyboardLayout.html">6. Adding keyboard layout files</a></span></dt>
+</dl>
+</div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/introduction/introduction.html b/documentation/developerManual/introduction/introduction.html
new file mode 100644
index 0000000..41c81a4
--- /dev/null
+++ b/documentation/developerManual/introduction/introduction.html
@@ -0,0 +1,48 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter 1. Introduction</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="../index.html" title="Jubula Developer Manual">
+<link rel="prev" href="../index.html" title="Jubula Developer Manual">
+<link rel="next" href="../clientAPI/clientAPI.html" title="Chapter 2. Writing UI tests via API">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">Chapter 1. Introduction</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="../index.html">Prev</a> </td>
+<th width="60%" align="center"> </th>
+<td width="20%" align="right"> <a accesskey="n" href="../clientAPI/clientAPI.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-node">Introduction</span>
+</div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="introduction"></a>Chapter 1. Introduction</h1></div></div></div>
+<p>This manual aims for Java and OSGi bundle developers. It describes how
+ to use and extend the ITE on a programmatic level.</p>
+<p><a class="xref" href="../clientAPI/clientAPI.html" title="Chapter 2. Writing UI tests via API">Chapter 2, <i>Writing UI tests via API</i></a> is a general starting point for information
+ on writing UI tests via the ITEs API.</p>
+<p>This handbook also shows general steps for creating ITE toolkit
+ extensions, which is described in <a class="xref" href="../toolkitExtension/toolkitExtension.html" title="Chapter 3. Creating toolkit extensions for custom UI widgets">Chapter 3, <i>Creating toolkit extensions for custom UI widgets</i></a>. In this
+ chapter you will find also a short description of the extension examples.
+ </p>
+<p>Information how to write an extension for GEF can be found in <a class="xref" href="../gefToolkitExtension/creating-gef-toolkit-extensions.html" title="Chapter 4. Creating GEF toolkit extensions">Chapter 4, <i>Creating GEF toolkit extensions</i></a>.</p>
+<p>Last but not least <a class="xref" href="../functions/functions.html" title="Chapter 5. Creating ITE functions">Chapter 5, <i>Creating ITE functions</i></a> describes how to create a
+ custom ITE function, which can be used in tests.</p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/keyboardLayout/keyboardLayout.html b/documentation/developerManual/keyboardLayout/keyboardLayout.html
new file mode 100644
index 0000000..c861a28
--- /dev/null
+++ b/documentation/developerManual/keyboardLayout/keyboardLayout.html
@@ -0,0 +1,88 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter 6. Adding keyboard layout files</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="../index.html" title="Jubula Developer Manual">
+<link rel="prev" href="../functions/functions.html" title="Chapter 5. Creating ITE functions">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">Chapter 6. Adding keyboard layout files</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="../functions/functions.html">Prev</a> </td>
+<th width="60%" align="center"> </th>
+<td width="20%" align="right"> </td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-node">Adding keyboard layout files</span>
+</div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="keyboardLayout"></a>Chapter 6. Adding keyboard layout files</h1></div></div></div>
+<p>
+ For SWT and RCP AUTs, you need to define a keyboard layouts for the
+ AUT (i.e. which keyboard layout is set for the system on which the AUT
+ runs).
+ </p>
+<p>
+ The keyboard layouts for German (Germany) and English (US) are already
+ present. If you want to use another keyboard layout, follow the
+ instructions in the next section to create one.
+ </p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>
+ The name of the file must be in the following format:<br xmlns:d="http://docbook.org/ns/docbook">
+ keyboardmapping_<language>_<COUNTRY>.properties<br xmlns:d="http://docbook.org/ns/docbook">
+ e.g. for US English: keyboardmapping_en_US.properties
+ </p></li>
+<li class="listitem"><p>
+ In the file, enter the codes for all characters which require you
+ to press a modifier key.
+ </p></li>
+<li class="listitem"><p>
+ The format for these codes is:<br xmlns:d="http://docbook.org/ns/docbook">
+ <Character>=<Modifier>+<Character without modifier><br xmlns:d="http://docbook.org/ns/docbook">
+ e.g. for the @ character: @=shift+2
+ </p></li>
+<li class="listitem"><p>
+ The following symbols must be escaped with a backslash:<br xmlns:d="http://docbook.org/ns/docbook">
+ <code class="literal">! = : \ ,</code><br xmlns:d="http://docbook.org/ns/docbook">
+ e.g. <code class="literal">\!=shift+1</code> for !
+ </p></li>
+<li class="listitem"><p>
+ There are pictures of various keyboards on the following website:<br xmlns:d="http://docbook.org/ns/docbook">
+ <span class="emphasis"><em>http://www.uni-regensburg.de/EDV/Misc/KeyBoards/</em></span>
+ </p></li>
+<li class="listitem">
+<p>
+ To add the keyboard layout file, you must create a fragment containing your newly added keyboard layout file(s). The host plugin for the fragment is:<br xmlns:d="http://docbook.org/ns/docbook">
+ <span class="emphasis"><em>org.eclipse.jubula.client.core</em></span><br xmlns:d="http://docbook.org/ns/docbook">
+ The path within the fragment must be:<br xmlns:d="http://docbook.org/ns/docbook">
+ <span class="emphasis"><em>resources/keyboard_mapping/<name>.properties</em></span>
+ </p>
+<p xmlns:d="http://docbook.org/ns/docbook"><table>
+<colgroup>
+<col>
+<col>
+</colgroup>
+<tbody><tr>
+<td><img align="bottom" width="100" height="91" src="../images/img2.jpg"></td>
+<td class="topbotline"><span class="strong"><strong>If you name the file with the locale code, then the keyboard layout will be displayed in plain text in the AUT configuration dialog.</strong></span></td>
+</tr></tbody>
+</table></p>
+</li>
+</ol></div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/toolkitExtension/creating-the-fragment.html b/documentation/developerManual/toolkitExtension/creating-the-fragment.html
new file mode 100644
index 0000000..80c27ca
--- /dev/null
+++ b/documentation/developerManual/toolkitExtension/creating-the-fragment.html
@@ -0,0 +1,248 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.3.1. Creating the fragment</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="remoteControlExtension.html" title="3.3. Remote control extension">
+<link rel="prev" href="remoteControlExtension.html" title="3.3. Remote control extension">
+<link rel="next" href="deploying-the-fragment.html" title="3.3.2. Deploying the fragment">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">3.3.1. Creating the fragment</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="remoteControlExtension.html">Prev</a> </td>
+<th width="60%" align="center">3.3. Remote control extension</th>
+<td width="20%" align="right"> <a accesskey="n" href="deploying-the-fragment.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="toolkitExtension.html">Creating toolkit extensions for custom UI widgets</a></span> > <span class="breadcrumb-link"><a href="remoteControlExtension.html">Remote control extension</a></span> > <span class="breadcrumb-node">Creating the fragment</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="creating-the-fragment"></a>3.3.1. Creating the fragment</h3></div></div></div>
+<p>
+ The following steps have to be done to extend the remote
+ control:
+ </p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>
+ Reference the zip-file<br xmlns:d="http://docbook.org/ns/docbook">
+ <span class="input">development/org.eclipse.jubula.site.zip</span><br xmlns:d="http://docbook.org/ns/docbook">
+ as a <span class="strong"><strong>Software Site</strong></span> in your <span class="strong"><strong>Target Platform</strong></span>. Verify while adding the software site, that the check box <span class="strong"><strong>Include required software</strong></span> is not checked. This software site also includes the Java documention of the source code.
+ </p></li>
+<li class="listitem"><p>
+ Set the installed software site as your target platform.
+ </p></li>
+<li class="listitem">
+<p>
+ Create a fragment project with one of the following IDs as
+ host:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ <span class="input">org.eclipse.jubula.rc.swing</span><br xmlns:d="http://docbook.org/ns/docbook">
+ for extending Swing support.
+ </p></li>
+<li class="listitem"><p>
+ <span class="input">org.eclipse.jubula.rc.swt</span><br xmlns:d="http://docbook.org/ns/docbook">
+ for extending SWT support without RCP environment.
+ </p></li>
+<li class="listitem"><p>
+ <span class="input">org.eclipse.jubula.rc.rcp.swt</span><br xmlns:d="http://docbook.org/ns/docbook">
+ for extending SWT support in Eclipse 3.x and 4.x (including compatibility layer).
+ </p></li>
+<li class="listitem"><p>
+ <span class="input">org.eclipse.jubula.rc.rcp.e3.swt</span><br xmlns:d="http://docbook.org/ns/docbook">
+ for extending GEF support in Eclipse 3.x (without compatibility layer).
+ </p></li>
+<li class="listitem"><p>
+ <span class="input">org.eclipse.jubula.rc.javafx</span><br xmlns:d="http://docbook.org/ns/docbook">
+ for extending JavaFX support.
+ </p></li>
+</ul></div>
+</li>
+<li class="listitem"><p>
+ Write your own adapter and Tester Classes.
+ </p></li>
+</ol></div>
+<p xmlns:d="http://docbook.org/ns/docbook"><table>
+<colgroup>
+<col>
+<col>
+</colgroup>
+<tbody><tr>
+<td><img align="bottom" width="100" height="91" src="../images/img2.jpg"></td>
+<td class="topbotline"><span class="strong"><strong>If you are writing an extension for the JavaFX
+ toolkit, make sure that your adapter and Tester Classes really
+ get compiled with Java 8 and the Bundle-Required Execution Environment
+ is also set to Java 8.
+ </strong></span></td>
+</tr></tbody>
+</table></p>
+<p>
+ Adapters are used for all supported toolkits, i.e. Swing, SWT,
+ GEF, RCP and JavaFX. They wrap and specify graphic components in
+ a form we need for our Tester Classes. You can write your own
+ adapter or reuse our existing adapters. We recommend reusing our
+ adapters to take advantage of the already existing code.
+ </p>
+<p>
+ Before we have a look at the remote control extension examples
+ in <a class="xref" href="extensionExamples.html" title="3.4. ITE and remote control extension examples">Section 3.4, “ITE and remote control extension examples”</a>, we describe in general how
+ to create an adapter and Tester Classes.
+ </p>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="creating-an-adapter"></a>3.3.1.1. Creating an adapter</h4></div></div></div>
+<p>
+ To use an adapter you have to implement the interface
+ <span class="input">IAdapterFactory</span>, which is defined in the package named
+ <span class="emphasis"><em>org.eclipse.jubula.rc.common.adaptable</em></span>.
+
+ It is necessary that the implementation of this interface resists in a package named
+ <span class="emphasis"><em>org.eclipse.jubula.ext.rc.common.adapter</em></span>.
+ The package naming is important for the remote control extension, because adapters can only be found if they are located in a package with the mentioned name.
+ </p>
+<p>
+ In order to support your own components, the targeted type must be an instance of <span class="input">IComponent</span>, which is defined in the package named
+ <span class="emphasis"><em>org.eclipse.jubula.rc.common.tester.adapter.interfaces</em></span>.
+ This targeted type can be used for text components. If you want to support your own graphical component, you should at least use the interface <span class="input">IWidgetComponent</span> as the targeted type, which is a child of <span class="input">IComponent</span>. Both interfaces are defined in the same package.
+ </p>
+<p>
+ For Swing, SWT and JavaFX there are also specific implementations of different adapters in the following packages, which can be used for your own component:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.jubula.rc.swing.tester.adapter</em></span>
+ </p></li>
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.jubula.rc.swt.tester.adapter</em></span>
+ </p></li>
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.jubula.rc.javafx.tester.adapter</em></span>
+ </p></li>
+</ul></div>
+<p>
+ </p>
+<p>
+ Now we know how to create an own adapter in general. The next
+ step is to implement one or more Tester Class.
+ </p>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="creating-a-tester-class"></a>3.3.1.2. Creating a Tester Class</h4></div></div></div>
+<p>
+ The functionally important aspect of a Tester Class is that it
+ contains public methods for the test actions, which will
+ appear in the client. These methods are linked to testable
+ actions within a user-defined ITE toolkit plug-in.
+ </p>
+<p>
+ Each ITE toolkit extension provides an XML configuration file,
+ which defines the available methods with parameters, as well
+ as information for string externalization. Reflection is used
+ to call these methods. For this reason, the signature of a
+ defined method including its name, and the ordered parameter
+ types are important for the remote control extension.
+ </p>
+<p>
+ You can write your own Tester Classes, but if you only want to support a new component with existing actions, you could use one of our existing Tester Classes, which you can find in the package named
+ <span class="emphasis"><em>org.eclipse.jubula.rc.common.tester</em></span>.
+ For Swing, SWT and JavaFX there are also specific implementations in the following packages:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.jubula.rc.swing.tester</em></span>
+ </p></li>
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.jubula.rc.swt.tester</em></span>
+ </p></li>
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.jubula.rc.javafx.tester</em></span>
+ </p></li>
+</ul></div>
+<p>
+ </p>
+<p>
+ Please take the following guidelines into consideration for
+ creating Tester Classes:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ The class must not reside within the namespace / package of other classes of the ITE / RC part. If however this should be necessary you can safely use the package prefix <span class="emphasis"><em>org.eclipse.jubula.ext.</em></span>.
+ </p></li>
+<li class="listitem"><p>
+ The class must be compatible with <span class="emphasis"><em>Java 1.5</em></span>.
+ </p></li>
+<li class="listitem">
+<p>
+ It must either
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
+<li class="listitem"><p>
+ implement the interface <span class="input">ITester</span> defined in the package named<br xmlns:d="http://docbook.org/ns/docbook">
+ <span class="emphasis"><em>org.eclipse.jubula.rc.common.tester.interfaces</em></span>,
+ </p></li>
+<li class="listitem"><p>
+ or extend the abstract class <span class="input">AbstractUITester</span> defined in the package named<br xmlns:d="http://docbook.org/ns/docbook">
+ <span class="emphasis"><em>org.eclipse.jubula.rc.common.tester</em></span>.
+ </p></li>
+</ul></div>
+</li>
+<li class="listitem"><p>
+ The component must provide
+ <span class="strong"><strong>public</strong></span> methods for all
+ actions declared by the XML configuration file of the
+ corresponding ITE toolkit extension.
+ </p></li>
+<li class="listitem"><p>
+ Each method that implements an action must throw a
+ <span class="input">StepExecutionException</span> defined in the
+ package named <span class="emphasis"><em>org.eclipse.jubula.rc.common.exception</em></span>
+ to notify the ITE if the execution of the action has failed.
+ </p></li>
+</ul></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="creating-an-container-adapter"></a>3.3.1.3. Creating an container adapter</h4></div></div></div>
+<p>
+ This is a JavaFX exclusive way to extend the functionality of Jubula. You
+ can use this extension mechanism to make components "mappable" that are
+ normally not, e.g. components which are part of the skin of a control.
+ With the container extension mechanism you are able to add the possibility
+ of mapping such components. But to keep the user experience in the
+ object mapping like it is designed, such an extension has to be very
+ specific.
+ </p>
+<p>
+ The approach is very similar to creating an adapter. Just create an
+ Adapter Factory and an Adapter Class like it is described in the
+ corresponding chapter. You have to create this Adapter Class for the type
+ of the direct parent node from the component which you wish to map to declare
+ it to be a container. For example, if you want to map some content of a cell
+ in a ListView, the type would be ListCell.
+ </p>
+<p>
+ Additionally, your Adapter Class has to implement the interface
+ <span class="emphasis"><em>IContainerAdapter</em></span>. You have to implement the method
+ <span class="emphasis"><em>getContent</em></span> and return a list of the components which
+ you wish to map.
+ </p>
+</div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/toolkitExtension/creating-the-toolkit-plug-in.html b/documentation/developerManual/toolkitExtension/creating-the-toolkit-plug-in.html
new file mode 100644
index 0000000..21b18dd
--- /dev/null
+++ b/documentation/developerManual/toolkitExtension/creating-the-toolkit-plug-in.html
@@ -0,0 +1,124 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.2.1. Creating the toolkit plug-in</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="iteExtension.html" title="3.2. ITE extension">
+<link rel="prev" href="iteExtension.html" title="3.2. ITE extension">
+<link rel="next" href="deploying-the-toolkit-plug-in.html" title="3.2.2. Deploying the toolkit plug-in">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">3.2.1. Creating the toolkit plug-in</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="iteExtension.html">Prev</a> </td>
+<th width="60%" align="center">3.2. ITE extension</th>
+<td width="20%" align="right"> <a accesskey="n" href="deploying-the-toolkit-plug-in.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="toolkitExtension.html">Creating toolkit extensions for custom UI widgets</a></span> > <span class="breadcrumb-link"><a href="iteExtension.html">ITE extension</a></span> > <span class="breadcrumb-node">Creating the toolkit plug-in</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="creating-the-toolkit-plug-in"></a>3.2.1. Creating the toolkit plug-in</h3></div></div></div>
+<p>
+ The following steps have to be done to extend the ITE toolkit:
+ </p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>
+ Create a <span class="strong"><strong>Plug-in Project</strong></span>
+ for your toolkit project.
+ </p></li>
+<li class="listitem"><p>
+ Create a <span class="strong"><strong>Feature Project</strong></span>
+ referencing your toolkit project from the previous step for
+ an easier installation into the ITE.
+ </p></li>
+<li class="listitem">
+<p>
+ Set the features
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.rcp</em></span> and
+ </p></li>
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.jubula.feature</em></span>
+ </p></li>
+</ul></div>
+<p>
+ from the installation folder as your
+ <span class="strong"><strong>Target Platform</strong></span> in the
+ workspace preferences. Information on configuring the target
+ platform can be found in Eclipse’s online Help under
+ <span class="emphasis"><em>Plug-in Development Environment Guide > Tools
+ > Preferences > Target Plug-ins</em></span>.
+ </p>
+</li>
+<li class="listitem">
+<p>
+ Add the following dependencies to your toolkit project:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.jubula.tools</em></span> and
+ </p></li>
+<li class="listitem"><p>
+ <span class="emphasis"><em>org.eclipse.jubula.toolkit.common</em></span>
+ </p></li>
+</ul></div>
+</li>
+<li class="listitem"><p>
+ Use and configure the following extension point in your toolkit project:
+ <span class="emphasis"><em>org.eclipse.jubula.toolkit.common.toolkitsupport</em></span>.
+ </p></li>
+<li class="listitem"><p>
+ Implement the interface <span class="input">IToolkitProvider</span>
+ from the extension point of the previous step.
+ </p></li>
+<li class="listitem">
+<p>
+ Create the definition of your own toolkit in the file
+ <span class="input">ComponentExtension.xml</span> by choosing one or more of the following possibilities:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ Extend existing toolkit components with new actions,
+ </p></li>
+<li class="listitem"><p>
+ derive new components from existing toolkit components, or
+ </p></li>
+<li class="listitem"><p>
+ define a new toolkit component.
+ </p></li>
+</ul></div>
+</li>
+<li class="listitem"><p>
+ Manage the i18n keys in the properties file.
+ </p></li>
+</ol></div>
+<p>
+ You will find projects in zip-files as a showcase for steps 1-8, which are located in the directory
+ <span class="input">examples/development/extension/src</span>.
+ Each zip-file contains an example for a specific toolkit, e.g. a Swing example extends the <span class="input">JSlider</span> component.
+ </p>
+<p>
+ These example projects can be simply imported into your Eclipse
+ workspace. Set the target after importing the projects as
+ described in step 3. All other steps have already been done in
+ the examples.
+ </p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/toolkitExtension/deploying-the-fragment.html b/documentation/developerManual/toolkitExtension/deploying-the-fragment.html
new file mode 100644
index 0000000..684b685
--- /dev/null
+++ b/documentation/developerManual/toolkitExtension/deploying-the-fragment.html
@@ -0,0 +1,135 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.3.2. Deploying the fragment</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="remoteControlExtension.html" title="3.3. Remote control extension">
+<link rel="prev" href="creating-the-fragment.html" title="3.3.1. Creating the fragment">
+<link rel="next" href="extensionExamples.html" title="3.4. ITE and remote control extension examples">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">3.3.2. Deploying the fragment</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="creating-the-fragment.html">Prev</a> </td>
+<th width="60%" align="center">3.3. Remote control extension</th>
+<td width="20%" align="right"> <a accesskey="n" href="extensionExamples.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="toolkitExtension.html">Creating toolkit extensions for custom UI widgets</a></span> > <span class="breadcrumb-link"><a href="remoteControlExtension.html">Remote control extension</a></span> > <span class="breadcrumb-node">Deploying the fragment</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="deploying-the-fragment"></a>3.3.2. Deploying the fragment</h3></div></div></div>
+<p>
+ Once you have written your fragment, you still need to make all
+ components aware of its presence. This is done by exporting the
+ fragment and deploying it into the remote control.
+ </p>
+<p>
+ There are different ways for installing your fragment into the
+ remote control, depending on the AUT Agent used and the specific
+ AUT. You are free to use either the embedded AUT Agent or the
+ standalone AUT Agent. Also your AUT can be based upon the OSGi
+ framework or not. The following table shows an overview, where
+ to deploy your fragment:
+ </p>
+<div class="informaltable"><table border="1">
+<colgroup>
+<col align="center">
+<col align="center">
+<col align="center">
+</colgroup>
+<tbody>
+<tr>
+<td align="center">
+
+ </td>
+<td align="center">
+ without OSGi<br xmlns:d="http://docbook.org/ns/docbook">(Swing, SWT, JavaFX)
+ </td>
+<td align="center">
+ with OSGi<br xmlns:d="http://docbook.org/ns/docbook">(RCP, GEF)
+ </td>
+</tr>
+<tr>
+<td align="center">
+ embedded<br xmlns:d="http://docbook.org/ns/docbook">AUT Agent
+ </td>
+<td align="center">
+ ITE
+ </td>
+<td rowspan="2" align="center">
+ AUT
+ </td>
+</tr>
+<tr>
+<td align="center">
+ standalone<br xmlns:d="http://docbook.org/ns/docbook">AUT agent
+ </td>
+<td align="center">
+ standalone<br xmlns:d="http://docbook.org/ns/docbook">AUT agent
+ </td>
+</tr>
+</tbody>
+</table></div>
+<p>
+ It shows, in which case you usually deploy your fragment into
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ the ITE with a feature including your fragment,
+ </p></li>
+<li class="listitem"><p>
+ the standalone AUT Agent by adding your fragment to its
+ configuration, or
+ </p></li>
+<li class="listitem"><p>
+ the AUT with a feature including your fragment.
+ </p></li>
+</ul></div>
+<p>
+ The configuration of the standalone AUT Agent can be done by modifying the file
+ <span class="input">server/configuration/config.ini</span>.
+ There you have to append <span class="input">,fragment_id</span> at the end of the line starting with
+ <span class="input">osgi.bundles=</span>. Make sure that the bundles are comma-separated. It is also necessary
+ to add the argument <span class="input">-clean</span> in the file <span class="input">server/autagent.ini</span>,
+ when deploying a new version with the same fragment ID. Apart from the deploying methods mentioned, it is also possible to install
+ your fragment using a p2 repository or the OSGi console.
+ </p>
+<p xmlns:d="http://docbook.org/ns/docbook"><table>
+<colgroup>
+<col>
+<col>
+</colgroup>
+<tbody><tr>
+<td><img align="bottom" width="100" height="91" src="../images/img2.jpg"></td>
+<td class="topbotline"><span class="strong"><strong>If you have deployed fragments for the JavaFX RC
+ bundle, you have to keep in mind that if you are executing the ITE
+ with Java 7 the RC bundle is not active and therefore the wiring for
+ the fragments has not been done by the OSGI framework. The current
+ workaround in Jubula is that all the fragments for the JavaFX RC
+ bundle are added, without taking any version ranges from the fragments
+ into account.
+ </strong></span></td>
+</tr></tbody>
+</table></p>
+<p>
+ You should be able to test your new component once you have
+ installed the toolkit feature into the ITE and the fragment as
+ described below.
+ </p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/toolkitExtension/deploying-the-toolkit-plug-in.html b/documentation/developerManual/toolkitExtension/deploying-the-toolkit-plug-in.html
new file mode 100644
index 0000000..0edd0fd
--- /dev/null
+++ b/documentation/developerManual/toolkitExtension/deploying-the-toolkit-plug-in.html
@@ -0,0 +1,128 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.2.2. Deploying the toolkit plug-in</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="iteExtension.html" title="3.2. ITE extension">
+<link rel="prev" href="creating-the-toolkit-plug-in.html" title="3.2.1. Creating the toolkit plug-in">
+<link rel="next" href="remoteControlExtension.html" title="3.3. Remote control extension">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">3.2.2. Deploying the toolkit plug-in</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="creating-the-toolkit-plug-in.html">Prev</a> </td>
+<th width="60%" align="center">3.2. ITE extension</th>
+<td width="20%" align="right"> <a accesskey="n" href="remoteControlExtension.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="toolkitExtension.html">Creating toolkit extensions for custom UI widgets</a></span> > <span class="breadcrumb-link"><a href="iteExtension.html">ITE extension</a></span> > <span class="breadcrumb-node">Deploying the toolkit plug-in</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="deploying-the-toolkit-plug-in"></a>3.2.2. Deploying the toolkit plug-in</h3></div></div></div>
+<p>
+ Once the toolkit feature has been created, it must be deployed
+ in the ITE. The toolkit feature must be exported to an update
+ site and then installed via this update site into the ITE. If
+ you want to execute tests on your new components via testexec,
+ it is important that you have write access to the ITE so that
+ the installed feature can be accessed during test execution.
+ </p>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="create-an-update-site-for-the-toolkit-feature"></a>3.2.2.1. Create an update site for the toolkit feature</h4></div></div></div>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>
+ Create an <span class="strong"><strong>Update Site
+ Project</strong></span>.
+ </p></li>
+<li class="listitem"><p>
+ Add a category to your update site that defines its
+ <span class="emphasis"><em>ID</em></span> and <span class="emphasis"><em>Name</em></span>.
+ </p></li>
+<li class="listitem"><p>
+ Add your toolkit feature to the category created in the
+ previous step.
+ </p></li>
+<li class="listitem"><p>
+ Build the created toolkit update site. The directory of
+ the toolkit update site project serves as an update site,
+ which is later used to install your toolkit feature into
+ the ITE. Remember to build and then synchronize this
+ update site if you have changed the toolkit feature.
+ </p></li>
+</ol></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="install-the-toolkit-feature-from-the-update-site"></a>3.2.2.2. Install the toolkit feature from the update site</h4></div></div></div>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>
+ Start the ITE and select from the main menu
+ <span class="menupath">Help</span>--><span class="menupath">Install new software...</span>.
+ </p></li>
+<li class="listitem"><p>
+ Click the ”<span class="emphasis"><em>Add...</em></span>” button in the
+ <span class="emphasis"><em>Install</em></span> dialog that appears.
+ </p></li>
+<li class="listitem"><p>
+ Click the ”<span class="emphasis"><em>Local...</em></span>” button in the
+ <span class="emphasis"><em>Add Repository</em></span> dialog that appears
+ </p></li>
+<li class="listitem"><p>
+ Navigate to the directory that contains your update site
+ and confirm your selection.
+ </p></li>
+<li class="listitem"><p>
+ Click ”<span class="emphasis"><em>OK</em></span>” to exit the <span class="emphasis"><em>Add
+ Repository</em></span> dialog. The active dialog should now
+ be <span class="emphasis"><em>Install</em></span>.
+ </p></li>
+<li class="listitem"><p>
+ Ensure that the check box named <span class="emphasis"><em>Group items by
+ category</em></span> is deselected. Your feature should be
+ visible in the central table of the dialog.
+ </p></li>
+<li class="listitem"><p>
+ Ensure that the check box next to your feature is selected
+ and click ”<span class="emphasis"><em>Next</em></span>”.
+ </p></li>
+<li class="listitem"><p>
+ Confirm the <span class="emphasis"><em>Installation Details</em></span> by
+ clicking the ”<span class="emphasis"><em>Next</em></span>” button again.
+ </p></li>
+<li class="listitem"><p>
+ Accept the license agreement terms and click
+ ”<span class="emphasis"><em>Finish</em></span>”.
+ </p></li>
+<li class="listitem"><p>
+ A warning dialog may appear to warn you are installing
+ unsigned content. Click ”<span class="emphasis"><em>OK</em></span>” in this
+ dialog if the feature comes from a trusted source. This
+ should be the case as long as you install your own
+ feature. Then the installation process begins.
+ </p></li>
+<li class="listitem"><p>
+ Click the ”<span class="emphasis"><em>Restart Now</em></span>” button to
+ perform a restart, when a dialog appears to prompt the
+ restart that will safely finish the update / installation.
+ After the restart your ITE toolkit extension feature is
+ installed.
+ </p></li>
+</ol></div>
+</div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/toolkitExtension/extensionExamples.html b/documentation/developerManual/toolkitExtension/extensionExamples.html
new file mode 100644
index 0000000..4768faa
--- /dev/null
+++ b/documentation/developerManual/toolkitExtension/extensionExamples.html
@@ -0,0 +1,88 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.4. ITE and remote control extension examples</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="toolkitExtension.html" title="Chapter 3. Creating toolkit extensions for custom UI widgets">
+<link rel="prev" href="deploying-the-fragment.html" title="3.3.2. Deploying the fragment">
+<link rel="next" href="../gefToolkitExtension/creating-gef-toolkit-extensions.html" title="Chapter 4. Creating GEF toolkit extensions">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">3.4. ITE and remote control extension examples</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="deploying-the-fragment.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 3. Creating toolkit extensions for custom UI widgets</th>
+<td width="20%" align="right"> <a accesskey="n" href="../gefToolkitExtension/creating-gef-toolkit-extensions.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="toolkitExtension.html">Creating toolkit extensions for custom UI widgets</a></span> > <span class="breadcrumb-node">ITE and remote control extension examples</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="extensionExamples"></a>3.4. ITE and remote control extension examples</h2></div></div></div>
+<p>
+ In the installation, there are source code examples for extending supported toolkits.
+ The examples can be found in the directory
+ <span class="input">examples/development/extension</span>,
+ which contains the following sub-folders:
+ </p>
+<div class="variablelist"><dl class="variablelist">
+<dt><span class="term">
+ src
+ </span></dt>
+<dd>
+<p>
+ Contains some zip-files with example source code projects,
+ which can be imported by Eclipse:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ <span class="input">RCPExtension.zip</span><br xmlns:d="http://docbook.org/ns/docbook">
+ An extension supporting <span class="input">Group</span> for SWT including client
+ and remote control projects. After deploying these projects you should be able to test the
+ <span class="input">Group</span> in RCP applications.
+ </p></li>
+<li class="listitem"><p>
+ <span class="input">SwingAUT.zip</span><br xmlns:d="http://docbook.org/ns/docbook">
+ An AUT using <span class="input">JSlider</span> from Swing.
+ </p></li>
+<li class="listitem"><p>
+ <span class="input">SwingExtension.zip</span><br xmlns:d="http://docbook.org/ns/docbook">
+ The extension supporting <span class="input">JSlider</span> for Swing including client
+ and remote control projects. After deploying these projects you should be able to test the
+ <span class="input">JSlider</span> in the Swing example AUT.
+ </p></li>
+<li class="listitem"><p>
+ <span class="input">SwingRendererExtension.zip</span><br xmlns:d="http://docbook.org/ns/docbook">
+ A remote control extension supporting a custom graphics component for
+ Swing.
+ </p></li>
+</ul></div>
+</dd>
+<dt><span class="term">
+ AUT
+ </span></dt>
+<dd><p>
+ Contains the binary file <span class="input">JSlider.jar</span>, which
+ is a simple example AUT using the normally unsupported
+ component <span class="input">JSlider</span>. After installing the
+ <span class="input">JSlider</span> example extension from the
+ <span class="strong"><strong>src</strong></span> folder, you will be
+ able to test this new component.
+ </p></dd>
+</dl></div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/toolkitExtension/iteExtension.html b/documentation/developerManual/toolkitExtension/iteExtension.html
new file mode 100644
index 0000000..7505bac
--- /dev/null
+++ b/documentation/developerManual/toolkitExtension/iteExtension.html
@@ -0,0 +1,50 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.2. ITE extension</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="toolkitExtension.html" title="Chapter 3. Creating toolkit extensions for custom UI widgets">
+<link rel="prev" href="requirements.html" title="3.1. Requirements">
+<link rel="next" href="creating-the-toolkit-plug-in.html" title="3.2.1. Creating the toolkit plug-in">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">3.2. ITE extension</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="requirements.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 3. Creating toolkit extensions for custom UI widgets</th>
+<td width="20%" align="right"> <a accesskey="n" href="creating-the-toolkit-plug-in.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="toolkitExtension.html">Creating toolkit extensions for custom UI widgets</a></span> > <span class="breadcrumb-node">ITE extension</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="iteExtension"></a>3.2. ITE extension</h2></div></div></div>
+<div class="toc"><dl class="toc">
+<dt><span class="section"><a href="creating-the-toolkit-plug-in.html">3.2.1. Creating the toolkit plug-in</a></span></dt>
+<dt><span class="section"><a href="deploying-the-toolkit-plug-in.html">3.2.2. Deploying the toolkit plug-in</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="deploying-the-toolkit-plug-in.html#create-an-update-site-for-the-toolkit-feature">3.2.2.1. Create an update site for the toolkit feature</a></span></dt>
+<dt><span class="section"><a href="deploying-the-toolkit-plug-in.html#install-the-toolkit-feature-from-the-update-site">3.2.2.2. Install the toolkit feature from the update site</a></span></dt>
+</dl></dd>
+</dl></div>
+<p>
+ This section shows you how to develop the ITE toolkit extension.
+ We describe the steps to create the toolkit plug-in and how it can
+ be exported.
+ </p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/toolkitExtension/remoteControlExtension.html b/documentation/developerManual/toolkitExtension/remoteControlExtension.html
new file mode 100644
index 0000000..458cf80
--- /dev/null
+++ b/documentation/developerManual/toolkitExtension/remoteControlExtension.html
@@ -0,0 +1,56 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.3. Remote control extension</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="toolkitExtension.html" title="Chapter 3. Creating toolkit extensions for custom UI widgets">
+<link rel="prev" href="deploying-the-toolkit-plug-in.html" title="3.2.2. Deploying the toolkit plug-in">
+<link rel="next" href="creating-the-fragment.html" title="3.3.1. Creating the fragment">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">3.3. Remote control extension</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="deploying-the-toolkit-plug-in.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 3. Creating toolkit extensions for custom UI widgets</th>
+<td width="20%" align="right"> <a accesskey="n" href="creating-the-fragment.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="toolkitExtension.html">Creating toolkit extensions for custom UI widgets</a></span> > <span class="breadcrumb-node">Remote control extension</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="remoteControlExtension"></a>3.3. Remote control extension</h2></div></div></div>
+<div class="toc"><dl class="toc">
+<dt><span class="section"><a href="creating-the-fragment.html">3.3.1. Creating the fragment</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="creating-the-fragment.html#creating-an-adapter">3.3.1.1. Creating an adapter</a></span></dt>
+<dt><span class="section"><a href="creating-the-fragment.html#creating-a-tester-class">3.3.1.2. Creating a Tester Class</a></span></dt>
+<dt><span class="section"><a href="creating-the-fragment.html#creating-an-container-adapter">3.3.1.3. Creating an container adapter</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="deploying-the-fragment.html">3.3.2. Deploying the fragment</a></span></dt>
+</dl></div>
+<p>
+ AUTs are controlled by the remote control called AUT Agent. The
+ ITE can also execute the remote control if the embedded AUT Agent
+ is used. Otherwise, the normal AUT Agent runs as a remote control
+ in a separate process independently from the ITE. For each
+ supported component known, a Tester Class must exist. This class
+ implements the test actions that can be carried out on the
+ component. You need to write a fragment for your component, which
+ contains the Tester Class and a corresponding adapter factory.
+ </p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/toolkitExtension/requirements.html b/documentation/developerManual/toolkitExtension/requirements.html
new file mode 100644
index 0000000..b04f47f
--- /dev/null
+++ b/documentation/developerManual/toolkitExtension/requirements.html
@@ -0,0 +1,57 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.1. Requirements</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="toolkitExtension.html" title="Chapter 3. Creating toolkit extensions for custom UI widgets">
+<link rel="prev" href="toolkitExtension.html" title="Chapter 3. Creating toolkit extensions for custom UI widgets">
+<link rel="next" href="iteExtension.html" title="3.2. ITE extension">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">3.1. Requirements</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="toolkitExtension.html">Prev</a> </td>
+<th width="60%" align="center">Chapter 3. Creating toolkit extensions for custom UI widgets</th>
+<td width="20%" align="right"> <a accesskey="n" href="iteExtension.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="toolkitExtension.html">Creating toolkit extensions for custom UI widgets</a></span> > <span class="breadcrumb-node">Requirements</span>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="requirements"></a>3.1. Requirements</h2></div></div></div>
+<p>
+ To create your own ITE toolkit and remote control extensions, you
+ need:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ <span class="strong"><strong>GUI</strong></span><span class="emphasis"><em>dancer</em></span>
+ 7.0 / Jubula 2.0 or later
+ </p></li>
+<li class="listitem"><p>
+ Eclipse 3.4 or later (4.4 recommended)
+ </p></li>
+<li class="listitem"><p>
+ JDK 5.0
+ </p></li>
+<li class="listitem"><p>
+ Full write access in installation directory for deploying the
+ extension.
+ </p></li>
+</ul></div>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/documentation/developerManual/toolkitExtension/toolkitExtension.html b/documentation/developerManual/toolkitExtension/toolkitExtension.html
new file mode 100644
index 0000000..a769186
--- /dev/null
+++ b/documentation/developerManual/toolkitExtension/toolkitExtension.html
@@ -0,0 +1,110 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter 3. Creating toolkit extensions for custom UI widgets</title>
+<link rel="stylesheet" type="text/css" href="../../css/style.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="../index.html" title="Jubula Developer Manual">
+<link rel="up" href="../index.html" title="Jubula Developer Manual">
+<link rel="prev" href="../clientAPI/ch02s06.html" title="2.6. Sample setup of the API usage">
+<link rel="next" href="requirements.html" title="3.1. Requirements">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<div class="navheader">
+<table width="100%" summary="Navigation header">
+<tr><th colspan="3" align="center">Chapter 3. Creating toolkit extensions for custom UI widgets</th></tr>
+<tr>
+<td width="20%" align="left">
+<a accesskey="p" href="../clientAPI/ch02s06.html">Prev</a> </td>
+<th width="60%" align="center"> </th>
+<td width="20%" align="right"> <a accesskey="n" href="requirements.html">Next</a>
+</td>
+</tr>
+</table>
+<hr>
+</div>
+<div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs">
+<span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-node">Creating toolkit extensions for custom UI widgets</span>
+</div>
+<div class="chapter">
+<div class="titlepage"><div><div><h1 class="title">
+<a name="toolkitExtension"></a>Chapter 3. Creating toolkit extensions for custom UI widgets</h1></div></div></div>
+<div class="toc"><dl class="toc">
+<dt><span class="section"><a href="requirements.html">3.1. Requirements</a></span></dt>
+<dt><span class="section"><a href="iteExtension.html">3.2. ITE extension</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="creating-the-toolkit-plug-in.html">3.2.1. Creating the toolkit plug-in</a></span></dt>
+<dt><span class="section"><a href="deploying-the-toolkit-plug-in.html">3.2.2. Deploying the toolkit plug-in</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="deploying-the-toolkit-plug-in.html#create-an-update-site-for-the-toolkit-feature">3.2.2.1. Create an update site for the toolkit feature</a></span></dt>
+<dt><span class="section"><a href="deploying-the-toolkit-plug-in.html#install-the-toolkit-feature-from-the-update-site">3.2.2.2. Install the toolkit feature from the update site</a></span></dt>
+</dl></dd>
+</dl></dd>
+<dt><span class="section"><a href="remoteControlExtension.html">3.3. Remote control extension</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="creating-the-fragment.html">3.3.1. Creating the fragment</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="creating-the-fragment.html#creating-an-adapter">3.3.1.1. Creating an adapter</a></span></dt>
+<dt><span class="section"><a href="creating-the-fragment.html#creating-a-tester-class">3.3.1.2. Creating a Tester Class</a></span></dt>
+<dt><span class="section"><a href="creating-the-fragment.html#creating-an-container-adapter">3.3.1.3. Creating an container adapter</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="deploying-the-fragment.html">3.3.2. Deploying the fragment</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="extensionExamples.html">3.4. ITE and remote control extension examples</a></span></dt>
+</dl></div>
+<p>When developing graphical applications, it is often necessary or
+ convenient to alter or combine the functionality of existing toolkit
+ components, or even to write entirely new ones, as the requirements or concept
+ of the software may dictate. These new components generally cannot be tested
+ "out of the box", as the behavior of custom components cannot be predicted, or
+ they may deviate from established standards of "look and feel". In order to
+ overcome this limitation, there is an extension API, which you can use to be
+ able to test your custom components.</p>
+<p>The following sections describe the steps involved in writing
+ extensions.</p>
+<p>AUTs are started, controlled and observed using its remote control
+ component. In order for the AUT Agent to know how to control each element of a
+ GUI, we have outfitted the AUT Agent with a pluggable interface for graphic
+ components. An adapter factory containing one or more components must be
+ implemented for and deployed with the AUT. On the client side, each GUI
+ toolkit that the ITE supports is described in a toolkit plug-in.</p>
+<p>We have opened up an interface to our users to allow flexible
+ customizations. You can extend existing functionality, or provide support for
+ in-house graphic components by implementing your own
+ <span class="strong"><strong>Tester Classes.</strong></span></p>
+<p>
+ The following chapter describes the general steps to take for
+ creating an ITE toolkit extension with custom defined components and
+ actions. This chapter begins by listing the requirements followed by
+ showing the necessary steps for creating an ITE and remote control
+ extension. The ITE toolkit extension is described in <a class="xref" href="iteExtension.html" title="3.2. ITE extension">Section 3.2, “ITE extension”</a>
+ and the implementation for the remote control extension in <a class="xref" href="remoteControlExtension.html" title="3.3. Remote control extension">Section 3.3, “Remote control extension”</a>.
+ </p>
+<p>
+ Extension examples with source code can be found in the subdirectory
+ <span class="input">examples/development/extension/src/</span>
+ of the installation.
+ </p>
+<p>
+ In general you always have to extend two things:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+ The ITE toolkit extension – by writing your own <span class="strong"><strong>toolkit</strong></span> plug-in:
+ This will tell the ITE which new components and actions are available.
+ </p></li>
+<li class="listitem"><p>
+ The remote control extension – by writing your own <span class="strong"><strong>fragment</strong></span>:
+ This part actually performs the actions on the new components.
+ </p></li>
+</ul></div>
+<p>
+ In this chapter all used directory names are located in the
+ installation directory as long as nothing else is specified.
+ </p>
+</div>
+<br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook">
+<address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address>
+<br xmlns:d="http://docbook.org/ns/docbook">
+</body>
+</html>
diff --git a/new/_index.html b/new/_index.html
index 20cf90e..98264f6 100644
--- a/new/_index.html
+++ b/new/_index.html
@@ -66,7 +66,7 @@
<p>
We've created a whole new layer in the ITE that allows you to write functional UI tests via an official Java client API.
Detailed information of the architecture and how to start can be found in the
- <a href="http://testing.bredex.de/documentation-download.html" target="_blank">Developer Manual</a>.
+ <a href="http://www.eclipse.org/jubula/documentation/developerManual/index.html" target="_blank">Developer Manual</a>.
</p>
<p>
There are two blog entries <a href="http://www.bredex.de/blog_article_de/jubula-client-api.html" target="_blank">here</a> and
