Difference between revisions of "DeepArrow"

From HaskellWiki
Jump to: navigation, search
m (Examples)
Line 4: Line 4:
* [http://darcs.haskell.org/packages/DeepArrow/doc/html Read the Haddock docs] (with source code & Comment/Talk links)
* [http://darcs.haskell.org/packages/DeepArrow/doc/html Read the Haddock docs] (with source code & Comment/Talk links)
* Get the code repository: '''<tt>darcs get http://darcs.haskell.org/packages/DeepArrow</tt>'''
* Get the code repository: '''<tt>darcs get http://darcs.haskell.org/packages/DeepArrow</tt>'''
* Or grab a [http://darcs.haskell.org/packages/phooey/dist distribution tarball].
* Or grab a [http://darcs.haskell.org/packages/DeepArrow/dist distribution tarball].
== Introduction ==
== Introduction ==

Revision as of 16:05, 2 February 2007


The DeepArrow library is a framework for composable "editors" of pure values.


By an "editor", I mean a function that targets a transformation at some part of a value, such as the first half of the second half of a value of type (a,(b,c)). In such a case, the transformation being targeted would have type b -> b', and the overall transformation would have type (a,(b,c)) -> (a,(b',c)).

If you've fooled around with arrows, you might guess that the arrow methods first and second having something to do with this game, and you'd be right. The main idea of DeepArrow is to play with compositions of first and second and of an analogous third combinator called result. I was stunned to realize that arbitrarily complex value editors can be made by stringing together compositions of these three combinators and delighted to find that the composition chains directly spell out the paths to the value subpart to be edited.

The DeepArrow library is about "deep function application" in two senses. First, compositions of first, second, and result apply functions deeply inside of values. Second, another set of combinators extract "deep functions" so they can be applied. Combining these two abilities allows a buried function to be applied to a buried argument, with the two contexts being carried along.


See example docs and source code in the library documentation.


The inspiration for value-editing paths came while I was looking for a way for non-programmers to be able to create functional images. I've had a growing intuition over the last fifteen years that media authoring tools can be usefully looked at as environments for functional programming. I'd been wondering how to map a user's gestures into operations on a functional program. Lots of noodling led to ideas of composable interfaces and "tangible values" (term thanks to Sean Seefried) and gestural composition in Eros.

Eros was more complicated than I like, so I started splitting it into pieces:

  • Phooey is a functional GUI library that has much of Eros's GUI implementation techniques, but much more carefully structured than in the Eros paper.
  • DeepArrow has the general notion of "deep application".
  • TV has the algebra of composable interfaces, or visualizations of pure values, and it has tangible values, which are separable combinations of interface and value. It uses Phooey to generate GUIs very simply from interfaces.