API naming inconsistent with charting

2 posts, 0 answers
  1. Charlie
    Charlie avatar
    13 posts
    Member since:
    Apr 2013

    Posted 02 Dec 2013 Link to this post

    Some api naming issues that tend to make working with charting more difficult:

    RadChart is in the Telerik.Windows.Charting.dll and is referred to as "Chart" in the documentation and RadChart in code.

    However, RadChartView is in the Telerik.Windows.Controls.Chart.dll (where you would think to look for RadChart), is referred to in the documentation as "ChartView" and the even less obvious "RadCartesianChart" in code.

    I'm sure as new assemblies and controls get created a need for backward compatibility must be maintained, so the Charting.dll reference is likely a product of that since it appears like new controls get added to the Controls namespace. But something should be considered for Chartview, either correcting the code name (which hurts upgrade-ability) or correcting the documentation (which is always a pain).

    Also, on a related note, the link in the Chart documentation that says "We encourage you to review our new control RadChartView for super-fast visualization of your data." links back to the Chart documentation instead of the ChartView documentation.


  2. Tina Stancheva
    Admin
    Tina Stancheva avatar
    3298 posts

    Posted 05 Dec 2013 Link to this post

    Hello Charlie,

    Thank you for sharing your feedback. Indeed the RadChart was the first solution and so when we created a better charting implementation we had to keep the backwards compatibility and to name the new implementation differently.

    Basically the RadChartView is not really a single component but a toolset of charting components such as the RadCartasianChart. Unfortunately its documentation doesn't describe that very well and we have identified that as a problem and during this release cycle we will be working on its improvement. I hope that once the documentation is updated, it will help better understand the new RadChartView components and differentiate them from the RadChart.

    Also, I fixed the incorrect link in the RadChart Overview tutorial and the change will be reflected with next week's update of our online documentation so thanks for pointing this out as well.

    Please feel free to share any additional feedback you might have on the topic.

    Regards,
    Tina Stancheva
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  3. UI for WPF is Visual Studio 2017 Ready
Back to Top