The diagrams-contrib package

[Tags: bsd3, library]

A collection of user contributions for diagrams, an embedded domain-specific language for generation of vector graphics.

[Skip to ReadMe]


Versions0.1.0.0,,, 0.6,,,,, 0.6.1, 0.7, 1.0,, 1.1,, 1.1.1,,,,,, 1.1.2,,,,,,, 1.3.0,,,,,,,
Change logCHANGES
Dependenciesbase (>=4.2 && <4.6), colour (>=2.3.1 && <2.4), containers (==0.4.*), data-default (==0.3.*), diagrams-lib (==0.5.*), fclabels (>=1.0.4 && <1.2), force-layout (==0.1.*), mtl (==2.0.*), vector-space (>=0.7 && <0.9) [details]
Home page
Source repositoryhead: darcs get
UploadedFri Mar 16 22:52:03 UTC 2012 by BrentYorgey
DistributionsLTSHaskell:, NixOS:, Stackage:
Downloads9953 total (469 in last 30 days)
0 []
StatusDocs uploaded by user
Build status unknown [no reports yet]




Maintainers' corner

For package maintainers and hackage trustees

Readme for diagrams-contrib-

This package is a repository for user contributions to the diagrams
project ( generation of
specialized diagrams, fun or instructive examples, half-baked ideas,
stuff which is not sufficiently polished or general to go in the
diagrams-lib package but is nonetheless worth sharing.  Any code is
welcome, as long as it conforms to a few simple standards:

  - Code must be released under a BSD3 license (see the LICENSE).

  - You must list yourself as the maintainer.

  - Try to keep external dependencies to a minimum; the goal is for
    diagrams-contrib to be easily installable by as many people as
    possible.  New dependencies will be considered on a case-by-case
    basis.  Dependencies involving the FFI will most likely be
    rejected.  If you have some cool code using diagrams which
    requires big external dependencies, you should release it as a
    separate package rather than including it in diagrams-contrib.

  - There should at minimum be a Haddock comment on the module itself,
    explaining the purpose, giving some examples of use, etc.

  - It must compile with no warnings under -Wall. This may seem a bit
    draconian, but you'll get over it.  If it makes you feel any
    better, you are welcome to turn off specific warnings for your
    module with an {-# OPTIONS_GHC -fno-warn-blah #-} pragma.