Diagrams: Difference between revisions
m (→Core DSL) |
m (Update homepage links) |
||
(47 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
[[Category:Graphics]] | |||
[[Category:Libraries]] | |||
[[Category:Packages]] | |||
[[Image:Diagrams-logo.png]] | |||
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. | ||
* [[/FAQ|Frequently asked questions]] | |||
* [[/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]] | ||
* [[/Support|Which versions of GHC and Haskell Platform are supported]] | |||
* | * [[/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 | ||
* | * [[/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/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 | |||
* [[/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 | |||
* [[/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. | |||
* [[/Dev/BuildStatus|Build status]] of all diagrams packages at a glance. | |||
* [http://diagrams.github.io/backend-tests/all-index.html Current test case results for backends side-by-side.] | |||
* [http:// | |||
Latest revision as of 13:28, 13 August 2018
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.