Difference between revisions of "Diagrams/Dev"
< Diagrams
Jump to navigation
Jump to search
(→Releases: link to 1.0 migration page) |
(→Guidelines: add link to git commit message guidelines) |
||
| Line 4: | Line 4: | ||
* [https://github.com/tibbe/haskell-style-guide/blob/master/haskell-style.md Coding style guidelines]. It's not worth being super picky about these, but in general they are quite good. |
* [https://github.com/tibbe/haskell-style-guide/blob/master/haskell-style.md Coding style guidelines]. It's not worth being super picky about these, but in general they are quite good. |
||
| + | |||
| + | * [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html git commit message guidelines]. |
||
* [[/ReviewingAndMerging|Guidelines for reviewing and merging code]]. For those with push access to one or more repos in the [http://github.com/diagrams github diagrams organization]. |
* [[/ReviewingAndMerging|Guidelines for reviewing and merging code]]. For those with push access to one or more repos in the [http://github.com/diagrams github diagrams organization]. |
||
Revision as of 12:27, 6 December 2013
Guidelines
- 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.
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
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:
