< Diagrams(Difference between revisions)
(→Releases: link to 1.0 migration page)
(→Guidelines: add link to git commit message guidelines)
Revision as of 12:27, 6 December 2013
- Coding style guidelines. It's not worth being super picky about these, but in general they are quite good.
- Guidelines for reviewing and merging code. For those with push access to one or more repos in the github diagrams organization.
2 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.
- : 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: