Difference between revisions of "ITasks"

From Clean
Jump to navigationJump to search
(Updated highly outdated page)
Line 1: Line 1:
At the '''ICFP 2007''' conference we presented '''iTasks''' [http://www.st.cs.ru.nl/papers/2007/plar2007-ICFP07-iTasks.pdf],
+
At the '''ICFP 2007''' conference we first presented '''iTasks''' [http://www.st.cs.ru.nl/papers/2007/plar2007-ICFP07-iTasks.pdf],
a multi-user workflow system for the web.
+
a multi-user workflow system for the web. Since then the system has evolved from a small library on top of the [[iData]] framework to
With this library one can assign tasks to users and control the order in which these tasks have to be performed.
+
a full fledged workflow language embedded in [[Clean]].  
A user uses a browser to perform the tasks assigned to him or her.
 
The iTask system is therefore also very suited for
 
web programming and web form handling.
 
The tasks are defined on a very high level declarative monadic style.
 
  
Have a look at the iTask pages [http://www.cs.ru.nl/~rinus/iTaskIntro.html].
+
Using '''iTasks''' workflows can be speficied using combinators in a very high level declarative monadic style. Workflows consist
 +
of typed tasks that produce results that can be passed as parameters to other tasks. Workflows are constructed by combining
 +
single steps sequentially or in parallel.
 +
From iTask specifications, executable workflow support systems are generated automatically.
  
The new release of the iTask library we are working on will support:
+
Lately we have been working on version 2 of iTasks that takes the quality of the generated workflow support systems
* Ajax handling of iTasks
+
to a higher level and aims to offer end-users working on tasks a more user-friendly experience. We have presented this new incarnation
* Client side evaluation of iTasks
+
of the iTask system at the '''IFL 2009''' conference, and we are working on getting it ready for an alpha release.
 +
[[File:itasks2-gui.jpg|thumb|The iTask2 GUI]]
  
With a simple annotation an iTask is evaluated on the client instead of on the server.
+
This latest version features:
To make this possible we run full blown Clean applications in the browser as Java applet, making use of the fast '''Sapl''' interpreter [http://www.st.cs.ru.nl/papers/2007/janj2007-TFP06-EfficientInterpretationOfSAPL.pdf].
+
* A highly declarative API for specification of dynamic workflows
The system automatically switches between client side and server side evaluation when needed.
+
* A rich Ajax client interface for working on tasks
 +
* Automatically generated editors for entering and updating data in workflows.
 +
* A JSON based service API for spawning and interacting with running workflow instances
 +
* The possibility to change running workflow instances
  
 +
 +
== Download ==
 
For the [[AFP2008|AFP Summerschool 2008]] we made a special Clean release which includes
 
For the [[AFP2008|AFP Summerschool 2008]] we made a special Clean release which includes
 
the new compiler which can generate SAPL code for execution on the client.
 
the new compiler which can generate SAPL code for execution on the client.
Line 25: Line 30:
 
== Read more ==
 
== Read more ==
 
* [[Workflow examples]]
 
* [[Workflow examples]]
 +
* Rinus' iTask pages [http://www.cs.ru.nl/~rinus/iTaskIntro.html].

Revision as of 09:26, 28 October 2009

At the ICFP 2007 conference we first presented iTasks [1], a multi-user workflow system for the web. Since then the system has evolved from a small library on top of the iData framework to a full fledged workflow language embedded in Clean.

Using iTasks workflows can be speficied using combinators in a very high level declarative monadic style. Workflows consist of typed tasks that produce results that can be passed as parameters to other tasks. Workflows are constructed by combining single steps sequentially or in parallel. From iTask specifications, executable workflow support systems are generated automatically.

Lately we have been working on version 2 of iTasks that takes the quality of the generated workflow support systems to a higher level and aims to offer end-users working on tasks a more user-friendly experience. We have presented this new incarnation of the iTask system at the IFL 2009 conference, and we are working on getting it ready for an alpha release.

The iTask2 GUI

This latest version features:

  • A highly declarative API for specification of dynamic workflows
  • A rich Ajax client interface for working on tasks
  • Automatically generated editors for entering and updating data in workflows.
  • A JSON based service API for spawning and interacting with running workflow instances
  • The possibility to change running workflow instances


Download

For the AFP Summerschool 2008 we made a special Clean release which includes the new compiler which can generate SAPL code for execution on the client.

You can download this release at: http://clean.cs.ru.nl/download/Clean22/windows/Clean2.2-iTasks-AFP2008.zip

Read more