1. Overview
RadChart for Windows Phone is a versatile charting component that has been specifically designed for the mobile environment.
It offers unmatched performance regarding loading time, drawing capabilities and realtime updates.
Its intuitive object model and public API allow complex charts to be easily setup either in XAML or through code.
The control is completely data aware and may work in bound or unbound mode, depending on the requirements.
Chart types (or series) are organized in hierarchies, depending on the coordinate system, used to plot data points –
for example we have RadCartesianChart (using Cartesian coordinate system) and RadPieChart (using radial coordinate system).
Note 

The following references are required in order to use RadChart for Windows Phone:

2. Architecture
A charting component in general is used to visualize (or plot) some data in a humanreadable way through different representations like lines, areas, bars pies, etc. Each series
has a collection of data points – the data equivalent of a 2D point – and knows how to visualize them. Different series types may process certain types of data points – for
example categorical series may contain categorical data points. Data points may be added directly to series or a data binding mechanism may be used to create the appropriate data
points from the raw data.
2.1. RadCartesianChart
As the name hints, this concrete chart control uses the Cartesian coordinate system to plot the data points in its chart series. The X and Y axes define how each point’s
coordinates in the plot area are calculated.
2.1.1. Axes
Available are the following axes:
2.1.1.1. Categorical
Arranges the plotted data points in categories where the key of each category is the point’s value (if available) for that axis or its index within the points collection. The
point’s coordinate, specified by this axis is discrete and is calculated depending on the size of the category slot where the point resides.
2.1.1.2. Datetime Categorical
Special categorical axis that expects each data point to provide a System.DateTime structure as its value for this axis. The points are grouped by a userdefined datetime
component (Year, Month, Day, etc.) and then the groups are sorted chronologically.
2.1.1.3. Linear
Calculates the coordinate of each data point, depending on the actual numerical value this point provides for the axis. Exposes Minimum and Maximum properties to allow for
explicit definition of the range of values visible on this axis. If these properties are not specified, the axis will automatically calculate the range, depending on the minimum
and maximum data point values.
2.1.1.4. Logarithmic
Special linear axis that will transform each data point value using the logarithm function. Allows numerical data with huge delta between the minimum and the maximum to be
visualized in a readable way.
2.1.1.5. Datetime Continuous
Special axis that expects each data point to provide a System.DateTime structure as its value for this axis. May be thought of as a timeline where the coordinate of each data
point is calculated depending on the position of its associated DateTime on the timeline. The base unit (or the timeline step) of the axis is calculated depending on the smallest
difference between any two dates.
2.1.2. Series
The currently implemented chart series are categorical – they accept Categorical data points and expect a categorical axis to be specified in order to be properly visualized.
Following is a list with all the available series:
2.1.2.1. Area
Data points and the corresponding coordinate axis enclose an area that may be optionally stroked and/or filled.
2.1.2.2. SplineArea
An area, which points are connected with smooth rather than straight segments.
2.1.2.3. Bar
Data points are represented by a box where the height (width) of the box is the distance between the point’s numerical value and the categorical axis that plots the point. Bars
may be either “horizontal” or “vertical” depending on whether the categorical axis is specified as an “Xaxis” or as a “Yaxis”.
2.1.2.4. Line
Data points are connected with straight line segments.
2.1.2.5. Spline
Data points are connected with smooth rather than straight line segments.
2.1.2.6. Scatter Point
Data points are simply plotted in the chart plot area with nothing connecting them. Each scatter data point has X and Y values which make the position
of the data point in the data source and its location on the plot area unrelated. For example the third data point in the data source may appear before the first
data point when plotted. There are also scatter line and scatter area series which behave in the exact same way with the only (visual) difference that the points define a line and and arearespectively.
2.1.2.7. Combined series
Each of the above series of same type may be combined in either stacks or clusters. Combinations are formed when more than one data point from different series falls within a same
category. The “Cluster” combine mode will position such points next to each other while the “Stack” one will arrange such points in a stacklike structure. When stacks are formed,
the numerical axis (if present) will consider each stack as a single entity and its sum will be the actual value used rather than each point’s one.
2.1.2.8. RangeBar
Data points are represented by a box, the height of which is determined by a min value and a max value.
2.1.3. Chart Grid
The Cartesian chart may be optionally decorated with gridlike visuals which support horizontal and vertical lines, associated with axis ticks and horizontal and vertical stripes
– the area between two adjacent ticks.
2.2. RadPieChart
This concrete chart control visualizes its data points using radial coordinate system. Each point is represented as an arc segment where the arc’s length is actually the
percentage this point’s value is from the total sum.
2.3. RadPolarChart
RadPolarChart inherits from RadChart and has a PolarAxis and a RadialAxis. It accepts only PolarSeries objects and plots data points in the polar coordinate system.
2.4. Behaviors
Both chart types (pie and cartesian) have a behaviors collection that accepts ChartBehavior objects. Each object represents a special interaction behavior such as ChartTooltipBehavior,
ChartPanAndZoomBehavior and ChartTrackballBehavior.