Telerik Admin
Top achievements
Rank 1
Iron
Rank 1
Iron
Telerik Admin
asked on 17 Apr 2008, 11:13 AM
Important information: from Q1 the compatibility layer which was used in the transition beta period is now removed. All client-side methods strictly follow the ASP.NET AJAX conventions and are lower case. For instance: set_mode() should always be used from now on, set_Mode() is no longer supported.
Example:
This change also results in significant improvement in page loading times.
Example:
| Old supported syntax |
New supported syntax |
| get_Text() | get_text() |
| get_Html() | get_html() |
| set_Html() | set_html() |
| get_Document() | get_document() |
| get_Mode() | get_mode() |
This change also results in significant improvement in page loading times.
2 Answers, 1 is accepted
0
Shaun Peet
Top achievements
Rank 2
Rank 2
answered on 17 Apr 2008, 12:38 PM
Did you guys mention anytime over the past year that you were planning to do this? I can't recall that you did, but perhaps I just missed that info.
0
Hi Shaun,
Let us shed some more light on the change in the client-side API naming. When we first started "Prometheus" there was no established convention in the ASP.NET AJAX libraries. Shortly after we have released the first beta of "Prometheus" we established the new convention for client-side methods - they should be all lower case as advised by Microsoft. We have immediately introduced new API following the ASP.NET AJAX conventions (that was in the summer of 2007), however for compatibility we have decided to keep the old layer for about 6 months so that customers have time to update their projects. In this period of time we have updated all product resources - documentation, demos, etc and have tried to encourage all customers to start using the new convention. Please note that this change has affected only the first few "Prometheus" controls which were developed before we established the new API convention.
With the official RadControls for ASP.NET AJAX (formerly "Prometheus") release, the compatibility layer which was used in the transition beta period is now removed. All client-side methods strictly follow the ASP.NET AJAX conventions and are lower case.
Additionally, with the improving JavaScript intellisense support of the Visual Studio IDE we found it confusing to keep both naming conventions at the same time. Another important thing is that the compatibility layer we have introduced affected performance - now the client-side code runs faster than before.
Greetings,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Let us shed some more light on the change in the client-side API naming. When we first started "Prometheus" there was no established convention in the ASP.NET AJAX libraries. Shortly after we have released the first beta of "Prometheus" we established the new convention for client-side methods - they should be all lower case as advised by Microsoft. We have immediately introduced new API following the ASP.NET AJAX conventions (that was in the summer of 2007), however for compatibility we have decided to keep the old layer for about 6 months so that customers have time to update their projects. In this period of time we have updated all product resources - documentation, demos, etc and have tried to encourage all customers to start using the new convention. Please note that this change has affected only the first few "Prometheus" controls which were developed before we established the new API convention.
With the official RadControls for ASP.NET AJAX (formerly "Prometheus") release, the compatibility layer which was used in the transition beta period is now removed. All client-side methods strictly follow the ASP.NET AJAX conventions and are lower case.
Additionally, with the improving JavaScript intellisense support of the Visual Studio IDE we found it confusing to keep both naming conventions at the same time. Another important thing is that the compatibility layer we have introduced affected performance - now the client-side code runs faster than before.
Greetings,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center