Hackage :: [Package]

evdev-streamly: Bridge for working with evdev and streamly

[ bsd3, library, streamly, system ] [ Propose Tags ] [ Report a vulnerability ]

Functions for working with streams of input events. Often much more pleasant than working in a more imperative style.

[Skip to Readme]

Modules

[Index] [Quick Jump]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.0.1.0, 0.0.2.0, 0.0.2.1
Change log CHANGELOG.md
Dependencies base (>=4.11 && <5), bytestring (>=0.10 && <0.13), containers (>=0.6.2 && <0.8), evdev (>=2.1 && <2.4), extra (>=1.6.18 && <1.8), filepath-bytestring (>=1.4.2 && <1.5), mtl (>=2.2 && <2.4), rawfilepath (>=1.0 && <1.2), streamly (>=0.9 && <0.11), streamly-fsnotify (>=1.1.1 && <1.2), unix (>=2.8 && <2.9) [details]
License BSD-3-Clause
Author George Thomas
Maintainer George Thomas
Category Streamly, System
Home page https://github.com/georgefst/evdev
Source repo head: git clone git://github.com/georgefst/evdev.git
Uploaded by GeorgeThomas at 2024-08-15T16:53:38Z
Distributions
Downloads 372 total (12 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2024-08-15 [all 1 reports]

Readme for evdev-streamly-0.0.2.1

[back to package description]

Evdev + Streamly

This library provides provides a high level Streamly-based interface to evdev, for working with streams of input events.

It doesn't re-export anything, so you will almost certainly also need to depend directly on both of those packages.

Many of the functions in this library make use of concurrency, so you will probably want --ghc-options=-threaded for any executables you build, in order to enable the threaded runtime, and get the expected behaviour. This should be on by default in a near-future version of GHC.

Why streamly?

Compared to other Haskell streaming libraries, I've found streamly to have a remarkably easy-to-use API, and the best, simplest support for concurrency. For example, merging concurrent streams of events, from different devices, is trivial.

If you wish to use this library alongside conduit, pipes etc. then see the Interoperation section of Streamly's tutorial.