Difference between revisions of "Diagrams"

From HaskellWiki
Jump to navigation Jump to search
m (Update homepage links)
 
(50 intermediate revisions by 5 users not shown)
Line 1: Line 1:
  +
[[Category:Graphics]]
The '''diagrams''' library provides an embedded domain-specific language (EDSL) for creating simple pictures and diagrams in Haskell
 
  +
[[Category:Libraries]]
  +
[[Category:Packages]]
   
  +
[[Image:Diagrams-logo.png]]
* [http://code.haskell.org/diagrams/ Homepage]
 
* [http://byorgey.wordpress.com/ Blog]
 
* [http://hackage.haskell.org/cgi-bin/hackage-scripts/package/diagrams HackageDB]
 
   
 
The [http://diagrams.github.io 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://diagrams.github.io 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.
== Rewrite ==
 
   
  +
* [[/FAQ|Frequently asked questions]]
=== Core DSL ===
 
  +
* [[/Install|Installation instructions]]
  +
* [[/Contributing|How to contribute]]
  +
* [[/Projects|Projects]]: who is working on what.
  +
* [[/GSoC|Google Summer of Code projects]]
   
  +
* [[/Converting|Converting between different diagrams types]]
* graphical primitives
 
** path (moveTo, lineTo, cubic bezier, quadratic bezier, arcTo, etc)
 
*** boolean operations
 
*** morphing
 
** text
 
** circle
 
** ellipse
 
** rectangle
 
** polygon
 
** polyline
 
*** imho there should be primitive shape typeclass, so that shapes like circles and rectangles have a "convertToPath" function. Backends like SVG can then choose to convert shapes like a rectangle to a polygon or to a SVG rectangle
 
* graphical attributes
 
** fill
 
*** paint
 
**** solid color, gradient, pattern
 
*** fill rule
 
**** evenOdd, nonZero
 
** stroke
 
*** paint
 
**** solid color, gradient, pattern
 
*** width
 
*** line cap
 
*** line join
 
*** miter limit
 
*** dash
 
**** offset
 
**** array
 
** marker symbols
 
** effects
 
*** shadow, blur, turbulence
 
* constraint solving
 
* animations/pages/frames
 
   
  +
* [[/Support|Which versions of GHC and Haskell Platform are supported]]
=== Modules/Extensions ===
 
   
  +
* [[/Dev/Migrate0.7|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
* shapes and symbols
 
  +
* [[/Dev/Migrate1.0|0.7 to 1.0 migration]]: Description of API changes that may affect diagrams 0.7 code, with explanations of how to migrate to 1.0
** stars, [http://local.wasp.uwa.edu.au/~pbourke/geometry/supershape/ supershape], [http://www.jroller.com/aalmiray/entry/jsilhouette_0_3_released symbols]
 
  +
* [[/Dev/Migrate1.1|1.0 to 1.1 migration]]: Description of API changes that may affect diagrams 1.0 code, with explanations of how to migrate to 1.1
* diagrams
 
  +
* [[/Dev/Migrate1.2|1.1 to 1.2 migration]]: Description of API changes that may affect diagrams 1.1 code, with explanations of how to migrate to 1.2
** histograms, density plots
 
  +
* [[/Dev/Migrate1.3|1.2 to 1.3 migration]]: Description of API changes that may affect diagrams 1.2 code, with explanations of how to migrate to 1.3
  +
* [[/Dev/Migrate1.4|1.3 to 1.4 migration]]: Description of API changes that may affect diagrams 1.3 code, with explanations of how to migrate to 1.4
   
  +
* [[/Dev|Developer wiki]]: notes on wanted features, style guidelines, best practices, etc.
=== Input/Output ===
 
   
  +
* [[/Dev/BuildStatus|Build status]] of all diagrams packages at a glance.
Many Haskell graphic libraries are tied to a specific rendering backend (Cairo, OpenGL, libGD etc) which makes collaboration and reuse of code and data structures very hard or impossible.
 
  +
* [http://diagrams.github.io/backend-tests/all-index.html Current test case results for backends side-by-side.]
 
Also some dependencies are hard to fulfill. Cairo is very difficult to install on Mac OS 10.6. If you just need to generate PDF diagrams, you could choose the pure HPDF library where e.g. Hieroglyph can not be installed because of its Cairo dependence.
 
 
==== Output ====
 
* interactive drawing via Cairo
 
* PDF export via pure [http://hackage.haskell.org/package/HPDF HPDF]
 
* EPS export
 
* SWF export
 
* LaTeX export
 
* exotic backends
 
** generate Java2d or [http://www.processing.org/ Processing] source code
 
 
==== Input ====
 
* pure Haskell PNG import via [http://hackage.haskell.org/package/pngload pngload]
 
* pure Haskell SVG import
 
 
== Inspiration ==
 
 
* [[Applications_and_libraries/Graphics]]
 
 
=== Related non-Haskell projects ===
 
 
* [http://asymptote.sourceforge.net/ Asymptote]
 
* [http://had.co.nz/ggplot2/ ggplot2]
 
* [http://www.tug.org/metapost.html MetaPost]
 
* [http://www.texample.net/tikz/examples/ TikZ]
 
 
=== Food for thought ===
 
 
* [http://www.adobe.com/devnet/pdf/pdf_reference.html PDF reference]
 
* [http://www.w3.org/TR/SVG11/ SVG reference]
 
* [http://www.adobe.com/devnet/swf/pdf/swf_file_format_spec_v10.pdf SWF reference]
 

Latest revision as of 13:28, 13 August 2018


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
  • 0.7 to 1.0 migration: Description of API changes that may affect diagrams 0.7 code, with explanations of how to migrate to 1.0
  • 1.0 to 1.1 migration: Description of API changes that may affect diagrams 1.0 code, with explanations of how to migrate to 1.1
  • 1.1 to 1.2 migration: Description of API changes that may affect diagrams 1.1 code, with explanations of how to migrate to 1.2
  • 1.2 to 1.3 migration: Description of API changes that may affect diagrams 1.2 code, with explanations of how to migrate to 1.3
  • 1.3 to 1.4 migration: Description of API changes that may affect diagrams 1.3 code, with explanations of how to migrate to 1.4
  • Developer wiki: notes on wanted features, style guidelines, best practices, etc.