Difference between revisions of "Diagrams/Dev"
< Diagrams
Jump to navigation
Jump to search
(info about darcs -> git migration) |
|||
| (16 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | == Guidelines == |
||
| − | == Darcs/patch-tag -> git/github migration == |
||
| + | * [[Diagrams/Contributing|How to contribute]] |
||
| − | All the diagrams repos are now migrated to github, under the [https://github.com/diagrams diagrams organization]. |
||
| + | * [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. |
||
| − | What still needs to be done: |
||
| + | * [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html git commit message guidelines]. |
||
| − | * Import issues from [http://code.google.com/p/diagrams/issues/list Google code] into github. However, the github issue trackers are per-repo, so we'll have to import according to 'Component' tag (and the component tags may need to be cleaned up on google code first). fryguybob thinks maybe we can modify [https://github.com/arthur-debert/google-code-issues-migrator/blob/master/migrateissues.py#L100 this] to get something that will work. |
||
| + | |||
| − | * Update any and all references to patch-tag to point to github instead. This includes: |
||
| + | * [[/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]. |
||
| − | ** The diagrams website |
||
| − | ** The user manual and tutorial? |
||
| − | ** The packages themselves (in the .cabal files) |
||
== Design notes == |
== Design notes == |
||
| Line 18: | Line 16: | ||
* [[/Freezing|Freeze, attribute transformation, and the backend API]] |
* [[/Freezing|Freeze, attribute transformation, and the backend API]] |
||
* [[/Transformations|Notes on the representation of transformations: linear and affine transformations, inverse, transpose, etc.]] |
* [[/Transformations|Notes on the representation of transformations: linear and affine transformations, inverse, transpose, etc.]] |
||
| + | * [[/Arrows|Arrows]] |
||
| + | * [[/Gradients|Gradients]] |
||
| + | |||
| + | == Links/resources == |
||
| + | |||
| + | Links to software, papers, documentation, etc. which is helpful or relevant. |
||
| + | |||
| + | * [http://cairographics.org/manual/ cairo reference manual] |
||
| + | |||
| + | * [http://potrace.sourceforge.net/ potrace], a nice raster -> vector library. Even has a [http://potrace.sourceforge.net/potrace.pdf detailed description of the algorithms used]. |
||
| + | * [http://homepages.cwi.nl/~ploeg/papers/padl131.pdf A Library for Declarative Resolution-Independent 2D Graphics] (PADL 2013) |
||
| + | * [http://conal.net/Pan/papers.htm Pan (Conal Elliott)] |
||
== Releases == |
== Releases == |
||
* [[/Migrate0.6|0.5 to 0.6 migration]] |
* [[/Migrate0.6|0.5 to 0.6 migration]] |
||
| + | * [[/Migrate0.7|0.6 to 0.7 migration]] |
||
| + | * [[/Migrate1.0|0.7 to 1.0 migration]] |
||
== Miscellaneous links == |
== Miscellaneous links == |
||
* [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: |
||
| + | <p>[https://www.beeminder.com/byorgey/goals/diagrams http://beeminder.com/byorgey/diagrams-thumb.png]</p> |
||
Revision as of 15:35, 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
Links/resources
Links to software, papers, documentation, etc. which is helpful or relevant.
- potrace, a nice raster -> vector library. Even has a detailed description of the algorithms used.
- A Library for Declarative Resolution-Independent 2D Graphics (PADL 2013)
- Pan (Conal Elliott)
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:
