The diagrams-contrib package

[Tags:bsd3, library, test]

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

[Skip to Readme]


Versions,,, 0.6,,,,, 0.6.1, 0.7, 1.0,, 1.1,, 1.1.1,,,,,, 1.1.2,,,,,,, 1.3.0,,,,,,,,,,,,, 1.4,
Change log CHANGES.markdown
Dependencies arithmoi (==0.4.*), base (>=4.2 && <4.7), circle-packing (==0.1.*), colour (>=2.3.1 && <2.4), containers (>0.4 && <0.6), data-default (>=0.3 && <0.6), diagrams-core (==0.6.*), diagrams-lib (==0.6.*), force-layout (==0.2.*), lens (>=3.8 && <4), MonadRandom (>=0.1.8 && <0.2), mtl (>=2.0 && <2.2), split (>=0.2.1 && <0.3), vector-space (>=0.7 && <0.9) [details]
License BSD3
Author Various
Maintainer Various; see individual modules
Category Graphics
Home page
Bug tracker
Source repository head: git clone
Uploaded Sat Mar 23 19:38:56 UTC 2013 by BrentYorgey
Distributions LTSHaskell:, NixOS:, Stackage:, Tumbleweed:
Downloads 13347 total (116 in the last 30 days)
0 []
Status Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI




Maintainer's Corner

For package maintainers and hackage trustees

Readme for diagrams-contrib

Readme for diagrams-contrib-0.6.1

Build Status

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. You may also want to use diagrams-haddock to include some example images in the Haddock documentation; see the diagrams-haddock documentation and take a look at other modules in the package for examples.

  • 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.

For more general information on contributing to the diagrams project, see the Contributing page on the diagrams wiki.