The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
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[@]metanet.ch.

gginnards: Explore the Innards of 'ggplot2' Objects

Extensions to 'ggplot2' providing low-level debug tools: statistics and geometries echoing their data argument. Layer manipulation: deletion, insertion, extraction and reordering of layers. Deletion of unused variables from the data object embedded in "ggplot" objects.

Version: 0.2.0-1
Depends: R (≥ 4.0.0), ggplot2 (≥ 3.4.0)
Imports: utils, methods, rlang (≥ 0.4.0), stringr (≥ 1.4.0), magrittr (≥ 1.5), tibble (≥ 2.1.0)
Suggests: knitr (≥ 1.24), rmarkdown (≥ 1.14), sf (≥ 0.9), pryr (≥ 0.1.4)
Published: 2024-11-14
DOI: 10.32614/CRAN.package.gginnards
Author: Pedro J. Aphalo ORCID iD [aut, cre]
Maintainer: Pedro J. Aphalo <pedro.aphalo at helsinki.fi>
BugReports: https://github.com/aphalo/gginnards/issues
License: GPL-2 | GPL-3 [expanded from: GPL (≥ 2)]
URL: https://docs.r4photobiology.info/gginnards/, https://github.com/aphalo/gginnards
NeedsCompilation: no
Materials: README NEWS
CRAN checks: gginnards results

Documentation:

Reference manual: gginnards.pdf
Vignettes: User Guide: 1 Debugging ggplots (source, R code)
User Guide: 2 Manipulating ggplots (source, R code)

Downloads:

Package source: gginnards_0.2.0-1.tar.gz
Windows binaries: r-devel: gginnards_0.2.0-1.zip, r-release: gginnards_0.2.0-1.zip, r-oldrel: gginnards_0.2.0-1.zip
macOS binaries: r-release (arm64): gginnards_0.2.0-1.tgz, r-oldrel (arm64): gginnards_0.2.0-1.tgz, r-release (x86_64): gginnards_0.2.0-1.tgz, r-oldrel (x86_64): gginnards_0.2.0-1.tgz
Old sources: gginnards archive

Reverse dependencies:

Reverse imports: bayesplay, RevGadgets
Reverse suggests: ggpmisc, ggpp

Linking:

Please use the canonical form https://CRAN.R-project.org/package=gginnards 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.