Difference between revisions of "Diagrams/Dev"
< Diagrams
Jump to navigation
Jump to search
m (→Design notes: add link to new page of notes re: transformations) |
m (github migration is complete) |
||
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | == Darcs/patch-tag -> git/github migration == |
||
+ | |||
+ | All the diagrams repos are now migrated to github, under the [https://github.com/diagrams diagrams organization]. I believe that all references (documentation, .cabal files, etc.) have now been updated as well. |
||
+ | |||
+ | == Guidelines == |
||
+ | |||
+ | * [[Diagrams/Contributing|How to contribute]] |
||
+ | |||
+ | * [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. |
||
+ | |||
+ | * [[/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]. |
||
+ | |||
== Design notes == |
== Design notes == |
||
Line 14: | Line 26: | ||
* [http://hackage.haskell.org/trac/ghc/ticket/4921]: 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. |
* [http://hackage.haskell.org/trac/ghc/ticket/4921]: 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. |
||
+ | |||
+ | * [[/BuildStatus|travis-ci build status]] of all diagrams packages. |
||
+ | |||
+ | * byorgey's time spent hacking on diagrams:<br />[https://www.beeminder.com/byorgey/goals/diagrams http://beeminder.com/byorgey/diagrams-thumb.png] |
Revision as of 20:59, 22 October 2012
Darcs/patch-tag -> git/github migration
All the diagrams repos are now migrated to github, under the diagrams organization. I believe that all references (documentation, .cabal files, etc.) have now been updated as well.
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.
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.