Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarkus Tiede2011-03-03 09:24:04 +0000
committerMarkus Tiede2011-03-03 09:24:04 +0000
commite3dafc2c0cd69614bfbfcc9b4f773572228d5d0d (patch)
treea635e6340be0989bf060c3f291157c8c39e68910 /org.eclipse.jubula.documentation
parent5750a3f142bac5264a0cd5a3053dd64f4881769a (diff)
parentf25b5b4a519851c0f4798c594d7d5c2e75c1ac35 (diff)
downloadorg.eclipse.jubula.core-e3dafc2c0cd69614bfbfcc9b4f773572228d5d0d.tar.gz
org.eclipse.jubula.core-e3dafc2c0cd69614bfbfcc9b4f773572228d5d0d.tar.xz
org.eclipse.jubula.core-e3dafc2c0cd69614bfbfcc9b4f773572228d5d0d.zip
Merge branch 'master' of ssh://gatekeeper.bredex.de:2405/gitroot/jubula/org.eclipse.jubula.core
Diffstat (limited to 'org.eclipse.jubula.documentation')
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex1
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/ButtonComp/VerifySelected/param-IsSelected.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyEnabled/param-IsEnabled.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyExists/param-IsExisting.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyFocus/param-HasFocus.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Activate/action-Activate.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/CheckExistenceOfWindow/param-IsExisting.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/ExecuteCommand/param-RunLocal.tex6
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/KeyToogle/param-SelectKey.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Pause/action-Pause.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/TabbedPane/VerifySelectedTab/param-IsSelected.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/ToolItem/VerifyEnabled/param-IsEnabled.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyEnabled/param-IsEnabled.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyExists/param-IsExisting.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyFocus/param-HasFocus.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifySelected/param-IsSelected.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/AbstractButton/VerifySelected/param-IsSelected.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Activate/action-Activate.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/KeyToogle/param-SelectKey.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Pause/action-Pause.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/SelectValue/param-UseRegularExpression.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/VerifyContainsValue/param-Contains.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/SelectValues/param-UseRegularExpression.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/VerifyContainsValue/param-Contains.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/ExpandByTextPath/param-UseRegularExpression.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByIndexPathAtTextNode/param-UseRegularExpression.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByTextPathAtTextNode/param-UseRegularExpression.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/SelectByTextPath/param-UseRegularExpression.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyEnabled/param-IsEnabled.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyExists/param-IsExisting.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyFocus/param-HasFocus.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/Regex.tex76
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Action/SimpleMatch.tex26
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Constants/CONTENT.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Debugging/remoteDebugging.tex4
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Icons/CONTENT.tex66
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Icons/browser.tex18
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Icons/cases.tex21
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Icons/other.tex29
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Icons/parametericons.tex17
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Icons/problemviewicons.tex17
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Icons/statusbaricons.tex40
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Icons/toolbar.tex15
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Intro/intro.tex17
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Overview/comp.tex12
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Relative/relpaths.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/Shortcuts/CONTENT.tex2
-rw-r--r--org.eclipse.jubula.documentation/reference/en/tex/content.tex4
-rw-r--r--org.eclipse.jubula.documentation/releasenotes/en/tex/content.tex860
-rw-r--r--org.eclipse.jubula.documentation/releasenotes/en/tex/summary.tex0
50 files changed, 69 insertions, 1254 deletions
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex
index cf0fcd613..b3930adba 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex
@@ -177,3 +177,4 @@ For more details about individual tasks, read the \bxref{Concepts}
\gdhelpid{problemViewContextId}{Problem View}
\label{DBTool}
\input{Tasks/DBTool/CONTENT}
+
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/ButtonComp/VerifySelected/param-IsSelected.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/ButtonComp/VerifySelected/param-IsSelected.tex
index 4b37fa924..bab36ba1a 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/ButtonComp/VerifySelected/param-IsSelected.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/ButtonComp/VerifySelected/param-IsSelected.tex
@@ -1,7 +1,7 @@
% CAP description for Button/Check Box/Radio Button --> Verify
% Selected --> Selected
\begin{itemize}
-\item Set this parameter to \app{}efbooleantrue{} if you expect the button to be selected.
-\item Set this parameter to \app{}efbooleanfalse{} if you expect the button to \emph{not} be selected.
+\item Set this parameter to \gdrefbooleantrue{} if you expect the button to be selected.
+\item Set this parameter to \gdrefbooleanfalse{} if you expect the button to \emph{not} be selected.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyEnabled/param-IsEnabled.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyEnabled/param-IsEnabled.tex
index e316d9f6d..81826a947 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyEnabled/param-IsEnabled.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyEnabled/param-IsEnabled.tex
@@ -1,5 +1,5 @@
% CAP description for Graphics Component --> Verify Enabled --> Enabled
\begin{itemize}
\item Set this parameter to true if you expect the component to be enabled.
-\item Set this parameter to \app{}efbooleanfalse if you expect the component to be disabled.
+\item Set this parameter to \gdrefbooleanfalse if you expect the component to be disabled.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyExists/param-IsExisting.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyExists/param-IsExisting.tex
index d352d60fd..70c63d730 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyExists/param-IsExisting.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyExists/param-IsExisting.tex
@@ -2,5 +2,5 @@
%
\begin{itemize}
\item Set this parameter to true if you expect the component to exist.
-\item Set this parameter to \app{}efbooleanfalse if you do \emph{not} expect the component to exist.
+\item Set this parameter to \gdrefbooleanfalse if you do \emph{not} expect the component to exist.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyFocus/param-HasFocus.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyFocus/param-HasFocus.tex
index 46debffb2..ba3b46120 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyFocus/param-HasFocus.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Abstract/Widget/VerifyFocus/param-HasFocus.tex
@@ -1,5 +1,5 @@
% CAP description for Graphics Component --> Verify Focus --> Has Focus
\begin{itemize}
-\item Set this parameter to \app{}efbooleantrue{} if you expect the component to be in focus.
-\item Set this parameter to \app{}efbooleanfalse{} if you expect the component \emph{not} to be in focus.
+\item Set this parameter to \gdrefbooleantrue{} if you expect the component to be in focus.
+\item Set this parameter to \gdrefbooleanfalse{} if you expect the component \emph{not} to be in focus.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Activate/action-Activate.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Activate/action-Activate.tex
index 6db812b00..72d00ae3a 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Activate/action-Activate.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Activate/action-Activate.tex
@@ -1,7 +1,7 @@
% CAP description for Application --> Activate
\label{activate}
\begin{itemize}
-\item When the \app{} client and \gdagent are running on the same computer, you may need to bring the \gdaut{} into focus before a test can begin.
+\item When the \ite{} and \gdagent are running on the same computer, you may need to bring the \gdaut{} into focus before a test can begin.
\item Exactly how to \bxname{activate} the application can vary from one system to another.
\item This action offers various different ways of activating the application.
\item \app{} realises this action by clicking in the location indicated in the \bxname{activation method} parameter.
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/CheckExistenceOfWindow/param-IsExisting.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/CheckExistenceOfWindow/param-IsExisting.tex
index a78196971..5becd40ee 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/CheckExistenceOfWindow/param-IsExisting.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/CheckExistenceOfWindow/param-IsExisting.tex
@@ -1,5 +1,5 @@
% CAP description for Application --> Check Existence of Window --> Exists
\begin{itemize}
\item Set this parameter to true if you expect the window to exist.
-\item Set this parameter to \app{}efbooleanfalse if you do \emph{not} expect the window to exist.
+\item Set this parameter to false if you do \emph{not} expect the window to exist.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/ExecuteCommand/param-RunLocal.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/ExecuteCommand/param-RunLocal.tex
index 693699b25..63eca70bd 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/ExecuteCommand/param-RunLocal.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/ExecuteCommand/param-RunLocal.tex
@@ -1,9 +1,9 @@
% CAP description for Application --> Execute External Command --> Local
\begin{itemize}
-\item Use this parameter to define whether the command should be run locally (on the client machine, the same machin as \app{} is installed on) or remotely (on the machine where the \gdagent{} is installed, and the \gdaut{} is running.).
+\item Use this parameter to define whether the command should be run locally (on the same machine as the \ite{}, the same machine as \app{} is installed on) or remotely (on the machine where the \gdagent{} is installed, and the \gdaut{} is running.).
\item Set this parameter to true to run the command locally.
-\item Set this parameter to \app{}efbooleanfalse to run the command remotely.
-\bxtipp{If you are running your \gdaut{} on the same machine as the \app{} client, there is no difference between running the command locally or remotely.}
+\item Set this parameter to \gdrefbooleanfalse to run the command remotely.
+\bxtipp{If you are running your \gdaut{} on the same machine as the \ite{}, there is no difference between running the command locally or remotely.}
\item For information on using relative paths to the location of the commands on local and remote machines, see the section in this document \bxpref{relativepath}.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/KeyToogle/param-SelectKey.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/KeyToogle/param-SelectKey.tex
index 78eec8fea..6a62947d7 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/KeyToogle/param-SelectKey.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/KeyToogle/param-SelectKey.tex
@@ -2,7 +2,7 @@
%
\begin{itemize}
\item Use this parameter to specify whether you want to turn the function on or off.
-\item Select \app{}efbooleantrue{} to turn the function on.
-\item Select \app{}efbooleanfalse{} to turn the function off.
+\item Select true to turn the function on.
+\item Select false to turn the function off.
\item Turning the function on when it is already on will not have any effect. The function remains on.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Pause/action-Pause.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Pause/action-Pause.tex
index b5f683ba6..502e1eb36 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Pause/action-Pause.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/GraphicApplication/Pause/action-Pause.tex
@@ -1,5 +1,5 @@
% CAP description for Application --> Pause Test Execution
\begin{itemize}
\item This action pauses the test execution.
-\item To continue a paused test, press the pause button in the \app{} client.
+\item To continue a paused test, press the pause button in the \ite{}.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/TabbedPane/VerifySelectedTab/param-IsSelected.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/TabbedPane/VerifySelectedTab/param-IsSelected.tex
index 349b8458b..07c4b0142 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/TabbedPane/VerifySelectedTab/param-IsSelected.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/TabbedPane/VerifySelectedTab/param-IsSelected.tex
@@ -2,5 +2,5 @@
\begin{itemize}
\item Set this parameter to true if you expect the tab to be selected.
-\item Set this parameter to \app{}efbooleanfalse if you expect the tab not to be selected.
+\item Set this parameter to false if you expect the tab not to be selected.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/ToolItem/VerifyEnabled/param-IsEnabled.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/ToolItem/VerifyEnabled/param-IsEnabled.tex
index 9885fadda..7d77b8517 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/ToolItem/VerifyEnabled/param-IsEnabled.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Concrete/ToolItem/VerifyEnabled/param-IsEnabled.tex
@@ -2,5 +2,5 @@
\begin{itemize}
\item Set this parameter to true if you expect the component to be enabled.
-\item Set this parameter to \app{}efbooleanfalse if you expect the component to be disabled.
+\item Set this parameter to false if you expect the component to be disabled.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyEnabled/param-IsEnabled.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyEnabled/param-IsEnabled.tex
index 2712f3ba9..2ba6c6644 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyEnabled/param-IsEnabled.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyEnabled/param-IsEnabled.tex
@@ -2,5 +2,5 @@
\begin{itemize}
\item Set this parameter to true if you expect the component to be enabled.
-\item Set this parameter to \app{}efbooleanfalse if you expect the component to be disabled.
+\item Set this parameter to false if you expect the component to be disabled.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyExists/param-IsExisting.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyExists/param-IsExisting.tex
index 1aa453ce0..631574eb8 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyExists/param-IsExisting.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyExists/param-IsExisting.tex
@@ -2,5 +2,5 @@
\begin{itemize}
\item Set this parameter to true if you expect the component to exist.
-\item Set this parameter to \app{}efbooleanfalse if you do \emph{not} expect the component to exist.
+\item Set this parameter to false if you do \emph{not} expect the component to exist.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyFocus/param-HasFocus.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyFocus/param-HasFocus.tex
index 512afc492..26a432e65 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyFocus/param-HasFocus.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifyFocus/param-HasFocus.tex
@@ -1,6 +1,6 @@
% CAP description for Toolbar Item --> Verify Focus --> Has Focus
\begin{itemize}
-\item Set this parameter to \app{}efbooleantrue{} if you expect the component to be in focus.
-\item Set this parameter to \app{}efbooleanfalse{} if you expect the component \emph{not} to be in focus.
+\item Set this parameter to true if you expect the component to be in focus.
+\item Set this parameter to false if you expect the component \emph{not} to be in focus.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifySelected/param-IsSelected.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifySelected/param-IsSelected.tex
index 4cdf87da9..2e6826610 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifySelected/param-IsSelected.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/Swt/ToolItem/VerifySelected/param-IsSelected.tex
@@ -1,7 +1,7 @@
% CAP description for Toolbar Item --> Verify Selected --> Selected
\begin{itemize}
-\item Set this parameter to \app{}efbooleantrue{} if you expect the toolbar item to be selected.
-\item Set this parameter to \app{}efbooleanfalse{} if you expect the toolbar item to \emph{not} be selected.
+\item Set this parameter to true if you expect the toolbar item to be selected.
+\item Set this parameter to false if you expect the toolbar item to \emph{not} be selected.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/AbstractButton/VerifySelected/param-IsSelected.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/AbstractButton/VerifySelected/param-IsSelected.tex
index 4b37fa924..7ee8de347 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/AbstractButton/VerifySelected/param-IsSelected.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/AbstractButton/VerifySelected/param-IsSelected.tex
@@ -1,7 +1,7 @@
% CAP description for Button/Check Box/Radio Button --> Verify
% Selected --> Selected
\begin{itemize}
-\item Set this parameter to \app{}efbooleantrue{} if you expect the button to be selected.
-\item Set this parameter to \app{}efbooleanfalse{} if you expect the button to \emph{not} be selected.
+\item Set this parameter to true{} if you expect the button to be selected.
+\item Set this parameter to false{} if you expect the button to \emph{not} be selected.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Activate/action-Activate.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Activate/action-Activate.tex
index ee951ecff..00132919e 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Activate/action-Activate.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Activate/action-Activate.tex
@@ -1,7 +1,7 @@
% CAP description for Application --> Activate
\label{activate}
\begin{itemize}
-\item When the \app{} client and server are running on the same computer, you may need to bring the \gdaut{} into focus before a test can begin.
+\item When the \ite{} and \gdagent{} are running on the same computer, you may need to bring the \gdaut{} into focus before a test can begin.
\item Exactly how to \bxname{activate} the application can vary from one system to another.
\item This action offers various different ways of activating the application.
\item \app{} realises this action by clicking in the location indicated in the \bxname{activation method} parameter.
@@ -16,4 +16,4 @@ activate the application. The activation method is automatically set to \bxcapti
- \ No newline at end of file
+
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/KeyToogle/param-SelectKey.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/KeyToogle/param-SelectKey.tex
index 78eec8fea..0fab71c37 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/KeyToogle/param-SelectKey.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/KeyToogle/param-SelectKey.tex
@@ -2,7 +2,7 @@
%
\begin{itemize}
\item Use this parameter to specify whether you want to turn the function on or off.
-\item Select \app{}efbooleantrue{} to turn the function on.
-\item Select \app{}efbooleanfalse{} to turn the function off.
+\item Select true{} to turn the function on.
+\item Select false{} to turn the function off.
\item Turning the function on when it is already on will not have any effect. The function remains on.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Pause/action-Pause.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Pause/action-Pause.tex
index b5f683ba6..502e1eb36 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Pause/action-Pause.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/GraphicApplication/Pause/action-Pause.tex
@@ -1,5 +1,5 @@
% CAP description for Application --> Pause Test Execution
\begin{itemize}
\item This action pauses the test execution.
-\item To continue a paused test, press the pause button in the \app{} client.
+\item To continue a paused test, press the pause button in the \ite{}.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/SelectValue/param-UseRegularExpression.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/SelectValue/param-UseRegularExpression.tex
index e3aeb9f6a..5515a02a4 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/SelectValue/param-UseRegularExpression.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/SelectValue/param-UseRegularExpression.tex
@@ -1,4 +1,4 @@
% CAP description for Combo Box --> Select Value --> Use Regular Expression
- Set to \app{}efbooleantrue if the text parameter contains a regular
- expression; set to \app{}efbooleanfalse otherwise. See \bxref{regex}
+ Set to true if the text parameter contains a regular
+ expression; set to false otherwise. See \bxref{regex}
for more information on using regular expressions in \app{}. \ No newline at end of file
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/VerifyContainsValue/param-Contains.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/VerifyContainsValue/param-Contains.tex
index fb77ce8f7..b5349f8dc 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/VerifyContainsValue/param-Contains.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JComboBox/VerifyContainsValue/param-Contains.tex
@@ -1,5 +1,5 @@
% CAP description for Combo Box --> Verify Containing Value --> Contains
%% \begin{itemize}
-%% \item Set this parameter to \app{}efbooleantrue{} if you expect the combo box to contain the value.
-%% \item Set this parameter to \app{}efbooleanfalse{} if you expect the combo box \emph{not} to contain the value.
+%% \item Set this parameter to true{} if you expect the combo box to contain the value.
+%% \item Set this parameter to false{} if you expect the combo box \emph{not} to contain the value.
%% \end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/SelectValues/param-UseRegularExpression.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/SelectValues/param-UseRegularExpression.tex
index 437a00c8b..854eea387 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/SelectValues/param-UseRegularExpression.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/SelectValues/param-UseRegularExpression.tex
@@ -1,4 +1,4 @@
% CAP description for List --> Select Value(s) --> Use Regular Expression
- Set to \app{}efbooleantrue if a regular expression is used to
- indicate the list item(s) to be selected. Set to \app{}efbooleanfalse
+ Set to true if a regular expression is used to
+ indicate the list item(s) to be selected. Set to false
if a normal string is used to match the list values.
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/VerifyContainsValue/param-Contains.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/VerifyContainsValue/param-Contains.tex
index 7cc3d3ed1..49cd0cfb0 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/VerifyContainsValue/param-Contains.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JList/VerifyContainsValue/param-Contains.tex
@@ -1,7 +1,7 @@
% CAP description for List --> Verify Containing Value --> Contains
\begin{itemize}
-\item Set the parameter to \app{}efbooleantrue{} if you expect the value to be in the list.
-\item Set the parameter to \app{}efbooleanfalse{} if you expect that the value to \emph{not} be in the list.
+\item Set the parameter to true{} if you expect the value to be in the list.
+\item Set the parameter to false{} if you expect that the value to \emph{not} be in the list.
\end{itemize}
\ No newline at end of file
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/ExpandByTextPath/param-UseRegularExpression.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/ExpandByTextPath/param-UseRegularExpression.tex
index d2c2a80fa..dfbd675f8 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/ExpandByTextPath/param-UseRegularExpression.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/ExpandByTextPath/param-UseRegularExpression.tex
@@ -1,4 +1,4 @@
% CAP description for Tree --> Expand by Textpath --> Use Regular Expression
- Set to \app{}efbooleantrue to evaluate ''Textpath'' as a
+ Set to true to evaluate ''Textpath'' as a
regular expression. See parameter description for ''Collapse''
action for details.
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByIndexPathAtTextNode/param-UseRegularExpression.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByIndexPathAtTextNode/param-UseRegularExpression.tex
index 3385aa65c..54c909aca 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByIndexPathAtTextNode/param-UseRegularExpression.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByIndexPathAtTextNode/param-UseRegularExpression.tex
@@ -1,5 +1,5 @@
% CAP description for Tree --> Context Menu by Indexpath (Node specified by textpath) --> Use Regular Expression
-%% Set to \app{}efbooleantrue to search via regular expression; set to
-%% \app{}efbooleanfalse otherwise. See \bxref{regex} for more
+%% Set to true to search via regular expression; set to
+%% false otherwise. See \bxref{regex} for more
%% information on using regular expressions.
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByTextPathAtTextNode/param-UseRegularExpression.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByTextPathAtTextNode/param-UseRegularExpression.tex
index 398b8e212..d6ac05626 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByTextPathAtTextNode/param-UseRegularExpression.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/PopupByTextPathAtTextNode/param-UseRegularExpression.tex
@@ -1,4 +1,4 @@
% CAP description for Tree --> Context Menu by Textpath (Node specified by textpath) --> Use Regular Expression
- %% Set to \app{}efbooleantrue to search via regular expression; set to
-%% \app{}efbooleanfalse otherwise. See \bxref{regex} for more
+ %% Set to true to search via regular expression; set to
+%% false otherwise. See \bxref{regex} for more
%% information on using regular expressions.
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/SelectByTextPath/param-UseRegularExpression.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/SelectByTextPath/param-UseRegularExpression.tex
index 3a9a325f9..224d3c825 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/SelectByTextPath/param-UseRegularExpression.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/JTree/SelectByTextPath/param-UseRegularExpression.tex
@@ -1,5 +1,5 @@
% CAP description for Tree --> Select by Textpath --> Use Regular Expression
-%% Set to \app{}efbooleantrue to evaluate ''Textpath'' as a regular
+%% Set to true to evaluate ''Textpath'' as a regular
%% expression. In this case, each part of the textpath (separated by
%% a slash, '{\tt /}' ) is handled as a separate regular
%% expression. For each evaluated part of the textpath, the first
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyEnabled/param-IsEnabled.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyEnabled/param-IsEnabled.tex
index e316d9f6d..ddc7a0c08 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyEnabled/param-IsEnabled.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyEnabled/param-IsEnabled.tex
@@ -1,5 +1,5 @@
% CAP description for Graphics Component --> Verify Enabled --> Enabled
\begin{itemize}
\item Set this parameter to true if you expect the component to be enabled.
-\item Set this parameter to \app{}efbooleanfalse if you expect the component to be disabled.
+\item Set this parameter to false if you expect the component to be disabled.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyExists/param-IsExisting.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyExists/param-IsExisting.tex
index d352d60fd..c971564dd 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyExists/param-IsExisting.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyExists/param-IsExisting.tex
@@ -2,5 +2,5 @@
%
\begin{itemize}
\item Set this parameter to true if you expect the component to exist.
-\item Set this parameter to \app{}efbooleanfalse if you do \emph{not} expect the component to exist.
+\item Set this parameter to false if you do \emph{not} expect the component to exist.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyFocus/param-HasFocus.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyFocus/param-HasFocus.tex
index 46debffb2..3041e6e57 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyFocus/param-HasFocus.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Descriptions/old/Widget/VerifyFocus/param-HasFocus.tex
@@ -1,5 +1,5 @@
% CAP description for Graphics Component --> Verify Focus --> Has Focus
\begin{itemize}
-\item Set this parameter to \app{}efbooleantrue{} if you expect the component to be in focus.
-\item Set this parameter to \app{}efbooleanfalse{} if you expect the component \emph{not} to be in focus.
+\item Set this parameter to true{} if you expect the component to be in focus.
+\item Set this parameter to false{} if you expect the component \emph{not} to be in focus.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/Regex.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/Regex.tex
index 3ca0c53a3..f907556cc 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/Regex.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/Regex.tex
@@ -101,81 +101,7 @@ The backslashes before the ordinary slashes are an escape symbol to tell \app{}
\item To check for a text which begins with a \bxshell{*}, you must use the escape character: \verb+\\*.*+
\end{itemize}
-
-%% %In order to allow for powerful verification of textual data, \app{}
-%% %offers support for regular expressions conforming to the
-%% %\bxname{Perl 5} standard. In the actions which support regular
-%% %expressions, there is an additional parameter which allows the user to
-%% %activate/deactivate this feature.
-
-%% %The following basic syntax can be applied for text verification with
-%% %regular expressions:\bigskip
-
-%% %% \begin{tabular}{p{1.5cm}p{5cm}p{2.5cm}}
-%% %% Syntax & Description & Example \\ \hline
-%% %% \app{}efregex{letter, digit, etc.} {Except for a few special characters, \newline
-%% %% {\tt [ ] $\backslash$ . | ? * + ( ) } \newline
-%% %% entering any character will match itself. The above special
-%% %% characters are escaped with a backslash, {\tt $\backslash$ }. }
-%% %% {\bxshell{abc} matches \bxshell{abc}.
-%% %% }
-%% %% \end{tabular}
-
-%% \begin{description}
-%% \item[\textbf{simple matching}]
-%% To match a string exactly to that in a text field, simply type it in:
-
-%% \bxshell{abc} matches \bxshell{abc}, and nothing else.
-
-%% %% To specify that a string should appear at the beginning or end of a
-%% %% text, use a carat ('\verb.^.') or dollar sign ('{\tt \$}'), respectively:
-
-%% %% ''\verb.^.abc'' matches \bxshell{abcxxx} but not
-%% %% \bxshell{xabcxx}.
-
-%% %% \bxshell{abc\$} matches \bxshell{xxxabc} but not \bxshell{xxabcx}.
-%% \item[\textbf{character matching}]
-%% Use brackets ('{\tt [}' and '{\tt ]}') to specify a range of allowed
-%% characters at the current location. Ranges may also be given with a
-%% minus sign ('{\tt -}'),
-%% or alternatives with a ''pipe'' ('{\tt |}'). A period ('{\tt .}')
-%% may be used as a wildcard (instead of brackets) to match any
-%% single character.
-
-%% \bxshell{[0-9A-F]} matches the numbers zero through nine and the
-%% capital letters '{\tt A}' through '{\tt F}' but nothing else.
-
-%% \bxshell{a.b} matches \bxshell{azb} and \bxshell{a6b} but not
-%% \bxshell{ab}.
-
-%% Characters are grouped together using parentheses ('{\tt (}' and
-%% '{\tt )}').
-
-%% \item[\textbf{wildcards/repetition:}]
-%% Use '{\tt ?}' to match a character or group 0 or 1 time(s), '{\tt
-%% *}' to match 0 or more times, and '{\tt +}' to match 1 or more
-%% times. Numbers enclosed in brackets
-%% ('{\tt \{}' and '{\tt \}}') may be used to specify the minimum and maximum
-%% repetitions. The expression
-
-%% ''\verb1abc.+xyz1''
-
-%% matches \bxshell{abcfghixyz} but not \bxshell{abcxyz}.
-
-%% Likewise, the expression
-
-%% ''\verb/[a-zA-Z][a-zA-Z0-9_\-]{4,7}/''
-
-%% may be used to
-%% verify a password format which accepts letters, numbers, '\verb/_/',
-%% and '{\tt -}', with a length between 5 and 8, where the first character
-%% must be a letter (note that '{\tt -}' is preceded by a backslash as
-%% an escape character, as it is normally used to specify range).
-
-%% \end{description}
For additional information about syntax and usage of regular
-expressions in general and in \app{} in particular, please consult one
+expressions in general, please consult one
of the many textbooks on the subject.
-%\bxcomment{MSH}{...or visit http://some.regex.site}
-%\bxcomment{MSH}{Exactly what standard do these conform to?}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Action/SimpleMatch.tex b/org.eclipse.jubula.documentation/reference/en/tex/Action/SimpleMatch.tex
index bb55dd820..1656f97e0 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Action/SimpleMatch.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Action/SimpleMatch.tex
@@ -12,9 +12,9 @@
\begin{itemize}
\item Using \bxname{simple match} lets you verify or select text even if you do not know exactly what the text is.
-\item Using a system of placeholders for characters and some function symbols, you can enter a simple match expression to find or check a text. The patterns for simple match are similar to Unix-style globs or Windows wildcards. The exact syntax is defined below.
\item Actions which support regular expressions have an additional parameter, \bxcaption{Operator}. From this combo box, you can choose \bxcaption{simple match} to indicate that you want to use simple matching.
\end{itemize}
+\bxtipp{\bxname{Simple match} is a good option if you are sure that you will only want to use the basic wildcards given below. For more powerful regular expressions, use the \bxname{matches} parameter \bxpref{regex}.}
\textbf{Simple matching}
\begin{itemize}
@@ -27,34 +27,12 @@
\item \bxshell{*} represents any number (zero or more) of any characters.
\end{itemize}
-\bxtipp{\app{} applies your expression to your entire string. To search for a match within a string, wildcards need to be placed on either side. See the examples below for more information.}
-
-
-\bxtipp{The following syntax information can be useful, but is also more complex. We recommend that simple match expressions use only letters (upper- and lowercase), numbers, and the wildcards described above. In this way, you can avoid complex syntax.}
-\textbf{Ranges}
-\begin{itemize}
-\item For each individual character, you can specify a range of things it is allowed to be.
-\item A range is specified using square brackets (\bxshell{[]}) and a dash \bxshell{-}.
-\item For example, you can specify that a particular character can be any capital letter: \bxshell{[A-Z]}.
-\end{itemize}
-
-\textbf{Escape character}
-\begin{itemize}
-\item Backslash \bxshell{$\backslash$} is used to negate the effect of the character following the backslash.
-\item The characters that are used to construct a simple match expression need to be escaped if they are to be matched within a string.
-\item The characters are: \newline
- [ ? * \newline
-\item Because \app{} already uses a backslash as an escape symbol, you will need to use two backslashes to escape simple match characters.
-\item For example, to check for a tree node \bxcaption{x/y/z/***} where the slashes are a part of the node, your regular expression in \app{} would look like this: \verb1 x\/y\/z\/\\*\\*\\* 1\newline
-The backslashes before the ordinary slashes are an escape symbol to tell \app{} that the following sign is not a path separator. The extra backslash before the stars tells \app{} that the second backslash is to be interpreted as a backslash in the regular expression, i.e. as an escape symbol.
-\end{itemize}
-
\textbf{Useful examples}
\begin{itemize}
\item A string that starts with \bxshell{a} is represented by: \bxshell{a*}
\item A string that ends in \bxshell{a} is represented by: \bxshell{*a}
\item A string that starts with \bxshell{a}, ends in \bxshell{b} and has unknown values (0 or more) in the middle is represented by: \bxshell{a*b}
\item A string which contains \bxshell{a} somewhere between other unknown characters (0 or more) is represented by: \bxshell{*a*}
-\item To check for a text which begins with a star (\bxshell{*}), you must use the escape character: \verb+\\**+
+%\item To check for a text which begins with a star (\bxshell{*}), you must use the escape character: \verb+\\**+
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Constants/CONTENT.tex b/org.eclipse.jubula.documentation/reference/en/tex/Constants/CONTENT.tex
index 972a34897..9fde128b0 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Constants/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Constants/CONTENT.tex
@@ -21,7 +21,7 @@
\index{Value Separator}
\index{Path Separator}
\index{Indices}
-Many of the \app{}actions use parameters for which you need to enter a ''path'' (e.g. menupaths, a path through a tree etc.) or a ''list'' (e.g. to select multiple items from a list or combo box).
+Many of the \app{} actions use parameters for which you need to enter a ''path'' (e.g. menupaths, a path through a tree etc.) or a ''list'' (e.g. to select multiple items from a list or combo box).
The following are the characters you must use to enter lists and paths:
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Debugging/remoteDebugging.tex b/org.eclipse.jubula.documentation/reference/en/tex/Debugging/remoteDebugging.tex
index 16bf7ab78..e5eeb7549 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Debugging/remoteDebugging.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Debugging/remoteDebugging.tex
@@ -28,11 +28,11 @@ and enter the hostname for the computer on which the \gdagent{} is running. The
To get your \gdaut{} running using remote debugging options you have to take the following steps:
\begin{enumerate}
\item Start the \gdagent{}
- \item Connect the Client with the \gdagent{}, load the \gdproject{} in \app{} and invoke the startup of the \gdaut{} in the \app{} client.
+ \item Connect the \ite{} with the \gdagent{}, load the \gdproject{} in \app{} and invoke the startup of the \gdaut{} in the \ite{}.
\item If ''suspend=y'', you now have to run your "Remote Java Application"-configuration
in Eclipse, as the JVM is waiting for the debugger to connect before starting the
application. As soon as you are connected you should see the default debug behaviour in your
- debug perspective of eclipse.
+ debug perspective of Eclipse.
\item Your \gdaut{} has now been launched with the ability to use remote debugging.
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Icons/CONTENT.tex b/org.eclipse.jubula.documentation/reference/en/tex/Icons/CONTENT.tex
deleted file mode 100644
index b5efc6543..000000000
--- a/org.eclipse.jubula.documentation/reference/en/tex/Icons/CONTENT.tex
+++ /dev/null
@@ -1,66 +0,0 @@
-% $Id: CONTENT.tex 9168 2009-09-28 08:37:25Z zeb $
-% Local Variables:
-% ispell-check-comments: nil
-% Local IspellDict: american
-% End:
-% --------------------------------------------------------
-% User documentation
-% copyright by BREDEX GmbH 2005
-% --------------------------------------------------------
-% name of component
-%\app{}efcomponent{}
-% ----------------------------
-% description of component
-%\app{}efdescription{}
-% ----------------------------
-% input the generated inherits
-%% \input{Action/Generated/inheritedAction-<name>}
-% ----------------------------
-% input the generated synopsis
-%% \input{Action/Generated/synopsis-<name>}
-% ----------------------------
-% input the generated new actions
-%% \input{Action/Generated/newAction-<name>}
-% ----------------------------
-% each new action in detail
-% \app{}efactiondesciption{<translated name>}{<description>}
-%\app{}efactiondesciption{}{}
-% and the arguments
-%\begin{gdrefparam}
-% \app{}efparamentry{<name>}{<type>}{<values>}{<default>}
- % \app{}efparamentry{}{}{}{}
-%\end{gdrefparam}
-% ----------------------------
-% the components which inherit the actions of this component
-% comma-separated list
-%\app{}efused{}
-\index{Icons!Parameter}
-\index{Icons!Status Bar}
-\index{Icons!Problem View}
-\index{Parameter!Icons}
-\index{Status Bar!Icons}
-\index{Problem View!Icons}
-This section will present and explain some of the symbols and icons used
-throughout \app{}.
-
-%\bxcomment{AI}{Need to do test case etc icons? Toolbar?}
-\section{Test units}
-\input{Icons/cases}
-
-\section{Perspectives}
-\input{Icons/browser}
-
-\section{Toolbar icons}
-\input{Icons/toolbar}
-
-\section{Parameter Value Icons}
-\input{Icons/parametericons}
-
-\section{Status Bar Icons}
-\input{Icons/statusbaricons}
-
-\section{Problem View Icons}
-\input{Icons/problemviewicons}
-
-\section{Other Icons}
-\input{Icons/other}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Icons/browser.tex b/org.eclipse.jubula.documentation/reference/en/tex/Icons/browser.tex
deleted file mode 100644
index a4719494b..000000000
--- a/org.eclipse.jubula.documentation/reference/en/tex/Icons/browser.tex
+++ /dev/null
@@ -1,18 +0,0 @@
-
-\begin{gdreficon}
- \app{}eficondescr{Specification perspective}{perspectivesp}
- \app{}eficondescr{Execution perspective}{perspectiveex}
- \app{}eficondescr{\gdtestcasebrowser}{specTcBrowser}
- \app{}eficondescr{\gdtestcaseeditor}{specTcEditor}
- \app{}eficondescr{\gdtestsuitebrowser}{testSuiteBrowser}
- \app{}eficondescr{\gdtestsuiteeditor}{testSuiteEditor}
- \app{}eficondescr{\gddatasetsview}{dataSetView}
- \app{}eficondescr{\gdpropview}{propertiesView}
- \app{}eficondescr{\gdprobview}{problems_view}
- \app{}eficondescr{\gdcompnamesview}{compNamesView}
- \app{}eficondescr{\gdtestresultview}{testResultTree}
- \app{}eficondescr{\gdomeditor}{omEditor}
-\end{gdreficon}
-
-
-
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Icons/cases.tex b/org.eclipse.jubula.documentation/reference/en/tex/Icons/cases.tex
deleted file mode 100644
index ac283d948..000000000
--- a/org.eclipse.jubula.documentation/reference/en/tex/Icons/cases.tex
+++ /dev/null
@@ -1,21 +0,0 @@
-\begin{gdreficon}
- \app{}eficondescr{\gdstep}{cap}
- \app{}eficondescr{\gdcase}{testCase}
- \app{}eficondescr{reused \gdcase}{testCaseRef}
- \app{}eficondescr{\gdehandler}{EventHandler}
- \app{}eficondescr{\gdsuite}{testSuite}
- \app{}eficondescr{Category}{category}
- \app{}eficondescr{\gdproject}{project}
-\end{gdreficon}
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Icons/other.tex b/org.eclipse.jubula.documentation/reference/en/tex/Icons/other.tex
deleted file mode 100644
index ab0db93dd..000000000
--- a/org.eclipse.jubula.documentation/reference/en/tex/Icons/other.tex
+++ /dev/null
@@ -1,29 +0,0 @@
-% $Id: other.tex 3127 2006-09-28 18:05:03Z mike $
-% Local Variables:
-% ispell-check-comments: nil
-% Local IspellDict: american
-% End:
-% --------------------------------------------------------
-% User documentation
-% copyright by BREDEX GmbH 2005
-% --------------------------------------------------------
-\begin{gdreficon}
- \app{}eficondescr{Collapse tree}{collapse}
- \app{}eficondescr{Order alphabetically}{sort}
- \app{}eficondescr{Start incomplete \gdsuite{}}{startIncomplSuite}
- \app{}eficondescr{Depricated action}{depricated}
- \app{}eficondescr{Local component name (used in the current \gdcase{})}{localName}
- \app{}eficondescr{Global component name (used in another \gdcase{})}{globalName}
- \app{}eficondescr{Highlight in \gdaut{}}{highlight}
- \app{}eficondescr{Map into a category}{MapInCat}
- \app{}eficondescr{Component name}{OMLogName}
- \app{}eficondescr{Technical name}{OMTecName}
- \app{}eficondescr{\gdstep{} successful}{StepOK}
- \app{}eficondescr{\gdstep{} failed}{StepNotOK}
- \app{}eficondescr{Testing \gdstep{}}{StepTesting}
- \app{}eficondescr{Move component name up a level}{propagate}
- \app{}eficondescr{Move parameter up a level}{refArrow}
- \app{}eficondescr{Search}{search}
- \app{}eficondescr{Show where reused}{showSpec}
- \app{}eficondescr{Read only data}{readonly}
-\end{gdreficon}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Icons/parametericons.tex b/org.eclipse.jubula.documentation/reference/en/tex/Icons/parametericons.tex
deleted file mode 100644
index 31f0ecbf3..000000000
--- a/org.eclipse.jubula.documentation/reference/en/tex/Icons/parametericons.tex
+++ /dev/null
@@ -1,17 +0,0 @@
-% $Id: parametericons.tex 3127 2006-09-28 18:05:03Z mike $
-% Local Variables:
-% ispell-check-comments: nil
-% Local IspellDict: american
-% End:
-% --------------------------------------------------------
-% User documentation
-% copyright by BREDEX GmbH 2005
-% --------------------------------------------------------
-\begin{gdreficon}
- \app{}eficondescr{Parameter values which are the same as those in the master
- template (i.e.
- have not been overwritten) are displayed with a gray diamond to their left in
- the \gdpropview{}}{originalData}
- \app{}eficondescr{Parameter values which have been overwritten show a yellow diamond. }{overwrittenData}
- \app{}eficondescr{When a reference has been entered, the reference symbol can be seen. }{refArrow}
-\end{gdreficon}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Icons/problemviewicons.tex b/org.eclipse.jubula.documentation/reference/en/tex/Icons/problemviewicons.tex
deleted file mode 100644
index e244559a8..000000000
--- a/org.eclipse.jubula.documentation/reference/en/tex/Icons/problemviewicons.tex
+++ /dev/null
@@ -1,17 +0,0 @@
-% $Id: problemviewicons.tex 3127 2006-09-28 18:05:03Z mike $
-% Local Variables:
-% ispell-check-comments: nil
-% Local IspellDict: american
-% End:
-% --------------------------------------------------------
-% User documentation
-% copyright by BREDEX GmbH 2005
-% --------------------------------------------------------
-
-The icons in the \gdprobview are as follows:
-
-\begin{gdreficon}
- \app{}eficondescr{Error}{error}
- \app{}eficondescr{Warning}{warning}
- \app{}eficondescr{Information}{info}
-\end{gdreficon}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Icons/statusbaricons.tex b/org.eclipse.jubula.documentation/reference/en/tex/Icons/statusbaricons.tex
deleted file mode 100644
index 443194cd6..000000000
--- a/org.eclipse.jubula.documentation/reference/en/tex/Icons/statusbaricons.tex
+++ /dev/null
@@ -1,40 +0,0 @@
-% $Id: statusbaricons.tex 6871 2008-05-20 09:21:12Z alexandra $
-% Local Variables:
-% ispell-check-comments: nil
-% Local IspellDict: american
-% End:
-% --------------------------------------------------------
-% User documentation
-% copyright by BREDEX GmbH 2005
-% --------------------------------------------------------
-
-\subsection{\gdagent information}
-
-The \gdagent messages which appear are:
-
-\begin{gdreficon}
- \app{}eficondescr{Not connected to \gdagent}{NoServer}
- \app{}eficondescr{Connected to \gdagent}{NoSC}
-\end{gdreficon}
-
-
-\subsection{\gdaut information}
-
-The following information about the \gdaut can be seen in the status bar:
-
-\begin{gdreficon}
- \app{}eficondescr{Connected to \gdagent (when the connection to the \gdaut is being made)}{NoAUT}
- \app{}eficondescr{\gdaut is running}{AUTup}
-\end{gdreficon}
-
-
-\subsection{Object mapping and observing information}
-
-When in the observation mode and \gdomm{}, this will be shown in the status bar:
-
-\begin{gdreficon}
- \app{}eficondescr{\gdomm started}{startOM}
- \app{}eficondescr{Observation mode started}{cam}
-\end{gdreficon}
-
-
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Icons/toolbar.tex b/org.eclipse.jubula.documentation/reference/en/tex/Icons/toolbar.tex
deleted file mode 100644
index 45ce5c540..000000000
--- a/org.eclipse.jubula.documentation/reference/en/tex/Icons/toolbar.tex
+++ /dev/null
@@ -1,15 +0,0 @@
-\begin{gdreficon}
- \app{}eficondescr{Save}{save}
- \app{}eficondescr{Working language}{globe}
- \app{}eficondescr{Connect to \gdagent}{startServer}
- \app{}eficondescr{Disconnect from \gdagent}{stopServer}
- \app{}eficondescr{Start \gdaut{}}{startAUT}
- \app{}eficondescr{Stop \gdaut{}}{stopAUT}
- \app{}eficondescr{Start \gdsuite{}}{startSuite}
- \app{}eficondescr{Pause \gdsuite{}}{pause}
- \app{}eficondescr{Stop \gdsuite{}}{stop}
- \app{}eficondescr{Start observation mode}{cam}
- \app{}eficondescr{Stop observation mode}{stopcam}
- \app{}eficondescr{Start \gdomm{}}{startOM}
- \app{}eficondescr{Stop \gdomm{}}{stopOM}
-\end{gdreficon}
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Intro/intro.tex b/org.eclipse.jubula.documentation/reference/en/tex/Intro/intro.tex
index 7e2f990e4..4fc62c6fa 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Intro/intro.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Intro/intro.tex
@@ -15,19 +15,4 @@
%% % ----------------------------------------------------------------------
%% \end{document}
-This manual provides important information about the more technical side of working with \gd. In the following sections, you will find:
-\begin{itemize}
-%\item a list of the keyboard shortcuts available in \app{}\bxpref{scut}.
-\item an introduction to using regular expressions as parameters \bxpref{regex}.
-\item an introduction to using simple matches in your parameters \bxpref{simplematch}
-\item a reference of all supported actions and their parameters \bxpref{actparam}.
-\item details about the constants used to enter paths and list items \bxpref{constants}.
-\item a guide to using the abstract components offered by \app{}\bxpref{overviewfam}.
-\item information on relative paths in \app{} \bxpref{relativepath}.
-\item a list of the special characters in \app{} \bxpref{specialchar}.
-\item a table of language codes \bxpref{langcodes}.
-\item information on keyboard layout files \bxpref{keyboardlayout}.
-%\item a list of common icons used in \app{}\bxpref{icons}.
-\item instructions on how to remotely debug your \gdaut{} with \app{} \bxpref{debugging}.
-%\item \app{}error messages \bxpref{errormsgs}.
-\end{itemize}
+This manual provides important information about the more technical side of working with \app{}.
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Overview/comp.tex b/org.eclipse.jubula.documentation/reference/en/tex/Overview/comp.tex
index 8f500d18e..58036bdfe 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Overview/comp.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Overview/comp.tex
@@ -11,4 +11,14 @@
The following diagram shows which abstract components \app{} uses and for which actions they can be used for.
-\input{Overview/model}
+\begin{figure}
+\begin{center}
+\includegraphics{Overview/PS/GUIdancerComponentHierarchysmall}
+\caption{\app{} component structure}
+\label{comp}
+\end{center}
+\end{figure}
+
+Figure \ref{comp} provides an overview of \app{}'s concrete and abstract component structure. This figure can be interpreted as follows: the arrows show inheritance relations between the components. Thus, a \bxname{Label} component has no actions of its own, but inherits them all from \bxname{Component with Text}. The \bxname{Label} component also inherits any actions that \bxname{Component with Text} also inherited. In this case, these are the actions from \bxname{Graphics component}.
+
+\clearpage
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Relative/relpaths.tex b/org.eclipse.jubula.documentation/reference/en/tex/Relative/relpaths.tex
index a93ccb5a9..b6162d13a 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Relative/relpaths.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Relative/relpaths.tex
@@ -16,7 +16,7 @@ These items reside on the machine on which the \gdagent is installed.
\textbf{Paths to Excel files}\\
-External data files reside on the machine on which the client is installed.
+External data files reside on the machine on which the \ite{} is installed.
\begin{itemize}
\item When you use an Excel file an external data source, you must enter the path to the Excel file in the \gdpropview{}.
\item The default root for external data sources is your workspace directory.
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/Shortcuts/CONTENT.tex b/org.eclipse.jubula.documentation/reference/en/tex/Shortcuts/CONTENT.tex
index 295c60fe2..ba7e4b653 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/Shortcuts/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/Shortcuts/CONTENT.tex
@@ -11,6 +11,6 @@
\app{} offers various keyboard shortcuts to make working with the keyboard easier and quicker.
-Most of the shortcuts can be changed in the \bxname{Preferences} in the \app{} client. Shortcuts for object mapping and observation are in the \app{} preferences. Other shortcuts can be seen and changed in the \bxname{General/Keys} preferences.
+Most of the shortcuts can be changed in the \bxname{Preferences} in the \ite{}. Shortcuts for object mapping and observation are in the \app{} preferences. Other shortcuts can be seen and changed in the \bxname{General/Keys} preferences.
\bxtipp{Press \bxkey{Ctrl+Shift+l} twice to see the list of shortcuts used in \app{} and Eclipse. }
diff --git a/org.eclipse.jubula.documentation/reference/en/tex/content.tex b/org.eclipse.jubula.documentation/reference/en/tex/content.tex
index dc094fbbc..48fb6796e 100644
--- a/org.eclipse.jubula.documentation/reference/en/tex/content.tex
+++ b/org.eclipse.jubula.documentation/reference/en/tex/content.tex
@@ -84,10 +84,6 @@
\label{keyboardlayout}
\input{Keyboard/CONTENT}
\clearpage
-%% \chapter{Icons}
-%% \label{icons}
-%% \input{Icons/CONTENT}
-\clearpage
\chapter{Debugging}
\label{debugging}
diff --git a/org.eclipse.jubula.documentation/releasenotes/en/tex/content.tex b/org.eclipse.jubula.documentation/releasenotes/en/tex/content.tex
index 8ffc5674a..19ecb43e7 100644
--- a/org.eclipse.jubula.documentation/releasenotes/en/tex/content.tex
+++ b/org.eclipse.jubula.documentation/releasenotes/en/tex/content.tex
@@ -24,866 +24,8 @@ The release notes are presented in chronological order, with the most recent at
\section{Important advice for migrating to new \app{} versions}
Existing customers who wish to update to a new version of \app{} should follow the steps described in the installation manual to ensure a problem-free migration.
-% improved speed of test execution: according to system. can lower if problems with synchronization or add more synchronization
+\input{summary}
-% renamed: rcp remote control plugin, ite for client, autrun, test executor (testexec), TST_ for
-%preferences now under Test
-% perspectives renamed
-%new menu Test, File
-
-% component id tag is there again - ID attribute name
-
-%copy paste guid
-
-%xls data removed from meters. instead cds
-
-%new db config preferences - context id!
-
-% support for divs and lists in html
-
-% support for link
-
-% support for swt component
-
-% new commands in gdrun and command line client (e.g. -data for ws)
-
-% export in file menu - what can it do (db prefs for example)
-
-% h2 db doesn't need username or password in dialog. both empty
-
-%db admin, config tool and license tool are gone
-
-%test result summary - last 50 shown
-
-
-%guidancer stuff
-
-% CC: Jacoco and Yourkit as standard. How add others? In AUT Config: Working Dir is default, source folder for class files for Jacoco available to enter. Once CC run, can see in test result summary view. Can open report to see CC. Report saved to workspace (have to delete self).Report details deleted with test result details. CC is reset when app is restarted (except for with restart AUT action). Cumulative if not restarted. Can specify in config whether should be reset at TS beginning or end. For real tests, always fresh AUT. For Test Jobs, don't reset between TS. No CC for gdrun. Which classes are not included? Heap space problem in AUT agent
-
-% Teststyle: in properties under Teststyle. Can set level.
-
-%License. Preferences GUIdancer. If no license, can be funny effects cos Jubula plugins all work but GD plugins can't be loaded. License valid for ever but not for all versions.
-
-
-\makeatletter
-\section{Release Notes for \app{} \@bxversion}
-\makeatother
-\subsection{Information}
-This release is a patch to fix a problem that occurred in the \bxname{unbound modules concrete} whereby the \bxname{tree} component had a false component type. The database and license are the same as in version 4.3.01105.
-
-\makeatletter
-\section{Release Notes for \app{} 4.3.01105}
-\makeatother
-\subsection{Information}
-This release is a patch to fix a problem that occurred in the \bxname{unbound modules concrete} whereby the \bxname{tree} component had a false component type. The database and license are the same as in version 4.3.01105.
-
-\makeatletter
-\section{Release Notes for \app{} 4.3.01105}
-\makeatother
-\subsection{New features and developments}
-\textbf{Mylyn integration}
-\begin{itemize}
-\item The Mylyn plugin is now available for use within \app{}.
-\item You can connect to repositories (e.g. bug-tracking systems) to work on testing tasks directly in \app{}.
-\item You can also create your own local tasks, and reduce the amount of \gdcases{} visible to only those required for the current task.
-\end{itemize}
-\textbf{Central test data}
-\begin{itemize}
-\item \app{} has a new editor for managing data centrally for a \gdproject{}
-\item The \gddataeditor{} can be opened via a button on the toolbar.
-\item Within the editor, you can add data sets which can then be referenced in \gdcases{}.
-\end{itemize}
-
-\textbf{New data option and display in \gdpropview{}}
-\begin{itemize}
-\item The \gdpropview{} now shows what type of data is currently being used for a \gdcase{}.
-\item The possible data sources are:
-\begin{description}
-\item [Referenced Test Case]{the data being used have come directly from the original specification of this \gdcase{}. }
-\item [Local Test Case]{the data being used were entered for this \gdcase{}. You can change from \bxname{local} to \bxname{referenced} test data using the combo box to reset the default value from the referenced \gdcase{}.}
-\item [Central test data set]{the data have come from a central test data set.}
-\item [Excel data file]{an Excel file has been entered as the data source.}
-\end{description}
-\end{itemize}
-
-\textbf{New search dialog and options}
-\begin{itemize}
-\item \app{} has new options to search for items and test data within a \gdproject{}.
-\item The search dialog can be opened from the toolbar and offers searches for:
-\begin{description}
-\item [Keywords]{Names of \gdsteps{}, \gdcases{}, \gdsuites{}, \gdjobs{} and categories in the \gdproject{}}
-\item [Test data]{Data contained in \gdcases{}, \gdsteps{} and central data sets}
-\item [Files]{File types and contents in the workspace}
-\item [Tasks]{Tasks from repositories connected to \app{}.}
-\end{description}
-\item Search results are shown in the \gdsearchresultview{}. Items can be opened in their editors by double-clicking the specific search result.
-\end{itemize}
-
-\textbf{Manual \gdsteps{}}
-\begin{itemize}
-\item \app{} now allows the definition of manual \gdcases{}
-\item There is a new module for a manual \gdstep{}.
-\item Manual \gdcases{} can be combined into \gdsuites{} and executed.
-\item During execution, a dialog appears to inform the manual tester which steps to perform.
-\item The tester can mark the action as \bxname{passed} or \bxname{failed} and can write comments about the \gdstep{}.
-\item The result reports from manual tests can be examined and analyzed just like result reports for automated tests.
-\end{itemize}
-
-\textbf{Testing \gdauts{} started by other \gdauts{}}
-\begin{itemize}
-\item It is now possible to test an \gdaut{} that was started by another \gdaut{}.
-\item There is a new mode for the \gdagent{} to allow this, the \bxname{lenient mode}.
-\item \gdauts{} started in this way must be of the same toolkit as the original \gdaut{}.
-\item For each newly started \gdaut{}, a new \gdaut{} ID is generated with a running number.
-\end{itemize}
-\textbf{Test results}
-\begin{itemize}
-\item Test results that are reopened from the \gdtestsummaryview{} now contain complete information about each \gdstep{}.
-\item Test results can also be exported from the \gdtestsummaryview{} in HTML and XML format.
-\item The option to automatically clean up test result details is now part of the \gdproject{} properties, and no longer a user preference.
-\item In the \gdtestsummaryview{}, you can now enter comments about each test run to document the reason for failing or passing.
-\end{itemize}
-\textbf{New split pane view for the \gdomeditor{}}
-\begin{itemize}
-\item The \gdomeditor{} has a new view -- the split view.
-\item In the split view, each category (\bxname{assigned names, unassigned component names} and \bxname{unassigned technical names}) has a different pane.
-\item This allows you to navigate to the place you require in each category separately to make mapping in large \gdprojects{} more comfortable.
-\end{itemize}
-\textbf{New actions}
-\begin{itemize}
-\item Check existence of window by title
-\item Check text at mouse position in trees
-\item Store value at mouse position on trees
-\item Store value on selected node in trees
-\item Store value at mouse position in tables
-\end{itemize}
-
-\textbf{New parameters for existing actions}
-\begin{itemize}
-\item The action for selecting a node from a tree now also has the parameter \bxname{extend selection} so that multiple nodes can be selected in trees.
-\item The parameters for actions requiring modifiers (control, alt etc.) have been changed so that a space-separated list of modifiers can be entered. Content assist is available for the modifier parameters.
-\end{itemize}
-
-\textbf{Protection for reused \gdprojects{}}
-\begin{itemize}
-\item There is a new option in the \gdproject{} wizard and \gdproject{} properties to \bxname{protect} a \gdproject{}.
-\item We recommend marking a \gdproject{} as protected if you are using it as a library (referenced) \gdproject{} for another \gdproject{}.
-\item In protected \gdprojects{}, \gdcases{} cannot be deleted, and the \bxname{edit parameters} dialog cannot be opened.
-\item This is to stop any irrevocable changes being made that would affect the \gdprojects{} that reuse the protected \gdproject{}.
-\item The protected status of \gdprojects{} can be altered in the \gdproject{} properties.
-\end{itemize}
-\textbf{Viewing BIRT reports in embedded database}
-\begin{itemize}
-\item BIRT reports generated from the \gdtestsummaryview{} can now be viewed when using the embedded \gddb{}.
-\end{itemize}
-\textbf{Show where used on \gdsuite{}}
-\begin{itemize}
-\item The action \bxname{Show where used} (\bxkey{F6}) is now also possible on \gdsuites{} that have been reused in \gdjobs{}.
-\end{itemize}
-\textbf{Open specification action}
-\begin{itemize}
-\item There is a new action available on \gdcases{} and \gdsuites{} which have been reused (in other \gdcases{} or in \gdjobs{}).
-\item Use \bxkey{Ctrl+F6} to open the specification of the selected \gdcase{} or \gdsuite{} in the relevant editor.
-\item This action is possible even if the \gdcase{} or \gdsuite{} to open is hidden due to an active filter.
-\end{itemize}
-\textbf{Open \gdcase{} action}
-\begin{itemize}
-\item There is a new dialog to open an existing \gdcase{} or multiple \gdcases{} in their editors.
-\item Use \bxkey{Ctrl+Shift+T} to open the dialog and select the \gdcases{} to be opened.
-\item This action is possible even if the \gdcase{} or \gdsuite{} to open is hidden due to an active filter.
-\end{itemize}
-
-
-\textbf{Show corresponding specification in \gdomeditor{}}
-\begin{itemize}
-\item In the \gdomeditor{} there is a new option to show the corresponding specification of a component name.
-\item You can use this option when a component name appears in the \gdomeditor{} that you should have overwritten.
-\item The \gdsearchresultview{} only shows places which could have lead to this component name appearing in the \gdomeditor{}, not all places in the test where it has been used.
-\end{itemize}
-
-\textbf{Key combination to switch views in the client}
-\begin{itemize}
-\item We have introduced shortcuts to switch to specific views in the specification perspective.
-\item To switch to the \gdtestsuitebrowser{}, use \bxkey{Alt+Shift+1}
-\item To switch to the \gdtestcasebrowser{}, use \bxkey{Alt+Shift+2}
-\item To switch to the \gdpropview{}, use \bxkey{Alt+1}
-\item To switch to the \gddatasetsview{}, use \bxkey{Alt+2}
-\item To switch to the \gdcompnamesview{}, use \bxkey{Alt+3}
-\item To switch to editor, use \bxkey{F12}
-\end{itemize}
-The key combinations can be changed in the preferences.
-
-\textbf{Support for custom renderers in Swing}
-\begin{itemize}
-\item Custom renderers in Swing \gdauts{} can now be tested with \app{} as long as the renderer implements either getText() or getTestableText().
-\item The method signatures you implement must be:
-\begin{quote}
-public String getTestableText();
-public String getText();
-\end{quote}
-\item If you don't have a getText() method, then we recommend using the getTestableText() option to avoid conflicts.
-\end{itemize}
-
-\textbf{Dropping \gdcases{} directly into the editor area}
-\begin{itemize}
-\item You can now drop \gdcases{} directly into the editor, without having to place the \gdcase{} before or after another \gdcase{} in the editor.
-\item The \gdcase{} is placed at the bottom of the tree in the editor.
-\end{itemize}
-
-\subsection{Other information}
-\textbf{New workspace recommended for 4.3}
-\begin{itemize}
-\item We recommend setting up a new workspace for version 4.3 of \app{}.
-\end{itemize}
-\textbf{Object mapping in RCP \gdauts{} that do not use GEF}
-\begin{itemize}
-\item We have fixed an issue with automatic component naming in RCP \gdauts{}.
-\item Customers testing RCP \gdauts{} where \textbf{no} GEF bundles are present are advised to remap their components.
-\end{itemize}
-\makeatletter
-\section{Release Notes for \app{} 4.2.01053}
-\makeatother
-\subsection{New features and developments}
-
-\textbf{Eclipse 3.6 supported}
-\begin{itemize}
-\item \app{} is compatible with Eclipse applications that are written in 3.6
-\end{itemize}
-
-\textbf{Viewing test results in \app{}}
-\begin{itemize}
-\item Full test result details that are still in the \gddb{} can now be opened in the \gdtestresultview{} from the \gdtestsummaryview{}.
-\item This lets you review tests that ran overnight directly in the \app{} client.
-\end{itemize}
-
-\textbf{Automatic \gddb{} migration}
-\begin{itemize}
-\item \app{} now contains a \gddb{} migration wizard.
-\item When a connection to a \gddb{} is made in a new version, \app{} automatically recognizes whether the \gddb{} version is incompatile.
-\item If so, you can start the migration wizard. You specify which \gdprojects{} \app{} should import into the new \gddb{} (the \gdprojects must have been exported from the previous version).
-\item The migration wizard converts the \gddb{} automatically to the new version.
-\end{itemize}
-
-\textbf{Commenting out \gdcases{}}
-\begin{itemize}
-\item You can now comment out \gdcases{} and \gdsteps{} in editors.
-\item Items that have been commented out are inactive and are neither validated for \gdsuite{} completeness, nor executed.
-\end{itemize}
-
-\textbf{New parameters for table actions}
-\begin{itemize}
-\item Actions on tables now have new parameters for \bxname{row operator} and \bxname{column operator}.
-\item You can now select rows and columns based on their title and also determine how you want the selection to occur (equals, matches, simple match, not equals).
-\end{itemize}
-
-\textbf{New parameter for select actions}
-\begin{itemize}
-\item Actions that select items from tables, lists and trees have a new parameter for \bxname{mouse button}.
-\item You can now define which mouse button should be used to select the item.
-\end{itemize}
-
-\textbf{Number of failed \gdsteps{} shown}
-\begin{itemize}
-\item The \gdtestsummaryview{} now also has the information about how many \gdsteps{} failed in a test run.
-\end{itemize}
-
-\textbf{Information about whether test result details are available}
-\begin{itemize}
-\item The \gdtestsummaryview{} now also has the information about whether the details for a test run are still in the \gddb{}.
-\item If the results are still available, then the \gdtestresultview{} can be reopened.
-\end{itemize}
-
-\textbf{Spring to next/previous error}
-\begin{itemize}
-\item In the \gdtestresultview{} which opens when you open the results for a test run from the \gdtestsummaryview{}, you can use two new toolbar buttons to spring to the next/previous error.
-\end{itemize}
-
-\textbf{Showing comments for \gdcases{}}
-\begin{itemize}
-\item Any comments you write on \gdcases{} are now visible as a tooltip when you hover over the \gdcase{} in the browsers or in the search result view.
-\end{itemize}
-
-\textbf{Pause on error}
-\begin{itemize}
-\item There is a new button on the toolbar to pause the test execution if an error occurs.
-\item This can be switched on and off during a test run and allows you to easily stop the test to see what went wrong.
-\item The test can be continued by clicking the \bxname{pause test execution} button on the toolbar.
-\end{itemize}
-
-\textbf{Using running \gdaut{} details to define an \gdaut{}}
-\begin{itemize}
-\item \gdauts{} that have been started using the \bxname{gdrun} command can now be automatically defined in the \app{} client.
-\item You can select the option to create an \gdaut{} definition from the running \gdauts{} view for any \gdaut{} that is currently unknown to \app{}.
-\end{itemize}
-
-\textbf{Show referenced children}
-\begin{itemize}
-\item There is a new option in the preferences to show referenced children in \gdcases{} in the \gdtestcasebrowser{}.
-\item This preference is activated by default.
-\item Deactivating the preference means that any children of referenced \gdcases{} are not displayed in the \gdtestcasebrowser{}.
-\item This can help in particularly large \gdprojects{} to inprove performance.
-\end{itemize}
-
-
-\textbf{New action}
-\begin{itemize}
-\item There is a new action to wait for the menu component.
-\end{itemize}
-
-\subsection{Other information}
-\textbf{XML and HTML reports scheduled for removal}
-\begin{itemize}
-\item The XML and HTML reports that can be generated by \app{} (configurable in the preferences) are scheduled for removal in the next versions.
-\item There will be an alternative feature to create a HTML report from the test result report in \app{}, as long as the test details are still in the \gddb{}.
-\item For queries about this plan, please contact the support team.
-\end{itemize}
-
-\textbf{Deprecated unbound modules earlier than 3.0 scheduled for removal}
-\begin{itemize}
-\item The unbound modules that have been deprecated in versions earlier than 3.0 are also scheduled for removal in the upcoming version.
-\item We always recommend updating to the latest version of the unbound modules and removing any references to deprecated modules in your tests.
-\end{itemize}
-
-\textbf{New unbound modules for tables and for select actions on lists, trees and tree-tables}
-\begin{itemize}
-\item Because we have added new parameters to actions on these components, there are new unbound modules for the actions.
-\item The old unbound modules have been set to deprecated.
-\item We recommend updating any deprecated modules in your tests with the new modules.
-\item You can see what the new module is by looking in the deprecated module - these now contain the new actions.
-\end{itemize}
-
-\textbf{Merging in the \gdomeditor}
-\begin{itemize}
-\item The option to merge components in the \gdomeditor{} has been temporarily deactivated for this release.
-\end{itemize}
-
-\makeatletter
-\section{Release Notes for \app{} 4.1.01039}
-\makeatother
-\subsection{New features and developments}
-\textbf{New option in delete \gdproject{} dialog}
-\begin{itemize}
-\item When you delete a \gdproject{}, you can now decide whether you want to keep the test results for the \gdproject{} or delete them as well.
-\end{itemize}
-\textbf{Performance improvements}
-\begin{itemize}
-\item We have further improved the performance for the saving and loading of \gdprojects{}. The validation of \gdsuites{} now runs as a background job so that test specification can continue while the tests are being validated.
-\item \gdsuites{} must be validated before they can be executed.
-\end{itemize}
-\textbf{Generated names penalty removed}
-\begin{itemize}
-\item The generated names penalty has been removed from the object mapping configuration area and from the object recognition calculation.
-\end{itemize}
-\textbf{Optional automatic screenshots when errors occur}
-\begin{itemize}
-\item You can now define whether or not \app{} should automatically take a screenshot when an error occurs.
-\item Screenshots taken in this manner are saved into the \gddb{} and can be viewed in the \gdimgview{} in \app{} by clicking on the failed \gdstep{}.
-\item You can alter this preference in the Test Result preference page.
-\item In the command line client, screenshots are automatically taken unless you include the parameter \bxshell{-s}.
-\end{itemize}
-\textbf{New relevance flag for test results}
-\begin{itemize}
-\item You can now specify at the beginning of each test execution whether the test results are relevant for your test reports.
-\item You can alter this preference in the Test Results preference page.
-\item In the command line client, test executions are automatically relevant unless you include the parameter \bxshell{-r}.
-\end{itemize}
-\textbf{MAC OSX no longer in BETA}
-\begin{itemize}
-\item We have now removed the BETA status of our MAC support.
-\item Please be aware that pure SWT tests are not supported on MAC systems.
-\item Testing RCP \gdauts{} also has some limitations on MAC, e.g. the action to select a value from a combo box does not work, and there are problems with the selection of tabs by their values.
-\item The license server will now run on MAC machines, as long as the development kit for the environment is installed.
-\end{itemize}
-
-\subsection{Other information}
-\textbf{Compatibility with 4.0}
-\begin{itemize}
-\item The \gddb{} is compatible with version 4.0, so your 4.0 \gddb{} can continue to be used with 4.1.
-%\item We do, however, recommend exporting all \gdprojects{} with the old version and reimporting them into the new version.
-\item The server and client components have been changed, so these will need to be reinstalled for 4.1.
-\item There have been no changes to the license mechnism or license administrator - you do not need to reinstall your license server.
-\end{itemize}
-\textbf{Eclipse plugin removed}
-\begin{itemize}
-\item The functionality to run \app{} as an Eclipse plugin has been removed.
-\end{itemize}
-\textbf{HTML actions deprecated}
-\begin{itemize}
-\item The action \bxname{follow link} in HTML is deprecated. Use the action \bxname{click} on \bxname{Graphics Component} instead to follow links.
-\item The action \bxname{select window} is also deprecated, and has not yet been replaced with a new action in this release.
-\end{itemize}
-\textbf{New \gddb{} configurations in DB Configuration}
-\begin{itemize}
-\item We have added separate \gddb{} configurations in the DB Configuration Tool for Oracle 8,9 and 10 as well as the embedded \gddb{} and Oracle XE.
-\item There are also two new options: MySQl and Postgresql. These are shown as unsupported: we have tested that \app{} can connect to them and open \gdprojects{}, but do not let our full tests run on them at this time.
-\end{itemize}
-\textbf{New colors for \gdcases{}}
-\begin{itemize}
-\item The unbound modules are now colored blue to make them easier to distinguish from other \gdcases{}.
-\item We have also made \gdcases{} that cannot be directly edited slightly grayer to make it easier to see which \gdcases{} are editable.
-\end{itemize}
-
-\subsection{Known issues}
-
-\textbf{Console output for DBTool}
-\begin{itemize}
-\item The DBTool does not yet produce an output when parameters are false or when errors occur.
-\end{itemize}
-
-\textbf{Edit parameters dialog}
-\begin{itemize}
-\item When editing parameters via the edit parameters dialog, it is currently necessary to save the \gdcase{} and reopen it to see the changes in the \gdpropview{}.
-\end{itemize}
-\textbf{Merging component names in the \gdomeditor{}}
-\begin{itemize}
-\item At the moment, the merging of component names does not work in the \gdomeditor{}.
-\item You can use the \gdcompnamebrowser{} to merge component names instead.
-\end{itemize}
-
-\makeatletter
-\section{Release Notes for \app{} 4.0.01205}
-\makeatother
-\subsection{New features and developments}
-\textbf{New implementation for HTML testing}
-\begin{itemize}
-\item We have a new implementation for the testing of HTML \gdauts{}.
-\item The new HTML toolkit is multi-browser compatible and has been tested for Windows (for IE6 and higher and for Firefox 2 and higher), Linux (Firefox 2 and higher) and Mac (Firefox 2 and higher and Safari 3 and higher).
-\item Firefox 3.6 is not yet supported.
-\item The new implementation also supports the testing of dynamic components.
-\item Please be aware that Frames and IFrames are not yet supported in this new implementation.
-
-\end{itemize}
-
-\textbf{New handling for starting \gdauts{} from within \app{}}
-\begin{itemize}
-\item It is now possible to start multiple \gdauts{} from \app{}.
-\item Each \gdaut{} now receives an ID which can be used to differentiate between various \gdauts{} (or instances of the same \gdaut{}) for object mapping, observation, and test execution.
-\item Some buttons that were previously on the toolbar have been moved to the \gdtestsuitebrowser{} and the new \app{}unautview{}.
-\end{itemize}
-
-\textbf{New gdrun option to start \gdauts{} independently of \app{}}
-\begin{itemize}
-\item \gdauts{} can now be started in one of two ways.
-\item They can be started as in previous versions via an \gdaut{} configuration. There is also a new option to start an \gdaut{} without an \gdaut{} configiration, independently of \app{}.
-\item For this, you can use the command \bxname{gdrun} with parameters for toolkit, \gdaut{} ID etc.
-\item This option is not currently available for HTML or SWT \gdauts{}.
-\end{itemize}
-
-\textbf{New running \gdauts{} view}
-\begin{itemize}
-\item There is a new view in the specification perspective which shows a list of running \gdauts{}.
-\item The \gdauts{} are shown using their ID.
-\item Via this view, you can start \gdsuites{} and stop \gdauts{}.
-\end{itemize}
-
-\textbf{Testing different \gdauts{} in one test}
-\begin{itemize}
-\item Being able to start multiple \gdauts{} and the new \bxname{gdrun} command mean that it is now possible to test multiple \gdauts{} (or instances of the same \gdaut{}) in one test.
-\item \gdsuites{} can now be combined to \gdjobs{}. A \gdjob{} executes each \gdsuite{} on the specified \gdaut{}.
-\item This feature is currently only available for \gdauts{} that are written with the same toolkit (e.g. Swing) or when the \gdproject{} toolkit is set to concrete (i.e. no specific actions for particular toolkits are used in the test).
-\item All \gdauts{} to be tested in a \gdjob{} must have been started using the \bxname{gdrun} command.
-\end{itemize}
-\textbf{New \app{} reporting perspective}
-\begin{itemize}
-\item \app{} has a new reporting perspective. After every test run, the test results are now stored in the \gddb{}. Both detailed results and a test result summary are saved.
-\item The test result summaries are shown in the new \gdtestsummaryview{}. You can use this view to sort and filter your test results.
-\item The test result details can be automatically removed from the \gddb{} after a specified number of days. This feature can be activated and configured in the preferences.
-\end{itemize}
-\textbf{Generation of test result statistics}
-\begin{itemize}
-\item From the \gdtestsummaryview{}, you can create \app{} BIRT reports of your test runs.
-\item There is a selection of example reports available in the \gdtestsummaryview{}.
-\item You can also use a BIRT designer to create your own reports.
-\item The built-in BIRT reports can currently only be used with an Oracle Database.
-\end{itemize}
-
-\textbf{Duplicate \gdaut{} configuration}
-\begin{itemize}
-\item To ease the configuration of multiple \gdauts{}, there is now the option to duplicate an existing \gdaut{} configuration.
-\end{itemize}
-\textbf{New action: take screenshot of active window}
-\begin{itemize}
-\item There is a new action in the concrete toolkit to take a screenshot not of the whole screen, but of the currently active window.
-\end{itemize}
-\textbf{New action: check property on figure}
-\begin{itemize}
-\item For the RCP toolkit, there is a new action to check the property of a figure in GEF editors.
-\end{itemize}
-\textbf{Timestamps in test result reports}
-\begin{itemize}
-\item The HTML and XML test reports have been extended so that timestamps for each step are documented.
-\end{itemize}
-\textbf{Mac BETA Support}
-\begin{itemize}
-\item The Mac Version is still in beta status.
-\item Pure SWT \gdauts{} cannot be started by \app{} on Mac systems. RCP \gdauts{}, however, can be.
-\end{itemize}
-\textbf{New options for the DBTool}
-\begin{itemize}
-\item The DBTool has two new options: \bxshell{-deleteall} deletes all \gdprojects{} (and test results) in the \gddb{}. \bxshell{-keepsummary} leaves the test result summaries in the \gddb{} when a \gdproject{} is deleted.
-
-\end{itemize}
-
-\subsection{Information}
-\textbf{Altered XML Scheme for extensions to \app{}}
-\begin{itemize}
-\item We have made a small change to the XML scheme for \app{} extensions.
-\item In the \bxname{ComponentConfiguration.xml} the tag \bxshell{componentClass} has changed.
-\item Instead of specifying your component class as:
-\begin{quote}
-\verb+<componentClass>javax.swing.JComboBox+
-
-\verb+</componentClass>+
-\end{quote}
-Use the following:
-\begin{quote}
-\verb+<componentClass name="javax.swing.JComboBox"/>+
-\end{quote}
-\end{itemize}
-\textbf{AUT Starter renamed AUT Agent}
-\begin{itemize}
-\item To reflect the change in behavior of the \app{} server component, we have renamed the AUT Starter to AUT Agent.
-\item The commands to start and stop the Agent have also changed. See the user manual for more details.
-\end{itemize}
-\textbf{Fix for GEF Editor figure recognition}
-\begin{itemize}
-\item We have fixed an error for figure recognition in multi-page GEF editors.
-\item Figures are now correctly found if an editor has multiple tabs.
-\end{itemize}
-\textbf{New licenses}
-\begin{itemize}
-\item \app{} 4.0 requires new licenses. You can request your new license from the support team.
-\end{itemize}
-\textbf{New support service available}
-\begin{itemize}
-\item We have updated our support service so that customers can also purchase premium support for questions relating to test environment, process etc.
-\item Full details about the new support service are in the license agreement and in the \app{} shop.
-\end{itemize}
-
-\textbf{Alternative classloading}
-\begin{itemize}
-\item We have made some changes to the classloading for \gdauts{} started with \app{}.
-\item Should you notice any problems when starting your \gdauts{} with the new version, you can switch to the old classloading mechanism by performing one of the following:
-\begin{itemize}
-\item Setting an environment variable \bxshell{GD\_USE\_CLASSIC\_CL=true}
-\item Setting the Java property \bxshell{-DGD\_USE\_CLASSIC\_CL=true}
-\end{itemize}
-\end{itemize}
-
-\textbf{Running the License Server on Windows 7}
-\begin{itemize}
-\item When starting the License Server as a Service (for example, after installing GUIdancer with administrator access rights), the firewall must be explicitly configured to allow incoming traffic for the License Server process.
-\end{itemize}
-
-\subsection{Known issues}
-\textbf{Refresh problem in the \gdcompnamebrowser{} when renaming components in the \gdomeditor{}}
-\begin{itemize}
-\item After renaming a component name in the \gdomeditor{}, the \gdcompnamebrowser{} is not refreshed until the \gdproject{} is re-opened.
-\item We recommend renaming component names in the \gdcompnamebrowser{} until this issue is resolved.
-\end{itemize}
-
-\textbf{Incorrect display of technical component name}
-\begin{itemize}
-\item In some cases, a technical name may be collected from the \gdaut{} in the form \bxname{guidancer.concrete.button} instead of \bxname{Button/Radio Button/Checkbox}, for example.
-\item This is a problem with the display of the component name and does not in any way affect the object recognition or mapping.
-\end{itemize}
-
-\textbf{Pausing and stopping test execution during restart \gdaut{}}
-\begin{itemize}
-\item There is a known issue which occurs when a test is paused or stopped while the action \bxname{restart \gdaut{}} is being executed.
-\item Doing this leads to the buttons on the toolbar being incorrectly disabled. Please wait until the action is finished before stopping or pausing the test, to avoid this problem.
-\end{itemize}
-
-\textbf{Start Incomplete Test Suite is no longer supported}
-\begin{itemize}
-\item The action to start an incomplete Test Suite is no longer supported.
-\end{itemize}
-
-\textbf{Closing an \gdaut{} in the observation mode}
-\begin{itemize}
-\item \app{} cannot currently stop an \gdaut{} during a test.
-\item If the observation mode is running, and you close the \gdaut{} (e.g. via File-Close), this leads to the object mapping for the \gdcase{} being falsely marked as incomplete.
-\end{itemize}
-
-\textbf{Default \gdehandlers{} in \gdsuites{}: RETURN}
-\begin{itemize}
-\item The \bxname{return} default \gdehandler{} in \gdsuites{} does not yet exist, although this is documented.
-\end{itemize}
-
-\textbf{Automatically ending Check Mode}
-\begin{itemize}
-\item When recording a verification step in Observation Mode, the button \bxname{Ok, but stop Checking} does not end the Check Mode. The mode must be ended manually.
-\end{itemize}
-
-\clearpage
-\makeatletter
-\section{Release Notes for \app{} 3.2.02004}
-\makeatother
-This release is a patch for version 3.2.01081 which contains updates to the documentation.
-\subsection{Information}
-\textbf{New software license version}
-\begin{itemize}
-\item The software license that you agree to when you download or install \app{} has been updated.
-\item You can read the new license in the installation directory in the \bxname{guidancer} folder.
-\end{itemize}
-
-
-\textbf{New object mapping shortcut}
-\begin{itemize}
-\item The standard shortcut to collect objects from an \gdaut{} in the \gdomm{} is now: \bxkey{Ctrl+Shift+Q}. You can see and change this shortcut in the preferences.
-\end{itemize}
-
-\makeatletter
-\section{Release Notes for \app{} 3.2.01081}
-\makeatother
-
-\subsection{New features and developments}
-\textbf{New actions}
-\begin{itemize}
-\item This version of \app{} contains a variety of new actions to:
-\begin{itemize}
-\item Check enablement, existence and selection of items in context-menus.
-\item Open context menus with any button (right, left or middle).
-\item Check the existence of tabs.
-\item Check the value of a specific tab.
-\item Check the existence of a value in a row or column in a table.
-\item Check the editability of a selected cell in a table.
-\item Check the editability of a cell at a specific mouse position.
-\item Refresh components in a web application.
-\end{itemize}
-\end{itemize}
-
-\textbf{Collecting components using clicks}
-\begin{itemize}
-\item Customers whose \gdauts{} cannot accept keystrokes can now set the object mapping preferences to collect components using clicks.
-\end{itemize}
-\textbf{Improvement for dynamic web testing}
-\begin{itemize}
-\item \app{} now contains a new option in the object mapping preferences to refresh components in a web application. This can be used during object mapping to recognize newly added components since the last refresh.
-\item This action is also available as a \gdstep{} to achieve the same effect during a test.
-\end{itemize}
-\textbf{Switching \gddb{} and \gddb{} configurations}
-\begin{itemize}
-\item There is a new \gddb{} configuration tool to select, add and configure \gddb{}s for use with \app{}. More information on this is available in the Installation Manual.
-\item It is now possible to switch between \gddb{}s or \gddb{} users in the \app{} client. This saves having to restart the client to switch the \gddb{}.
-\end{itemize}
-
-\textbf{Windows 7 supported}
-\begin{itemize}
-\item \app{} 3.2 has been tested with Windows 7 as well as XP and Vista.
-\end{itemize}
-
-\subsection{Other information}
-
-\textbf{Administrator privileges required for configuration tools and license administrator}
-\begin{itemize}
-\item The configuration tool, the \gddb{} configuration tool and the license administrator may require administrative privileges.
-\item Run these tools as an administrator to be able to configure your \app{} installation.
-\end{itemize}
-
-\textbf{New \gdagent{} commands under Linux}
-\begin{itemize}
-\item The \gdagent{} commands under Linux have changed.
-\item To start the \gdagent{}, enter: \bxshell{./AutStarter (-p <port number>)}
-\item To stop the \gdagent{}, enter: \bxshell{stopAutStarter.sh}
-\end{itemize}
-
-\textbf{Fixed issue with a component name}
-\begin{itemize}
-\item We have fixed a falsely calculated component name in the unbound modules for dragging and dropping list items.
-\item The affected component names are: \bxname{nn\_dragSource\_lst} and \bxname{nn\_dropTarget\_lst}.
-\item Customers who have used unbound modules containing these component names should take the following steps to update their \gdprojects{}:
-\begin{enumerate}
-\item Open the \gdproject{} and switch the version of the unbound modules from 3.1 to 3.2.
-\item Find the places where the affected component names were used in the test by using F7 on the unbound modules for dragging and dropping in lists.
-\item Any affected places will display a message in the \gdcompnamesview{}: \bxname{no component type exists!}.
-\item Make a note of the component name that you used here.
-\item Make a small change in the \gdtestcaseeditor{} to make the editor ''dirty'' and save the editor.
-\item Add the component name that you previously used in this \gdcase{} and save the editor again.
-\end{enumerate}
-\end{itemize}
-\subsection{Known issues}
-\textbf{Selection of multiple SWT list items under Linux}
-\begin{itemize}
-\item There is an issue in some versions of GTK and the selection of multiple list items.
-\item Items further down in the list may be clicked falsely. This is a known error in GTK.
-\end{itemize}
-
-\section{Release Notes for \app{} 3.1.2003}
-This release is a patch for the previous 3.1.01019 version. For more information about the 3.1 version, see the previous release notes.
-\subsection{New features and developments}
-\textbf{New timer actions}
-\begin{itemize}
-\item \bxname{Application - Start Timer} - This action allows you to start a timer with a given name. In addition to the timer name this action requires a variable in which to store the start time.
-\item \bxname{Application - Read Timer} - Use this action to read the current value of a timer you have started and store this value in a given variable.
-\item \bxname{Application - Check Numeric Values} - With this action two numeric values can be compared. Valid comparison methods are e.g. "less-than" or "greater-or-equal-than".
-\end{itemize}
-
-\subsection{Other information}
-\textbf{Fix for GEF figure recognition}
-\begin{itemize}
-\item The figure recognition in the GEF toolkit has been corrected.
-\item Figure positions will now be correctly calculated regardless of which side the palette is on.
-\end{itemize}
-
-\textbf{Connect to \gdagent{}}
-\begin{itemize}
-\item The issue in the previous release with connecting to the \gdagent{} and then disconnecting before a \gdproject{} was open has now been fixed.
-\end{itemize}
-
-\textbf{Wait for Window actions}
-\begin{itemize}
-\item The Swing implementation for the \bxname{Application - Wait for Window...} actions has been modified.
-\item The modification fixes an issue with the occasional incorrect evaluation of the window status.
-\item Affected actions are: \bxname{Wait for Window}, \bxname{Wait for Window to Close} and \bxname{Wait for Window Activation}
-\end{itemize}
-
-\makeatletter
-\section{Release Notes for \app{} 3.1.01019}
-\makeatother
-
-\subsection{New features and developments}
-
-\textbf{GEF support}
-\begin{itemize}
-\item We have added support for the figure canvas and figure testing for RCP applications.
-\item See the section in the user manual on GEF testing and the reference manual for details on testing applications with GEF components. %\bxextref{\gduserman}{user,gefaccess}.
-\item GEF actions can not be recorded using the observation mode.
-\end{itemize}
-
-\textbf{Eclipse 3.5 compatibility - important information}
-\begin{itemize}
-\item \app{} is now compatible with Eclipse 3.5 and can test applications written in 3.5.
-\item Existing customers wishing to test Eclipse applications on more than one platform should activate the new \bxname{generate names} option in the \gdaut{} settings. %\bxextref{\gduserman}{user,Defineaut}.
-\item This option improves the generated names and object recognition for buttons in RCP wizards and dialogs. It is deactivated in existing \gdprojects{} and activated in new ones. Activating this option will mean remapping affected components from the \gdaut{}.
-\item The affected components can easily be found by filtering the \gdomeditor{} using this text: \\
-\bxshell{*swt.widgets.button}. \\
-Delete the affected components and then refresh the \gdomeditor{}. You will then see the component names which need to be remapped.
-\end{itemize}
-
-\textbf{Mac OSX BETA support}
-\begin{itemize}
-\item Testers wishing to try out the BETA for Mac support are invited to do so.
-\item The license manager cannot run on a Mac system; it must be installed on a Windows or Linux system.
-\end{itemize}
-
-\textbf{New actions}
-\begin{itemize}
-\item The action \bxname{Copy to clipboard} has been added to the \bxname{Application} component. This can be used on native dialogs during the test, to enter filepaths etc.
-\item We have updated the actions on tables to allow selection and checking of cells by the header value as well as the column index. Entering an integer will result in the column being found based on its position. Entering a string will mean that the column is found based on its header text. Header texts currently only support the \bxname{equals} operator. Old table actions are now deprecated and should be exchanged for the new actions.
-\item \app{} can now select and check the selection of checkboxes on SWT Trees.
-\end{itemize}
-
-\textbf{RCP component name generation}
-\begin{itemize}
-\item In the \gdaut{} settings, there is a new option for RCP \gdauts{} to generate unique names for buttons in dialogs and wizards. %\bxextref{\gduserman}{user,Defineaut}.
-\item This option is automatically on for new \gdprojects{} and deactivated in existing \gdprojects{}.
-\item If your tests must be platform independent, we recommend activating this option for your existing \gdprojects{}. Information on how to easily remap the affected components is available above in the section on Eclipse 3.5.
-\end{itemize}
-
-\textbf{Filter in \gdomeditor{}}
-\begin{itemize}
-\item The \gdomeditor{} now has a text filter like the browsers.
-\item Unlike the browsers, the \gdomeditor{} filter searches based on both the text and the technical component type in the editor.
-\end{itemize}
-
-\textbf{Control decoration}
-\begin{itemize}
-\item We have added control decoration to various components in the user interface to help new users understand some of the more advanced options with \app{}.
-\end{itemize}
-
-\textbf{New cheat sheet}
-\begin{itemize}
-\item A new cheat sheet on using \gdehandlers{} is available in the help menu.
-\end{itemize}
-
-\textbf{Show unused \gdcases{}}
-\begin{itemize}
-\item There is a new filter in the \gdtestcasebrowser{} -- show unused \gdcases{}.
-\item Use this filter to refactor and clean up your tests by identifying which \gdcases{} are no longer referenced.
-\end{itemize}
-
-\textbf{Show where used on \gdcases{}}
-\begin{itemize}
-\item This action now also works on \gdcases{} from reused \gdprojects{}.
-\item This means that you can easily search for references to deprecated unbound modules from our \gdcase{} library in your \gdproject{} to switch them.
-\end{itemize}
-
-\textbf{New preferences}
-\begin{itemize}
-\item In the \app{} preferences, you can choose to hide the information behind \gdstep{} names.% \bxextref{\gduserman}{user,gdprefs}.
-\item You can also deactivate the option to show the original \gdcase{} name behind a new name when you rename a reused \gdcase{}. %\bxextref{\gduserman}{user,gdprefs}.
-\end{itemize}
-
-\subsection{Other Information}
-
-\textbf{Coolbars and Toolbars in Eclipse}
-\begin{itemize}
-\item To fix an issue with the recognition of coolbars in Eclipse, we have introduced better component recognition for coolbars and toolbars.
-\item Customers testing RCP applications will have to remap their toolbar and coolbar buttons unless these have been given names by the development team.
-\end{itemize}
-
-
-\textbf{Whitespaces in commands}
-\begin{itemize}
-\item The action \bxname{execute external command} has been changed to allow whitespaces in commands and in parameters.
-\item Relative paths can be written simply with the white spaces included. You will need to use quotes (") around the path or command if you are using path fragments (e.g. \bxshell{./} or \bxshell{../}) for the relative path.
-\item When using absolute paths, use quotes (") around the command or parameter containing the whitespaces.
-
-\end{itemize}
-For example, instead of: \\
-\verb+C:\Program Files\guidancer\guidancer.exe +
-\newline
-\verb+-data C:\Program Files\guidancer\ws +
-\newline
-enter:\\
-\verb+"C:\Program Files\guidancer\guidancer.exe" +
-\newline
-\verb+ -data "C:\Program Files\guidancer\ws" +
-\begin{itemize}
-\item In Linux, quotes may be placed around the command and the parameter. Windows cmd.exe can only accept quotes in either the parameter or the command.
-\item Please bear in mind that strings within the quotes are not checked for validity.
-
-\end{itemize}
-
-\textbf{Absolute and relative searches in tables}
-\begin{itemize}
-\item The relative search in tables now searches starting from the next item after the selected item.
-\item Move actions in the table search relative to the mouse position.
-\end{itemize}
-
-\textbf{Keyboard mappings}
-\begin{itemize}
-\item We have added documentation how to add keyboard mapping files to the RCP accessor.
-\end{itemize}
-
-\textbf{New parameters for the keyboard modifiers}
-\begin{itemize}
-\item The parameters \bxkey{Cmd} and \bxkey{Mod} have been added to actions for key combinations to allow testing on MAC systems, and to ensure platform-independent testing across Windows, Unix and MAC systems.
-\end{itemize}
-
-\subsection{Known issues}
-
-\textbf{Connecting to the \gdagent{}}
-\begin{itemize}
-\item When no \gdproject{} is open, connecting to the \gdagent{} and disconnecting again results in no longer being able to connect to the \gdagent{} until \app{} is restarted.
-\end{itemize}
-
-\textbf{Exit Code 11}
-\begin{itemize}
-\item Restarting an RCP \gdaut{} may cause an error in Eclipse which displays an error code 11.
-\item This can be hindered by updating the launcher to Eclipse version 3.3 and using the parameter \verb+ --launcher.supressErrors (Executable) +.
-\end{itemize}
-
-\textbf{Click in component}
-\begin{itemize}
-\item We do not recommend using the percentages 0 and 100 for click in component when scrollbars surround the component.
-\end{itemize}
-
-\textbf{GIJ and OpenJDK}
-\begin{itemize}
-\item These are not supported by \app{}.
-\end{itemize}
diff --git a/org.eclipse.jubula.documentation/releasenotes/en/tex/summary.tex b/org.eclipse.jubula.documentation/releasenotes/en/tex/summary.tex
new file mode 100644
index 000000000..e69de29bb
--- /dev/null
+++ b/org.eclipse.jubula.documentation/releasenotes/en/tex/summary.tex

Back to the top