UISF is a library for making arrowized GUIs.
This is a framework for creating commandline applications. It provides various features which give a polished feel to your application.
It is designed to encourage you to provide clear documentation and working examples. It implements default 'help' and 'man' commands for your application, which will layout help text and generate Unix-style man pages.
It provides special handling for applications of the form ''program command args'', the style of interaction common in revision control systems. It will dispatch to handler functions that you provide for each command, and also provide command-specific help to the user.
A simple unique identiier, serializable to binary and JSON, and since base32 is a primary encoding, renders in URLs without any further encoding.
This package lets you easily query various facts about the system that your code is running on. Currently, it reports whether the operating system is "Windows" or "Unix", and also the name and version of the Haskell compiler used.
This package implements lots of complicated trickery to determine the build environment. Once built, other packages can query this information without needing to do complex trickery themselves.
See also the included ReadMe.xhtml file.
* If the configure step fails to detect the OS type, the configure step now fails.
* A new file Manual.hs allows you to override the auto-detected platform values with whatever you want. (See ReadMe.xhtml for details.)
* All the platform queries no longer return Maybe values. (This breaks API compatibility, hence the version bump.)
Drive Aho-Corasick machines in Conduit pipelines.
Some simple interactive programs for sending MIDI control messages via ALSA. The GUI uses wxHaskell. Currently we provide these programs:
* Send All Notes Off and All Sounds Off events.
* Show several sliders, that trigger sending MIDI controller messages.
* Show a list widget, that triggers MIDI program changes.
Consume attoparsec parsers via conduit.
This language is a demonstration of the Epic compiler API. It is a dynamically typed language with higher order functions and system interaction (specifically graphics). Requires SDL and SDL_gfx libraries, and their C headers.
Base64-encode and decode streams of bytes.
The binary-conduit package. Allow binary serialization using iterative conduit interface.
Bitstream support for Conduit
This library provides an abstraction of buffered output of byte streams and several convenience functions to exploit it. For example, it allows to efficiently serialize Haskell values to lazy bytestrings with a large average chunk size. The large average chunk size allows to make good use of cache prefetching in later processing steps (e.g. compression) and reduces the system call overhead when writing the resulting lazy bytestring to a file or sending it over the network.
Convert streams of builders to streams of bytestrings.
This package integrates the builders from the blaze-builder package with the enumerator package. It provides infrastructure and enumeratees for incrementally executing builders and pass the filled chunks to a bytestring iteratee.
Includes utilities for checking the host platform, running tests, capturing output, handling errors, comparing runtimes against a baseline, sending mail, running events to a schedule etc.
Tools for working with buildbox benchmark result files.
Buildwrapper is an alternative to scion. It provides services to configure, build and give information on source files to help IDEs manage Haskell projects. You can use buildwrapper to build project and retrieve errors, get outline for each module source, get the type of something inside a source file, get lexer tokens, etc. Buildwrapper is used in the EclipseFP project (Eclipse plugins for Haskell development)
This is the bytestring builder that is debuting in bytestring-0.10.4.0, which should be shipping with GHC 7.8, probably late in 2013. This builder has several nice simplifications and improvements, and more out-of-box functionality than the older blaze-builder.
Note that this package detects which version of bytestring you are compiling against, and if you are compiling against bytestring-0.10.4 or later, will be an empty package.
This package lets the new interface and implementation be used with most older compilers without upgrading bytestring, which can be rather problematic. In conjunction with blaze-builder-0.4 or later, which offers an implementation of blaze-builder in terms of bytestring-builder, this should let most people try the new interface and implementation without causing undue compatibility problems with packages that depend on blaze-builder.
GHC 7.6 did debut an almost identical interface and implementation, but with slightly different module names and organization. Trying to re-export/rename the builder provided with 7.6 did not turn out to be very practical, because this interface includes new functions that rely on Builder internals, which are not exported in 7.6. Furthermore, these module names should be deprecated in 7.10.
Streaming compression/decompression via conduits.
Support for QuickCheck with the detailed Cabal testing interface.
Show more results