Hi, I worked with a lot of chart components for Wpf. I think Telerik offer the best charts architecture that allow to obtain great results in every scenario. After years of use, I think is possible to improve more the global architecture. 1) Series Dataset Charts now works with Points. I think that a better solution require a more abstract structure as a virtual "Dataset". A dataset reuire a type [conform to X axis], tipically X can be a double, a datetime, a label. Dataset return info about poits, tipically: - Min X - Max X Dataset return a DataContext that allow to draw chart: - GetCloserX to an X value [Trackball/Lables...] - GetPoints from/to [Pan/Zoom] This approach is really more efficent and powerfull. In example you can simply define a Dataset as a Formula: Dataset "CosX" based on doubles. MinX=-inf Maxx=+inf GetDataContext from/to -> Return allways 100 points x, cos(x). So you can obtain: - Ultraefficient series using GetDataContext algorithms for specific cases, in example, ordered data. - Trend lines using "Formula" series 2) Only one series, with subtypes. It is really annoying change series type. I think a chart must contains a series and this series can show Line, Area, Split Line, Markers, Columns... To write a good "option panel" that allow user to set Line Thickness, Line Split or standard, Area opacity, Area Color, Marker Type, Marker Colors, Columns Borders... require today a giant work and elaborate code that add and remove serie, reassign points, set z-index, remove and add series in legend... with an incredible useless works in points. 3) More accurate axes definition. Now Chart and Series expose Horizontal and Vertical Axis property. I think this is terrible properties :-). "Horizontal" and "Vertical" is depending chart orientation. Furthermore now, first X/Y axis must be set in chart, others in series. Moving series from an axis to another is really annoying: if new axis is first you must set is null else you must set it... I think Chart must expose XAxesCollection and YAxesCollection. This collections must contains all X and Y axes. Series [and annotation and every object that uses axes] must expose XAxis and YAxis as the Axis object or Axis index. 4) Chart orientation Today a simple chart rotation require a lot of code. The developer must be invert Horizontal and vertical axes, change axes in series and annotations, zoom/pan stop to work... When this is combined with point 2) problems the result is an nightmare. I understand this require a big work and a lot of compatibility problems [Telerik already exposes two charts versions, three is probably a little bit confused]. But if Telerik obtains this features I think it become the most unattainable charts component producer of the world. Decline reason: Most suggestions were tried in the old RadChart and they weren't working very well.