This question is locked. New answers and comments are not allowed.
Brian Mains
Top achievements
Rank 1
Rank 1
Brian Mains
asked on 07 Oct 2009, 02:24 PM
Hello,
Saw on the other page of your site that in the future, the Telerik extensions for ASP.NET MVC will no longer use JQuery at some point in the future. SO I was wondering why you expose JQuery in the namespaces and helper method names... seems like if you are going to drop JQuery (and even if you continue using JQuery), that it would be better to leave it out to hide those underlying details (since it's a telerik product and not JQuery product).
Thanks.
Saw on the other page of your site that in the future, the Telerik extensions for ASP.NET MVC will no longer use JQuery at some point in the future. SO I was wondering why you expose JQuery in the namespaces and helper method names... seems like if you are going to drop JQuery (and even if you continue using JQuery), that it would be better to leave it out to hide those underlying details (since it's a telerik product and not JQuery product).
Thanks.
3 Answers, 1 is accepted
0
Rommel Manalo
Top achievements
Rank 1
Rank 1
answered on 08 Oct 2009, 03:41 AM
What is the URL of that page sir. AFAIK, they use jQuery as one of the core JavaScript Framework, Telerik will be dropping JQuery UI. I already ask this question from this forum
0
Brian Mains
Top achievements
Rank 1
Rank 1
answered on 08 Oct 2009, 01:17 PM
Here is the comment I found:
Found at: http://www.telerik.com/products/aspnet-mvc.aspx
My comment was about why use the jQuery method in the HTML helpers? Whether they use JQuery or not, abstracting out that you are using JQuery and simply calling the product a telerik product prevents code changes later, and forces me not to change when they do drop support (if they do).
Note I'm referring to the server-side HTML helper as in :
<%= HTML.JQuery()....
Future Telerik UI Extensions will not be based on jQueryUI
These wrappers are a preview of the power and implementation of the Telerik Extensions for ASP.NET MVC framework. The wrappers are provided as-is as contributions to the ASP.NET MVC and jQuery communities. Later this year, Telerik will begin shipping new, custom-built, open source UI components based the foundation revealed in this CTP. Telerik’s new UI Extensions will use the API format found in this CTP, but will more closely match the styling and features of the RadControls for ASP.NET AJAX.
Found at: http://www.telerik.com/products/aspnet-mvc.aspx
My comment was about why use the jQuery method in the HTML helpers? Whether they use JQuery or not, abstracting out that you are using JQuery and simply calling the product a telerik product prevents code changes later, and forces me not to change when they do drop support (if they do).
Note I'm referring to the server-side HTML helper as in :
<%= HTML.JQuery()....
0
Hi Brian Mains,
The new view components will be exposed through the Html.Telerik() extension method. We will continue to maintain compatibility with the currently release jQuery UI wrappers but we probably won't update them unless something critical arises. The jQuery UI components will continue to be available through Html.jQuery() to distinguish them from our home-grown components.
Regards,
Atanas Korchev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
The new view components will be exposed through the Html.Telerik() extension method. We will continue to maintain compatibility with the currently release jQuery UI wrappers but we probably won't update them unless something critical arises. The jQuery UI components will continue to be available through Html.jQuery() to distinguish them from our home-grown components.
Regards,
Atanas Korchev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.