A cookbook for using the model-view controller user interface paradigm in Smalltalk-80
Journal of Object-Oriented Programming
FUDGETS: a graphical user interface in a lazy functional language
FPCA '93 Proceedings of the conference on Functional programming languages and computer architecture
Composing the User Interface with Haggis
Advanced Functional Programming, Second International School-Tutorial Text
Interactive Functional Objects in Clean
IFL '97 Selected Papers from the 9th International Workshop on Implementation of Functional Languages
wxHaskell: a portable and concise GUI library for haskell
Haskell '04 Proceedings of the 2004 ACM SIGPLAN workshop on Haskell
Relational lenses: a language for updatable views
Proceedings of the twenty-fifth ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems
iTasks 2: iTasks for end-users
IFL'09 Proceedings of the 21st international conference on Implementation and application of functional languages
iData for the world wide web – programming interconnected web forms
FLOPS'06 Proceedings of the 8th international conference on Functional and Logic Programming
GiN: a graphical language and tool for defining itask workflows
TFP'11 Proceedings of the 12th international conference on Trends in Functional Programming
Defining multi-user web applications with itasks
CEFP'11 Proceedings of the 4th Summer School conference on Central European Functional Programming School
| Hi-index | 0.00 |
The iTask system is a combinator library written in Clean offering a declarative, domain-specific language for defining workflows. From a declarative specification, a complete multi-user, web-enabled, workflow management system (WFMS) is generated. In the iTask paradigm, a workflow is a definition in which interactive elements are defined by editors on model values (abstracting from concrete GUI implementation details). The order of their appearance is calculated dynamically using combinator functions (abstracting from concrete synchronisation details). Defining interactive elements and the order of their appearance are also major concerns when programming GUI applications. For this reason, the iTask paradigm is potentially suited to program GUI applications as well. However, the iTask system was designed for a different application domain and lacks a number of key features to make it suited for programming GUI applications. In this paper, we identify these key features and show how they can be added to the iTask system in an orthogonal way, thus creating a new paradigm for programming GUI applications.