This is a migrated thread and some comments may be shown as answers.
Following AJAX standards
8 Answers 145 Views
This is a migrated thread and some comments may be shown as answers.
none123456
Top achievements
Rank 1
none123456 asked on 25 Sep 2007, 05:50 PM
We're switching from ComponentArt's controls to telerik's RadControls, and we've been very pleased so far. One thing ComponentArt did a bid better, however, was following the ASP.NET AJAX conventions. For example methods were camel-cased (datePicker.clear(), not datePicker.Clear()) and properties followed the get/set pattern (datePicker.set_selectedDate(), not datePicker.SetSelectedDate()). Also, the client objects were available through the standard $find(clientID) pattern (not just as global objects). I was hoping telerik would follow these conventions in the "Prometheus" controls, but as far as I can tell, in the documentation, that is not the case. Can you tell me if any of these conventions are or will be supported for "Prometheus" controls?

I realize that, for backwards-compatibility reasons, you may not be able to remove properties or methods defined using the old conventions (Clear() and SetSelectedDate()), but you could leave these methods for compatibility and add the equivalent versions named according to the standard conventions. The same thing could be done for component references (leave the global variable, and add $find(clientID) support). Would it be possible to follow the ASP.NET AJAX conventions going forward?

Thanks,

David

8 Answers, 1 is accepted

Sort by
0
Edvin
Top achievements
Rank 1
answered on 25 Sep 2007, 09:26 PM

Hi david,

I completely agree with you. In last month I was using trial version of RAD controls for ASP.NET and I was very pleased. I was able to convert quite big application from pure ASP. NET to rad without any major problems. My plain was to use rad controls for some months and then move application to Prometheus. But I’m not quite sure anymore, I have read Prometheus help files and I see that ASP.NET AJAX conventions are not followed. Some controls (new ones) use something what is near to ASP.NET AJAX, but old are far from that. I think that that those rules must be strictly followed even for the sake of backwards-compatibility, because I don’t care of 1 or 2 additional days for conversion, more important are then years of effecting working. My opinion is that Prometheus controls (client side) must use namespaces, must be derived from Sys.UI.Control, all event handlers must be in form  handlerName(sender, args), correct naming conventions etc… It is better that things are done correctly in the beginning than later corrected with each release…

Thanks

edvin

0
Missing User
answered on 26 Sep 2007, 03:30 PM
Hello guys,

Thank you for the nice words about our controls. The Telerik controls have been designed with backwards compatibility in mind and you are absolutely right about the naming convention. We will investigate this issue thoroughly and will address it for the official release.

Thanks a lot for your feedback - we really appreciate it.

Best regards,
Plamen
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
Gavin Bryan
Top achievements
Rank 1
answered on 15 Dec 2007, 01:08 PM
Hi David

Just caught your post (I know it was a while ago). I'm also thinking of moving from ComponentART to Telerik and was wondering if there were some reasons why you did this that might help me in my decision.

Thanks
0
Bodrov
Top achievements
Rank 1
answered on 15 Dec 2007, 03:40 PM
Hi David,

ComponentArt has very beautifully crafted controls but for all the beauty in the world, they have lack in functionality in several cases.

ComponentArt recently released their own WYSIWYG HTML editor, but Telerik has several years experience already and their HTML editor is IMHO the best editor on the market. The control offers multiple nice features and enhancements which you can see and test here.

The ComponentArt's "callback" control seem to be nothing different from the built-in UpdatePanel in the ASP.NET AJAX, at least in my experience.

In addition, I noticed that Telerik produces not only ASP.NET controls- but also WinForms, WPF, Reporting or Silverlight components. The guys have a very ambitious product roadmap and introduce new controls almost every quarter. They make regular updates that fix not only the most of the reported bugs but also very often provide new features.

Last but not least, you can always post your questions in the forums and the community will help you.

Best regards,
/Ivan
0
Gavin Bryan
Top achievements
Rank 1
answered on 15 Dec 2007, 04:24 PM
Thanks Ivan for the reply.

