Diagrams/Dev

Guidelines

• How to contribute

• Coding style guidelines. It's not worth being super picky about these, but in general they are quite good.

• git commit message guidelines.

• Guidelines for reviewing and merging code. For those with push access to one or more repos in the github diagrams organization.

Design notes

• Text support
• Notes on extending support for paths
• Bounding functions
• Freeze, attribute transformation, and the backend API
• Notes on the representation of transformations: linear and affine transformations, inverse, transpose, etc.
• Arrows
• Gradients

Releases

• 0.5 to 0.6 migration
• 0.6 to 0.7 migration
• 0.7 to 1.0 migration

Miscellaneous links

• [1]: ticket re: GHC error messages with ambiguous type variables. This comes up a lot when using diagrams, it would be nice to see this ticket resolved.

• travis-ci build status of all diagrams packages.

• byorgey's time spent hacking on diagrams: