Personal tools

Diagrams/Dev

From HaskellWiki

< Diagrams(Difference between revisions)
Jump to: navigation, search
(info about darcs -> git migration)
(Links/resources)
(16 intermediate revisions by one user not shown)
Line 1: Line 1:
== Darcs/patch-tag -> git/github migration ==
+
== Guidelines ==
  
All the diagrams repos are now migrated to github, under the [https://github.com/diagrams diagrams organization].
+
* [[Diagrams/Contributing|How to contribute]]
  
What still needs to be done:
+
* [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.
  
* Import issues from [http://code.google.com/p/diagrams/issues/list Google code] into githubHowever, 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.
+
* [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html git commit message guidelines].
* Update any and all references to patch-tag to point to github instead.  This includes:
+
 
** The diagrams website
+
* [[/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 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

Contents

1 Guidelines

2 Design notes

3 Links/resources

Links to software, papers, documentation, etc. which is helpful or relevant.

4 Releases

5 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.
  • byorgey's time spent hacking on diagrams:

diagrams-thumb.png