Telerik的UI控件VS jQuery的客户端UI [英] Telerik UI controls vs client-side UI with jQuery

查看:97
本文介绍了Telerik的UI控件VS jQuery的客户端UI的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图决定我要怎么处理一个面向外部的web应用程序的用户界面。因为它是外部的,引起的页鼓胀延迟可能是一个问题。

I am trying decide on how I want to handle the UI for an external-facing web app. Because it is external, latency caused by page bloat could be an issue.

我已经使用jQuery的一些过去,而我评价Telerik的现在控制。我已经看到了很多对Telerik控制好的建议,包括一些在计算器上。事实上,他们似乎相当功能全面。我也毫不怀疑,我可以更快地开发很多应用程序使用这些控件比我用jQuery。不过,我担心自己会引起我的网页太多膨胀。

I have used jQuery some in the past, and I am evaluating the Telerik controls now. I have seen a lot of good recommendations on the Telerik controls, including some on StackOverflow. Indeed they do seem fairly full-featured. I also have no doubt that I can develop the application much more quickly using those controls than I can with jQuery. However, I am worried that they will cause too much bloat on my pages.

做任何你有比较这些控件的性能对一个纯粹的jQuery的实施经验?具体来说,

Do any of you have experience comparing the performance of these controls against a purely jQuery implementation? Specifically,


  • 是Telerik的的RadScriptManager真的比MS Ajax的ScriptManager的更好吗?

  • 是一般有性能问题与Telerik控制?

  • 是否有任何插件的jQuery来接近radgrid控件的网格功能?

任何其他相关信息将是有用的。

Any other related information would be useful as well.

推荐答案

我使用Telerik的和JQuery多年。 全功能,一般相当于吨臃肿,功能,你不需要和最后一页,是很难(甚至不可能)优化。 Telerik的下降,并使用像jQuery裸机框架。你会发现,它可以让你建立你所需要的特定功能,你永远不会回去。很多喜欢全功能的UI套件(如Telerik的或ComponentArt)是非常诱人的,但我认为它们鼓励了很多不好的节目。

I've used Telerik and JQuery for years. "Full featured" generally equates to tons of bloat, features you don't need and a final page that is hard (or impossible) to optimize. Drop Telerik and use a bare metal framework like JQuery. You'll find that it will allow you to build the specific functionality you need and you'll never go back. Many of the full featured UI suites like (like Telerik or ComponentArt) are very seductive but I think they encourage a lot of bad programming.

例如....你真的需要有网格拖和下拉能列?可能不会。这可能是最好有一个设计区,让您的用户可以布局其列preferences然后当电网瞬间轻盈主视图。不要渲染下的附加功能,用户将永远不会(或很少)与每一个页面视图中使用MB为单位。

For instance.... Do you really need to have drag-and-drop-able columns on your grid? Probably not. It's probably better to have a design area where your users can layout their column preferences and then the main view where the grid is snappy and lightweight. Don't render down megabytes of added features that your users will never (or rarely) use with every page view.

这篇关于Telerik的UI控件VS jQuery的客户端UI的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