Personal tools

Functional Reactive Programming

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
m (Behaviors)
(People: Added Ertugrul Söylemez.)
 
Line 90: Line 90:
 
* [http://www.cs.nott.ac.uk/~nhn/ Henrik Nilsson]
 
* [http://www.cs.nott.ac.uk/~nhn/ Henrik Nilsson]
 
* [http://mcis.western.edu/~jpeterson/ John Peterson]
 
* [http://mcis.western.edu/~jpeterson/ John Peterson]
  +
* Ertugrul Söylemez
   
 
[[Category:FRP|*]]
 
[[Category:FRP|*]]

Latest revision as of 22:54, 12 November 2013

Functional Reactive Programming (FRP) integrates time flow and compositional events into functional programming. This provides an elegant way to express computation in domains such as interactive animations, robotics, computer vision, user interfaces, and simulation.


Contents

[edit] 1 Introduction

The original formulation of Functional Reactive Programming can be found in the ICFP 97 paper Functional Reactive Animation by Conal Elliott and Paul Hudak.

[edit] 1.1 Behaviors

Traditionally a widget-based user interface is created by a series of imperative actions. First an action is invoked to create an edit widget, then additional actions can be invoked to read its current content, set it to a specific value or to assign an event callback for when the content changes. This is tedious and error-prone.

A better way to represent an edit widget's content is a time-varying value, called a behavior. The basic idea is that a time-varying value can be represented as a function of time:

newtype Behavior a =
    Behavior {
      at :: Time -> a
    }
 
myName :: Behavior Text
 
myName `at` yesterday

This is only a theoretical model, because a time-varying value can represent something impure like the content of an edit widget, the current value of a database entry as well as the system clock's current time. Using this model the current content of an edit widget would be a regular first class value:

myEditWidget :: Behavior Text

In most frameworks there is an applicative interface for behaviors, such that you can combine them easily:

liftA2 (<>) myEdit1 myEdit2
The result is a time-varying value that represents the concatenation of
myEdit1
and
myEdit2
. This could be the value of a third widget, a label, to display the concatenation. The following is a hypothetical example:
do edit1 <- editWidget
   edit2 <- editWidget
   label <- label (liftA2 (<>) edit1 edit2)
   {- ... -}

Without behaviors you would have to write event callback actions for the edit widgets to update the label's content. With behaviors you can express this relationship declaratively.

[edit] 1.2 Events

To do

[edit] 2 Libraries


[edit] 3 Publications and talks


[edit] 4 Blog posts


[edit] 5 People