Difference between revisions of "Diagrams/Dev"
< Diagrams
Jump to navigation
Jump to search
m (→Guidelines: add link to contributing page) |
(→Releases: add migration page links) |
||
(19 intermediate revisions by 3 users 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]. |
||
− | |||
− | What still needs to be done: |
||
− | |||
− | * Update any and all references to patch-tag to point to github instead. This includes: |
||
− | ** The diagrams website |
||
− | ** The user manual and tutorial? |
||
− | ** The packages themselves (in the .cabal files) |
||
− | |||
== Guidelines == |
== Guidelines == |
||
Line 15: | 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]. |
||
Line 23: | Line 14: | ||
* [[/Paths|Notes on extending support for paths]] |
* [[/Paths|Notes on extending support for paths]] |
||
* [[/Bounds|Bounding functions]] |
* [[/Bounds|Bounding functions]] |
||
⚫ | |||
* [[/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]] |
||
+ | * [[/Expression|Backend type parameters and the expression problem]] |
||
+ | * [[/Fixpoint|Fixpoint semantics]] |
||
+ | * [[/Constraints|Constraint design notes]] |
||
+ | * [[/AlignedCompose|Aligned composition]] |
||
+ | |||
+ | === Outdated design notes === |
||
+ | |||
+ | Stuff which is no longer current but kept here for historical reference. |
||
+ | |||
⚫ | |||
+ | |||
+ | == 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)] |
||
+ | |||
+ | Misc instructions |
||
+ | |||
+ | * How to add [[/IRCHooks|IRC Hooks]] to repositories in the github diagrams organization |
||
== 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]] |
||
+ | * [[/Migrate1.1|1.0 to 1.1 migration]] |
||
+ | * [[/Migrate1.1|1.0 to 1.1 migration]] |
||
+ | * [[/Migrate1.2|1.1 to 1.2 migration]] |
||
+ | * [[/Migrate1.3|1.2 to 1.3 migration]] |
||
+ | * [[/Migrate1.4|1.3 to 1.4 migration]] |
||
== Miscellaneous links == |
== Miscellaneous links == |
||
Line 35: | Line 58: | ||
* [[/BuildStatus|travis-ci build status]] of all diagrams packages. |
* [[/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> |
||
+ | |||
+ | * [[/ReleaseAutomation| Notes on automating tedious parts of our release process]] |
Latest revision as of 19:39, 16 October 2016
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
- Notes on the representation of transformations: linear and affine transformations, inverse, transpose, etc.
- Arrows
- Gradients
- Backend type parameters and the expression problem
- Fixpoint semantics
- Constraint design notes
- Aligned composition
Outdated design notes
Stuff which is no longer current but kept here for historical reference.
- Freeze, attribute transformation, and the backend API (after the merging of the "units" branch, freeze is no more)
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)
Misc instructions
- How to add IRC Hooks to repositories in the github diagrams organization
Releases
- 0.5 to 0.6 migration
- 0.6 to 0.7 migration
- 0.7 to 1.0 migration
- 1.0 to 1.1 migration
- 1.0 to 1.1 migration
- 1.1 to 1.2 migration
- 1.2 to 1.3 migration
- 1.3 to 1.4 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: