Author: buildbot
Date: Wed Jul 13 21:40:57 2016
New Revision: 992725
Log:
Staging update by buildbot for taverna
Modified:
websites/staging/taverna/trunk/cgi-bin/ (props changed)
websites/staging/taverna/trunk/content/ (props changed)
websites/staging/taverna/trunk/content/documentation/interaction/index.html
Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 13 21:40:57 2016
@@ -1 +1 @@
-1752543
+1752544
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 13 21:40:57 2016
@@ -1 +1 @@
-1752543
+1752544
Modified:
websites/staging/taverna/trunk/content/documentation/interaction/index.html
==============================================================================
--- websites/staging/taverna/trunk/content/documentation/interaction/index.html
(original)
+++ websites/staging/taverna/trunk/content/documentation/interaction/index.html
Wed Jul 13 21:40:57 2016
@@ -195,64 +195,64 @@ Instead it shows <a class="alert-link" h
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
<h2 id="interacting-with-a-workflow-in-your-browser">Interacting with a
workflow in your browser<a class="headerlink"
href="#interacting-with-a-workflow-in-your-browser" title="Permanent
link">¶</a></h2>
-<p>Many workflows, when run, require interaction with a user.
-This can be to enter data values, confirm that intermediate results are OK to
proceed with the
- run, or to control the functionality of a service. </p>
+<p>Many workflows, when run, require interaction with a user.
+This can be to enter data values, confirm that intermediate results are OK to
proceed with the
+ run, or to control the functionality of a service.</p>
<h3 id="beanshells">Beanshells<a class="headerlink" href="#beanshells"
title="Permanent link">¶</a></h3>
-<p>When running a workflow in <a href="/download/workbench">Taverna
Workbench</a> you can use beanshells
+<p>When running a workflow in <a href="/download/workbench">Taverna
Workbench</a> you can use beanshells
to show Java swing components. Taverna Workbench includes a set of
pre-defined beanshells to,
for example, <a
href="http://dev.mygrid.org.uk/wiki/display/taverna/Ask";>Ask</a> the user for
data.</p>
<h3 id="biovel-interaction-service">BioVeL interaction service<a
class="headerlink" href="#biovel-interaction-service" title="Permanent
link">¶</a></h3>
-<p>If you run your workflow in a portal or on a <a
href="/download/server">server</a>, then using beanshells
- for interaction will not work. Attempts to use Swing will either fail or,
worse,
+<p>If you run your workflow in a portal or on a <a
href="/download/server">server</a>, then using beanshells
+ for interaction will not work. Attempts to use Swing will either fail or,
worse,
open dialogs on the machine where the workflow is running.</p>
<p>To support interaction with workflows running on a server, the <a
href="http://www.biovel.eu";>BioVeL</a>
- project developed a new
- <a
href="http://dev.mygrid.org.uk/wiki/display/taverna/Interaction+service";>interaction
service</a>.
-This interaction service allows users to interact with a running workflow
within a standard web
- browser.
-The interaction can be as simple as acknowledging a message,
- or as complex as controlling a tool running on a remote machine.
-The interaction can be parameterized by data from the workflow and can return
data from the
+ project developed a new
+ <a
href="http://dev.mygrid.org.uk/wiki/display/taverna/Interaction+service";>interaction
service</a>.
+This interaction service allows users to interact with a running workflow
within a standard web
+ browser.
+The interaction can be as simple as acknowledging a message,
+ or as complex as controlling a tool running on a remote machine.
+The interaction can be parameterized by data from the workflow and can return
data from the
browser to the workflow.</p>
-<iframe src="http://www.youtube.com/embed/S9X6E4PdFcM?start=60";
frameborder="0"
+<iframe src="http://www.youtube.com/embed/S9X6E4PdFcM?start=60"; frame
border="0"
width="420" height="315"></iframe>
<p>Interactions have already been used for many purposes. These include:</p>
<ul>
-<li>to manipulate data inside <a href="http://openrefine.org/";>Open Refine</a>
(previously Google Refine),</li>
-<li>to show information on maps and</li>
-<li>to show the results of species population modelling</li>
+<li>manipulating data inside <a href="http://openrefine.org/";>Open Refine</a>
(previously Google Refine),</li>
+<li>showing information on maps, and</li>
+<li>showing the results of species population modelling.</li>
</ul>
<h2 id="notification-of-interaction-requests">Notification of interaction
requests<a class="headerlink" href="#notification-of-interaction-requests"
title="Permanent link">¶</a></h2>
-<p>One of the advantages of running workflows on a server is that you do not
need to monitor them
- constantly.
-However, you then need a way to be alerted that a workflow requires an
interaction.
-The interaction service uses <a
href="http://en.wikipedia.org/wiki/Atom_(standard)">ATOM</a> feeds to send
- out notifications.
-ATOM feeds can be read by many different clients, including mobile phone Apps
and mail readers.
+<p>One of the advantages of running workflows on a server is that you do not
need to monitor them
+ constantly.
+However, you then need a way to be alerted that a workflow requires an
interaction.
+The interaction service uses
[ATOM](http://en.wikipedia.org/wiki/Atom_(standard) feeds to send
+ out notifications.
+ATOM feeds can be read by many different clients, including mobile phone Apps
and mail readers.
The ATOM message will include a link to the HTML page for the interaction
required.</p>
<h2 id="usage-scenarios">Usage scenarios<a class="headerlink"
href="#usage-scenarios" title="Permanent link">¶</a></h2>
-<p>The interaction service combines standard protocols such as ATOM and HTML.
+<p>The interaction service combines standard protocols such as ATOM and HTML.
As a result there are many ways in which users can interact with their
workflow run.</p>
<h3 id="on-your-phone">On your phone<a class="headerlink"
href="#on-your-phone" title="Permanent link">¶</a></h3>
-<p>Most modern mobile/cell phones support web browsers and also ATOM feed
Apps.
-If you subscribe to the ATOM feed for a workflow run,
- then you can open the HTML page in the phone's browser, interact with the
workflow run,
+<p>Most modern mobile/cell phones support web browsers and also ATOM feed Apps.
+If you subscribe to the ATOM feed for a workflow run,
+ you can open the HTML page in the phone's browser, interact with the
workflow run,
and then go back to whatever you were doing.</p>
-<p>This has been demonstrated for simple interactions; complex interactions
can be limited a
+<p>This has been demonstrated for simple interactions. Complex interactions
can be limited by a
phone's screen resolution.</p></p>
<h3 id="inside-another-web-page">Inside another web page<a class="headerlink"
href="#inside-another-web-page" title="Permanent link">¶</a></h3>
-<p>It is common to use a web page to run workflows on a server.
-This could be, for example, within a
- <a href="/documentation/taverna-player">Taverna Player</a>,
- or a more complex portal such as the Taverna 2.4 Server Demonstrator.
-When a workflow is run, the page creates a subscription to the run&'s ATOM
feed.
-When a notification is sent on the feed, the page can then show the
interaction.
-An example of this is demonstrated in this video.</p>
+<p>It is common to use a web page to run workflows on a server.
+This could be, for example, within a
+ <a href="/documentation/taverna-player">Taverna Player</a>,
+ or a more complex portal such as the Taverna 2.4 Server Demonstrator.
+When a workflow is run, the page creates a subscription to the run's ATOM feed.
+When a notification is sent on the feed, the page can then show the
interaction.
+An example of this is demonstrated in the video.</p>
<h3 id="in-the-workbench">In the workbench<a class="headerlink"
href="#in-the-workbench" title="Permanent link">¶</a></h3>
-<p>The Taverna Workbench is also able to run interaction services.
-When a notification is sent, it opens up the HTML page in your preferred
browser.
+<p>The Taverna Workbench is also able to run interaction services.
+When a notification is sent, it opens up the HTML page in your preferred
browser.
You can choose to use <a title="Jetty"
href="http://www.eclipse.org/jetty/";>Jetty</a> to handle the feed and hosting
of pages, or an external site.</p></p>
<h2>Installing the interaction service</h2>
