Difference between revisions of "Diagrams"

From HaskellWiki
Jump to navigation Jump to search
Line 8: Line 8:
 
== Rewrite ==
 
== Rewrite ==
   
=== Similar non-Haskell projects ===
+
=== Related non-Haskell projects ===
   
 
* [http://asymptote.sourceforge.net/ Asymptote]
 
* [http://asymptote.sourceforge.net/ Asymptote]
Line 14: Line 14:
 
* [http://www.texample.net/tikz/examples/ TikZ]
 
* [http://www.texample.net/tikz/examples/ TikZ]
   
=== Similar Haskell projects ===
+
=== Related Haskell projects ===
   
 
* [http://hackage.haskell.org/package/Chart Chart]
 
* [http://hackage.haskell.org/package/Chart Chart]
  +
* [http://hackage.haskell.org/package/gd gd]
 
* [http://www.haskell.org/haven/ Haven]
 
* [http://www.haskell.org/haven/ Haven]
 
* [http://hackage.haskell.org/package/Hieroglyph Hieroglyph]
 
* [http://hackage.haskell.org/package/Hieroglyph Hieroglyph]
  +
* [http://hackage.haskell.org/package/HPlot HPlot]
  +
* [http://hackage.haskell.org/package/hps hps]
  +
* [http://hackage.haskell.org/package/OpenVG OpenVG]
   
 
=== Ideas ===
 
=== Ideas ===

Revision as of 12:02, 23 October 2009

The diagrams library provides an embedded domain-specific language (EDSL) for creating simple pictures and diagrams in Haskell


Rewrite

Related non-Haskell projects

Related Haskell projects

Ideas

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.

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.

A rewrite of diagrams should include separate packages for:

  • high-level code
    • constraint solving
    • high-level diagrams
  • low-level code
    • graphical primitives
      • text, rectangles, polygons, paths, stars, symbols
      • 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
      • boolean operations of paths
    • graphical attributes
      • fill, stroke, arrows, shadow
  • input/output backends
    • pure Haskell SVG loader
    • interactive painting via Cairo
    • pure Haskell PDF conversion via HPDF
    • pure Haskell PNG conversion via ???
    • etc.