Difference between revisions of "Diagrams"
Jump to navigation
Jump to search
m |
|||
| (82 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:Graphics]] |
||
| ⚫ | |||
| + | [[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] |
||
| ⚫ | |||
| + | 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. |
||
| − | == Rewrite == |
||
| + | * [[/FAQ|Frequently asked questions]] |
||
| − | === Ideas === |
||
| + | * [[/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]] |
||
| − | 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. |
||
| + | * [[/Support|Which versions of GHC and Haskell Platform are supported]] |
||
| − | 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. |
||
| + | * [[/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 |
||
| − | A rewrite of diagrams should include separate packages for: |
||
| + | * [[/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 |
||
| − | * high-level code |
||
| + | * [[/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 |
||
| − | ** constraint solving |
||
| + | * [[/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 |
||
| − | ** high-level diagrams |
||
| + | * [[/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 |
||
| − | * low-level code |
||
| + | * [[/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 |
||
| − | ** graphical primitives |
||
| − | *** text, rectangles, polygons, paths, stars, [http://www.jroller.com/aalmiray/entry/jsilhouette_0_3_released 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. |
||
| + | * [[/Dev|Developer wiki]]: notes on wanted features, style guidelines, best practices, etc. |
||
| − | == Inspiration == |
||
| + | * [[/Dev/BuildStatus|Build status]] of all diagrams packages at a glance. |
||
| − | == Food for thought == |
||
| + | * [http://projects.haskell.org/diagrams/backend-tests/all-index.html Current test case results for backends side-by-side.] |
||
| − | |||
| − | * [http://www.adobe.com/devnet/pdf/pdf_reference.html PDF reference] |
||
| − | * [http://www.w3.org/TR/SVG11/ SVG reference] |
||
| − | |||
| − | === Related non-Haskell projects === |
||
| − | |||
| − | * [http://asymptote.sourceforge.net/ Asymptote] |
||
| − | * [http://www.tug.org/metapost.html MetaPost] |
||
| − | * [http://www.texample.net/tikz/examples/ TikZ] |
||
| − | |||
| − | === Related Haskell projects === |
||
| − | |||
| − | * [http://hackage.haskell.org/package/Chart Chart] |
||
| − | * [http://hackage.haskell.org/package/gd gd] |
||
| − | * [http://www.haskell.org/haven/ Haven] |
||
| − | * [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] |
||
Revision as of 20:28, 2 June 2017
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.
- Frequently asked questions
- Installation instructions
- How to contribute
- Projects: who is working on what.
- Google Summer of Code projects
- 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.
- Build status of all diagrams packages at a glance.
- Current test case results for backends side-by-side.