wires:Functional reactive programming library
Modules
[Index]
Flags
Manual Flags
| Name | Description | Default |
|---|---|---|
| examples | Build the example programs | Disabled |
Use-f <flag> to enable a flag, or-f -<flag> to disable that flag.More info
Downloads
- wires-0.2.1.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Candidates
- No Candidates
| Versions[RSS] | 0.1.0,0.2.0,0.2.1 |
|---|---|
| Change log | CHANGELOG.md |
| Dependencies | base (>=4.8 && <5),deepseq (>=1.4 && <1.5),mtl (>=2.0 && <2.3),profunctors (>=5.0 && <5.3),semigroupoids (>=5.0 && <5.3),these (>=0.7 && <0.8) [details] |
| License | BSD-3-Clause |
| Copyright | Copyright 2017 Ertugrul Söylemez |
| Author | Ertugrul Söylemez <esz@posteo.de> |
| Maintainer | Ertugrul Söylemez <esz@posteo.de> |
| Uploaded | byesz at2018-04-15T22:21:16Z |
| Category | Control,FRP |
| Home page | https://github.com/esoeylemez/wires |
| Bug tracker | https://github.com/esoeylemez/wires/issues |
| Source repo | head: git clonehttps://github.com/esoeylemez/wires.git |
| Distributions | |
| Reverse Dependencies | 2 direct, 0 indirect [details] |
| Executables | wires-ping-pong, wires-feedback |
| Downloads | 2211 total (11 in the last 30 days) |
| Rating | 2.0 (votes: 1)[estimated byBayesian average] |
| Your Rating |
|
| Status | Docs uploaded by user Build status unknown[no reports yet] |
Readme for wires-0.2.1
[back to package description]Wires
This is a functional reactive programming library for interactiveapplications with the following features:
heavy focus on real-time applications like games and simulations,
very small core abstraction,
efficient in both time and space.
Until a proper tutorial has been written, please check out theexamples directory. If you have questions, join #haskell-game onirc.freenode.net. If you would like to report a bug or request afeature, pleasefile anissue.
Module overview
The library is split into two roles:applications andcontrollers.An application developer models interactions and implements reactivesystems, i.e. the application logic. A controller developer implementsthe glue between the application and the real world, i.e. how events andtime-varying values map to actual things on the screen or in thenetwork. The module structure reflects that distinction:
Control.Wire: Application language (basically core + utils)Control.Wire.Controller: Controller languageControl.Wire.Core: Core application languageControl.Wire.Internal: You should never need this moduleControl.Wire.Utils: Extra application utilities
Modules not listed here are highly experimental and should not be used.
If you are asking yourself whether you are an application or acontroller developer: at this early stage of development you areprobably both, which means that you will write the application as wellas connect its inputs and outputs to the real world.