Difference between revisions of "Diagrams"

From HaskellWiki
Jump to navigation Jump to search
(link to new 0.6 -> 0.7 migration page)
(Bug tracker(s) URL changed)
Line 7: Line 7:
 
The [http://projects.haskell.org/diagrams diagrams framework] provides an embedded domain-specific language (EDSL) for declarative drawing.
 
The [http://projects.haskell.org/diagrams diagrams framework] provides an embedded domain-specific language (EDSL) for declarative drawing.
   
This is the diagrams wiki, for collecting tips and tricks, examples, information about related projects, and any other related information. If you are looking for more structured documentation (tutorial, user manual, API reference), see the [http://projects.haskell.org/diagrams diagrams web page]. There is also a [http://code.google.com/p/diagrams/issues/list bug tracker].
+
This is the diagrams wiki, for collecting tips and tricks, examples, information about related projects, and any other related information. If you are looking for more structured documentation (tutorial, user manual, API reference), see the [http://projects.haskell.org/diagrams diagrams web page]. There are also [https://github.com/diagrams/diagrams-lib/issues?state=open bug] [https://github.com/diagrams/diagrams-core/issues?state=open trackers] for different parts of the project.
   
 
* [[/FAQ|Frequently asked questions]]
 
* [[/FAQ|Frequently asked questions]]

Revision as of 08:55, 13 November 2013


Diagrams-logo.png

The diagrams framework provides an embedded domain-specific language (EDSL) for declarative drawing.

This is the diagrams wiki, for collecting tips and tricks, examples, information about related projects, and any other related information. If you are looking for more structured documentation (tutorial, user manual, API reference), see the diagrams web page. There are also bug trackers for different parts of the project.

  • 0.6 to 0.7 migration: Description of API changes that may affect diagrams 0.6 code, with explanations of how to migrate to 0.7
  • Developer wiki: notes on wanted features, style guidelines, best practices, etc.