|
|
| (23 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | The '''Clean Team''' does its best to deliver reliable software.
| + | If you want to stay informed about the latest development of Clean, you can follow what we do through our Gitlab website. |
| − | It therefore might take some time before a new release is pubished.
| |
| − | On this site we will keep you informed about the latest developments.
| |
| − | Please be patient, software development always takes more time as expected.
| |
| | | | |
| − | | + | On https://gitlab.com/clean-and-itasks/ we host our latest unreleased code, and track progress of new features and bugfixes. |
| − | * the '''iTask''' combinator library for the '''Web'''
| |
| − | | |
| − | At the '''ICFP 2007''' conference we presented '''iTasks''' (see [http://www.st.cs.ru.nl/papers/2007/plar2007-ICFP07-iTasks.pdf]),
| |
| − | a multi-user workflow system for the web.
| |
| − | With this library one can assign tasks to users and control the order in which these tasks have to be performed.
| |
| − | 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 (see [http://www.cs.ru.nl/~rinus/iTaskIntro.html])
| |
| − | | |
| − | The new release of the iTask library we are working on will support:
| |
| − | * Ajax handling of iTasks;
| |
| − | * Client side evaluation of iTasks.
| |
| − | | |
| − | With a simple annotation an iTask will be evaluated on the client instead of on the server.
| |
| − | To make this possible we run full blown Clean applications in the browser as Java applet, making use of the fast '''Sapl''' interpreter (see [http://www.st.cs.ru.nl/papers/2007/janj2007-TFP06-EfficientInterpretationOfSAPL.pdf]).
| |
| − | The system automatically switches between client side and server side evaluation when needed.
| |
| − | | |
| − | We will use and release this new system at the '''AFP-summerschool''' (see [http://www.st.cs.ru.nl/AFP_TFP_2008/])
| |
| − | | |
| − | | |
| − | | |
| − | * the '''Clean Compiler'''
| |
| − | | |
| − | We are adding a new front-end to the Clean compiler that will accept '''Haskell '98''' source code.
| |
| − | | |
| − | Good news for many people, we hope.
| |
| − | | |
| − | Not only there will be another Haskell '98 compiler, which should be one that compiles fast and produces efficient code.
| |
| − | | |
| − | Another important property is that '''''Haskell and Clean code can be mixed'''''!
| |
| − | | |
| − | | |
| − | So, Clean users can make use of Haskell libraries, while Haskell users
| |
| − | can make use of Clean libraries (such as the iTask library) and Clean features (such as uniqueness typing, dynamics, generic programming).
| |
| − | | |
| − | Although many things already work, we don't dare to say anything about the release date.
| |
