% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/aaa.R, R/facet_edges.R, R/facet_graph.R,
%   R/facet_nodes.R, R/geom_axis_hive.R, R/geom_conn_bundle.R, R/geom_edge.R,
%   R/geom_edge_arc.R, R/geom_edge_bend.R, R/geom_edge_density.R,
%   R/geom_edge_diagonal.R, R/geom_edge_elbow.R, R/geom_edge_fan.R,
%   R/geom_edge_hive.R, R/geom_edge_link.R, R/geom_edge_loop.R,
%   R/geom_edge_parallel.R, R/geom_node_arc_bar.R, R/geom_node_circle.R,
%   R/geom_node_tile.R, R/geom_node_voronoi.R, R/ggproto-classes.R
\docType{data}
\name{StatFilter}
\alias{StatFilter}
\alias{FacetEdges}
\alias{FacetGraph}
\alias{FacetNodes}
\alias{StatAxisHive}
\alias{GeomAxisHive}
\alias{StatConnBundle}
\alias{StatConnBundle2}
\alias{StatConnBundle0}
\alias{GeomEdgePath}
\alias{GeomEdgeParallelPath}
\alias{GeomEdgeSegment}
\alias{GeomEdgeParallelSegment}
\alias{GeomEdgeSpanPath}
\alias{GeomEdgeSpanSegment}
\alias{GeomEdgePoint}
\alias{GeomEdgeTile}
\alias{GeomEdgeBezier}
\alias{GeomEdgeBspline}
\alias{StatEdgeArc}
\alias{StatEdgeArc2}
\alias{StatEdgeArc0}
\alias{StatEdgeBend}
\alias{StatEdgeBend2}
\alias{StatEdgeBend0}
\alias{StatEdgeDensity}
\alias{GeomEdgeDensity}
\alias{StatEdgeDiagonal}
\alias{StatEdgeDiagonal2}
\alias{StatEdgeDiagonal0}
\alias{StatEdgeElbow}
\alias{StatEdgeElbow2}
\alias{StatEdgeElbow0}
\alias{StatEdgeFan}
\alias{StatEdgeFan2}
\alias{StatEdgeFan0}
\alias{StatEdgeHive}
\alias{StatEdgeHive2}
\alias{StatEdgeHive0}
\alias{StatEdgeLink}
\alias{StatEdgeLink2}
\alias{StatEdgeLoop}
\alias{StatEdgeLoop0}
\alias{StatEdgeParallel}
\alias{StatEdgeParallel2}
\alias{StatEdgeParallel0}
\alias{StatNodeArcBar}
\alias{StatNodeCircle}
\alias{GeomNodeTile}
\alias{StatNodeVoronoi}
\alias{ggraph-extensions}
\title{ggraph extensions to ggplot2}
\description{
This help page lists all exported ggproto classes defined by ggraph. In
general these should be of no concern to the user as the main interface to
the functionality is, as with ggplot2, the \verb{geom_*} format. As opposed
to ggplot2 there really aren't any use for separate \verb{stat_*} functions
as they are intimately linked to each geom and mixing and matching stats and
geoms would only cause a lot of trouble.
}
\details{
Many of the \verb{geom_edge_*} geoms comes in different flavors dependent on
the functionality required. There will always be a base geom and some will
have a \code{geom_edge_*0} and \code{geom_edge_*2} version. The base geom
will, in the case of multiple versions, draw the edge as a sequence of small
segments. The different aesthetics will be repeated for each segment and a
counter will be added the enumerates the progression of segments, so that a
gradient of colour or size can be added along the edge by assigning the
respective aesthetic to \code{stat(index)}. \code{geom_edge_*2} will also draw
the edge as segments but will interpolate between the aesthetics at the end
points. This makes it possible for an edge to interpolate node properties of
its end nodes. \code{geom_edge_*2} is less performant than the base geom so
use only when interpolation is needed. \code{geom_edge_*0} is a
high-performance version that usually maps directly to a grid grob. It does
not allow for drawing gradients or interpolations though, so use only for
simple edge drawings.
}
\keyword{datasets}
\keyword{internal}
