Hi
We just downloaded the new version of the prometheus controls. We noticed that for several controls method and function names have changed, instead of big caps into small caps, for example in the slider and the panelbar. We have to go through all of our javascript code to check if everything still works...
Why did these name changes occur? Even in the css files names have been changed, so even our designer needs to recheck his work...
Best regards
Andres
We just downloaded the new version of the prometheus controls. We noticed that for several controls method and function names have changed, instead of big caps into small caps, for example in the slider and the panelbar. We have to go through all of our javascript code to check if everything still works...
Why did these name changes occur? Even in the css files names have been changed, so even our designer needs to recheck his work...
Best regards
Andres
1 Answer, 1 is accepted
0
Hi Andres,
Let me 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 ("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. For instance: set_mode() should always be used from now on, set_Mode() is no longer supported.
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.
There are sticky threads in the forum for each affected control. Also there is info on this change in the documentation. If you still need some help in upgrading your projects please do not hesitate to contact us - we will assist right away.
All that being said, please accept our apologies for any inconvenience we might have caused. We will do our best to help you upgrade your projects ASAP.
Which CSS file names do you refer to? What product and skins are you using?
Regards,
Ivo
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Let me 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 ("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. For instance: set_mode() should always be used from now on, set_Mode() is no longer supported.
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.
There are sticky threads in the forum for each affected control. Also there is info on this change in the documentation. If you still need some help in upgrading your projects please do not hesitate to contact us - we will assist right away.
All that being said, please accept our apologies for any inconvenience we might have caused. We will do our best to help you upgrade your projects ASAP.
Which CSS file names do you refer to? What product and skins are you using?
Regards,
Ivo
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center