Thank you for pointing this out. Currently there is no reason that these properties are not of type DependencyProperty (this is why the binding fails currently). They will be modified to be dependency properties for the next internal build which will be available next week.
Initially, while designing the chart, we did application startup performance tests and it turned out that the dependency property metadata registration can have a noticeable impact. With this in mind we decided to implement most properties as plain CLR properties. After releasing the chart however, users started asking why some properties can not be bound to and we decided to change them to dependency properties whenever someone asked about a particular property.
Please write again if you have more feedback to share.
the Telerik team
Sharpen your .NET Ninja skills
! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>