Difference between revisions of "Diagrams"
Jump to navigation
Jump to search
(Remove info about Diagrams 0.5 with GHC 7.6) |
|||
| (88 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:Graphics]] |
||
| ⚫ | |||
| + | [[Category:Libraries]] |
||
| + | [[Category:Packages]] |
||
| + | [[Image:Diagrams-logo.png]] |
||
| − | * [http://code.haskell.org/diagrams/ Homepage] |
||
| − | * [http://hackage.haskell.org/cgi-bin/hackage-scripts/package/diagrams diagrams on 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. |
||
| − | == Ideas for the rewrite == |
||
| + | * [[/FAQ|Frequently asked questions]] |
||
| − | 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. |
||
| + | * [[/Install|Installation instructions]] |
||
| + | * [[/Contributing|How to contribute]] |
||
| + | * [[/Projects|Projects]]: who is working on what. |
||
| + | * [[/GSoC|Google Summer of Code projects]] |
||
| + | * [[/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 |
||
| − | 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/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 |
||
| + | * [[/Dev|Developer wiki]]: notes on wanted features, style guidelines, best practices, etc. |
||
| − | A rewrite of diagrams should include separate packages for: |
||
| + | |||
| − | * high-level code (constraint solving) |
||
| + | * [[/Dev/BuildStatus|Build status]] of all diagrams packages at a glance. |
||
| − | * low-level graphical primitives (fill, stroke, gradients, rectangles, polygons, paths, etc) |
||
| + | * [http://projects.haskell.org/diagrams/backend-tests/all-index.html Current test case results for backends side-by-side.] |
||
| − | ** imho there should be primitive shape typeclass like circles and rectangles having a "convertToPath" function. Backends like SVG can then choose to use a primitive like a rectangle as a polygon or a rectangle |
||
| − | ** boolean combination of paths |
||
| − | * input/output backends |
||
| − | ** pure Haskell SVG loader |
||
| − | ** interactive painting via Cairo |
||
| − | ** pure Haskell PDF conversion via HPDF |
||
| − | ** pure Haskell PNG conversion via ??? |
||
| − | ** etc. |
||
Revision as of 22:18, 8 January 2014
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
- 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.