问题描述
我知道Kendo UI核心软件包中包含Kendo UI mobile(15个控件)，但是我需要了解它们之间的区别.我可以使用kendo UI控件(非移动)来开发SPA混合移动应用程序，还是只能使用15个移动控件?到目前为止，我的理解是我可以使用所有40多个版本，但是移动控件提供了更好的数据绑定支持和本机渲染...如果我错了，请纠正我.
I understand that Kendo UI mobile (15 controls) are included as part of Kendo UI core package, but I need to understand the difference. Can I use the kendo UI controls (non-mobile) to develop a SPA hybrid mobile app or I am only limited to the 15 mobile controls? So far my understanding is that I can use all of the 40+ but the mobile controls provides better data binding support and native rendering... Please correct me if I am wrong.
推荐答案
移动控件是专门为混合移动应用程序构建的.这意味着它们不仅是您通常在较小的屏幕(导航栏，列表视图，选项卡，抽屉)上找到的控件，而且还有一个随附的应用程序对象，可将应用程序胶合"在一起并提供视图转换.这是一个简单的例子....
The mobile controls are built specifically for hybrid mobile applications. That means that not only are they controls that you typically find on smaller screens (navbars, listviews, tabstrips, drawers), but there is an accompanying application object which "glues" together the application and provides view transitions. Here is a simple example....
移动框架在处理元标记，溢出滚动，快速单击和触摸支持(无300ms延迟)方面也做了大量工作.
The mobile framework also does a TON of heavy lifting in terms of taking care of meta tags, overflow scrolling, fast-click and touch support (no 300ms delay).
SPA框架是从移动应用程序对象的使用中抽象出来的.因此，当您可以使用SPA框架和Web小部件来构建混合应用程序时，Kendo UI Mobile正是为此而设计的，因此使用Kendo UI Mobile会更好.
The SPA framework is abstracted from what the mobile application object uses. So while you could use the SPA framework and web widgets to build your hybrid app, Kendo UI Mobile was designed for exactly this, so you would be much better off with Kendo UI Mobile.
此外-如果您要进行混合，则可能要签出提供剑道的 AppBuilder UI Mobile作为默认的UI库.
Also - if you're doing hybrid, you may want to checkout AppBuilder which provides Kendo UI Mobile as the default UI library.
这篇关于Kendo UI Core和Kendo UI Mobile有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！