Yes I've noticed that these forums seem alot more active than ComponentARTs forums and feedback to issues from Telerik seem more reponsive and informative. They seem to have lots of documentation, demos and general information on their controls. The web side is the side I would be interested in. I have a more comfortable feeling with Telerik being more customer orientated than ComponentART and although ComponentART were ahead with the Ajax controls they seem to behind in other key areas (Editor and more importantly to me Silverlight). I love the client side API of ComponentART and not sure if Telerik would be the same but I probably need to do some proper comparisons. i.e. I can add nodes to a treeview from client side with ComponentART and not sure if this is possible with Telerik from what I've seen. Also I noticed ComponentART now have Ajax webservices linked in to alot of their controls.

How do you find memory leakage with Telerik controls as this is another issue for me with ComponentART. I don't think their Javascript is very tight and IE6 would start dying after a while. IE7 has better memory management leakage but still not 100% and ComponentARTs controls still seem to suffer. If I knew Telerik's didn't suffer from this and performance was good I would make the jump today as have found with ComponentARTs controls the IE memory size just gets bigger and bigger and makes controls unusable where lots of page refreshes occur. I am writing a CMS system at the moment and users will be flicking in and out of pages and don't want it dying due to memory leaks.

Thanks
0
Ivo
Telerik team
answered on 17 Dec 2007, 07:45 AM
Hello Gavin,

We are doing our best to address all inquiries in the forums and to promptly help everyone who has questions on Telerik products. There are also a lot of MVPs and active community members who are helping us turn Telerik forums into a great place for finding info on almost any question. We also maintain a comprehensive set of documentation materials, product samples, knowledge base articles, code library samples, videos, etc. We are proud to have one of the most helpful product resources on the market.

I would like to turn your attention to our new generation of webcontrols -- RadControls "Prometheus" for ASP.NET. The successors of our "Classic" ASP.NET controls are built entirely on top of ASP.NET AJAX and provide unbeatable performance and great client-side features and API.

With our Q3 release this week we will introduce new "Prometheus" versions of RadTreeView and RadMenu. These controls will provide client-side databinding capabilities and we will have a couple of examples on how to populate the controls with web services. The new controls will have a rich client-side API and comprehensive set of events guaranteeing full control over various functions performed on the client. You can easily add/delete/update items at the client side and all the changes will be persisted on the server as well.

One of our top priorities is minimal output and swift performance. We also continuously test for memory leaks within the controls and all potential problems are resolved early in the development cycle.

I would invite you to go ahead and try RadControls as well as the new "Prometheus" controls we are releasing. Any feedback or questions you might have are very welcome.

Thank you for choosing to evaluate our products.

Kind regards,
Ivo Nedkov
Unit Manager, RadControls for ASP.NET
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
Gregory Ott
Top achievements
Rank 1
answered on 17 Dec 2007, 10:10 PM
Gavin,

Some of the major reasons we moved were:
1. Telerik has a combined date/time picker. ComponentArt didn't offer that (at least at the time).
2. Telerik uses much better (semantic) markup. They seem to "do it right" much more so than other vendors.
3. Telerik markup is much more accessible.

I hope these things help.

David
0
Jafin
Top achievements
Rank 2
answered on 19 Dec 2007, 07:19 AM
I am not a user of ComponentArt tools but I do have some other vendor tools.  By far and above Telerik's customer service excels above the other vendors.  This alone in my opinion keeps us renewing our subscription with them. 

In many cases I've had tickets open with them and they have in a lot of cases promptly returned information that has allowed me to progress my projects even if at fault of the product which they have also supplied hotfixes out of release cycle.




Asked by
none123456
Top achievements
Rank 1
Answers by
Edvin
Top achievements
Rank 1
Missing User
Gavin Bryan
Top achievements
Rank 1
Bodrov
Top achievements
Rank 1
Ivo
Telerik team
Gregory Ott
Top achievements
Rank 1
Jafin
Top achievements
Rank 2
Share this question
or