The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.
An 'R' interface to 'pikchr' (<https://pikchr.org>, pronounced “picture”), a 'PIC'-like markup language for creating diagrams within technical documentation. Originally developed by Brian Kernighan, 'PIC' has been adapted into 'pikchr' by D. Richard Hipp, the creator of 'SQLite'. 'pikchr' is designed to be embedded in fenced code blocks of Markdown or other documentation markup languages, making it ideal for generating diagrams in text-based formats. This package allows R users to seamlessly integrate the descriptive syntax of 'pikchr' for diagram creation directly within the 'R' environment.
Version: | 1.0 |
Depends: | R (≥ 4.0) |
Imports: | dplyr, knitr, brio, htmltools, rlang, purrr, stringr, rsvg |
Suggests: | kableExtra, tidyverse |
Published: | 2024-12-02 |
DOI: | 10.32614/CRAN.package.pikchr |
Author: | Andre Leite [aut, cre], Hugo Vaconcelos [aut], Richard Hipp [ctb], Brian Kernighan [ctb] |
Maintainer: | Andre Leite <leite at castlab.org> |
License: | GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
URL: | <https://github.com/StrategicProjects/pikchr> |
NeedsCompilation: | yes |
Materials: | README NEWS |
CRAN checks: | pikchr results |
Reference manual: | pikchr.pdf |
Vignettes: |
Examples (source, R code) Pikchr User Manual (source, R code) |
Package source: | pikchr_1.0.tar.gz |
Windows binaries: | r-devel: pikchr_1.0.zip, r-release: pikchr_1.0.zip, r-oldrel: pikchr_1.0.zip |
macOS binaries: | r-release (arm64): pikchr_1.0.tgz, r-oldrel (arm64): pikchr_1.0.tgz, r-release (x86_64): pikchr_1.0.tgz, r-oldrel (x86_64): pikchr_1.0.tgz |
Old sources: | pikchr archive |
Please use the canonical form https://CRAN.R-project.org/package=pikchr to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.