Sencha Touch 是一个应用程序框架(您通过 Javascript 以编程方式创建界面),而 jQuery Mobile 更像是一个移动增强库(您为内容编写常规 HTML,然后添加 jQuery mobile 进行转换/动画)。 jQuery Mobile 的学习曲线更容易,但 Sencha Touch 可以更好地模拟“本机”应用程序。
Sencha Touch is an application framework (you create your interface programmatically through Javascript) while jQuery Mobile is more of a mobile enhancement library (you write regular HTML for your content, then add jQuery mobile for transitions/animations). jQuery Mobile has an easier learning curve, but Sencha Touch can better simulate "native" apps.
The first question you need to ask yourself is what is the purpose of the application. If you want to release an application for sales on one of the retail outlets (iTunes, Andoid App store), or you need access to device specific functions that are not accessible via local APIs yet (accelerometer, camera, contacts, etc) then you should be thinking Native or one of the hybrid solutions (Appcelerator, PhoneGap, etc.).
If your audience is going to be more in the "mobile web" space, such as a mobile version of a corporate web desktop site, or intranet web application port, then you should be looking at Sencha Touch and jQuery Mobile. The decision between those two is really going to be based on you development experience and and what you feel more comfortable with. Sencha Touch is a VERY robust platform that has a Desktop (ExtJS) and mobile (Sencha Touch) that mirror each other so knowing one pretty much allows you to get up and running with the other. Also, Sencha has moved to an MVC model on the client which really helps to organize client side code and make it much more congruent with server-side development platforms.
The post above is actually incorrect, using the MVC pattern on the client combined with the historyUrl on your dispatch commands gives you the ability to use the browser back and forward buttons of the browser, so that is not exclusive to jQuery Mobile. Also, the Sencha Team's suite of products includes a Designer application that provides Designer which is a WYSIWYG editor that allows for the drag and drog creation of UIs. This company's roadmap has them in the process of updating the Designer app to allow for the drag and drop design of Touch mobile screens and application that will function with the MVC pattern. They are also getting ready to release a new version of the Sencha Command tool that will automatically generate entire MVC application structures for you in a matter of minutes, which you can then add the necessary custom code to round out your application. Lastly, the new SASS theming capabilities allow designers to use CSS3 and SASS config files along with variables and Mixins to generate cross-browser CSS style sheets for your application.
So, the decision of which way to go for the mobile web development question comes down to how comfortable you are with object oriented javascript. If you are very comfortable with it, then Sencha Touch is the way to go as it very extensible class system built into the core engine that can be customized to your hearts content...but if you have minimal experience with JS and you want the server to deliver your UI and don't mind seeing the Address bar drop down to move between pages (less web 2.0 looking), then jQueryMobile is the way to go.
It's pretty obvious that I am biased to Sencha Touch due to its well thought out class structure, extensibility, very active user community, web/mobile continuity, and constant improvement to the core framework and new tools that simplify development efforts. And not to mention that the Touch platform is more mature as jQM has not reached production mode yet.
Though it's alpha, they are showing good progress. I've been looking into their development in github, seems like there's going to be cool stuff by early 2011.
If you're going to make a mobile version of a website, I am going to use jQuery Mobile. If you're going to make a “native” mobile application, I will be more likely use Sencha Touch.
Sencha touch has lived longer than jquerymobile but I found that jquerymobile handles device back button much better than SenchaTouch. I always consider back/history button handling is important in my apps, so I prefer jquerymobile. I always consider myself a JavaScript programmer, but I like the fact that I rarely need to to type any JavaScript code when I use jquerymobile. jquerymobile design is brilliant IMHO.
the make the comparison based on what you are trying to accomplish. I know Sencha Touch has a licensing fee and like you said jQM is not officially released yet.
This is a great time to be in the mobile space because there are so many viable options
我认为 jQuery mobile 更容易学习,而且似乎很有前途。 1.0 版本尚未推出,但它将是一个很好的产品。我发现它非常有吸引力,因为它基于 jQuery - 简单是座右铭
I think jQuery mobile is easier to learn and seems to be very promising. Version 1.0 is not yet available, but its going to be a good product. I find it very attractive because it is based on jQuery - simplicity is the motto
Don't forget that there is also Dojo Toolkit Mobile. It looks nice, at least at first look and it is built on top of the proven and solid Dojo Toolkit core. http://dojotoolkit.org/features/mobile. The Dojo Toolkit don't get too much audience recently but it looks like they made a lot of progress from the times it was a bit heavy, I think it is worth looking at it.
I've been trying out the sencha architect and to be honest ithas been a nightmare to get running.
My background is DotNet, html, javascript, VB, java and have been using eclipse etc for a while so am not a huge newbie with figuring out dependencys etc.
Here is what I have struck:
I went to the Sench site, downloaded Architect. It then got me to download toolkit and sencha touch. I downlaoded exactly what was recommend / instructed by the help files / site. I have Sencha Architect V2.1.0 Build 584., sencha-touch-2.0.1.1-commercial.zip, SenchaSDKTools-2.0.0-beta3-windows.exe
I also downloaded and installed a new java sdk / run time etc. The install has been done on a dead clean XP box (vmware). Web server is xampp.
Sencha does not recognise the SenchaSDKTools-2.0.0-beta3. You have to hack it using hard to find instructions. Even after hacking it the architect fails to use the proper SDK and gives error messages on deployment.
There have also been numerous errors to figure out along the way and issues where data just wont load even having followed instructions to the letter.
I have spent 11 hours getting to the point where the application will run properly without whinging but it wont deploy. It is bad enough learning a new tool / framework etc without the ide causing grief and the "instructional demos" leading you up the path.
There are lots of people getting the same errors all over.
After 15 hours of effort I am giving it up as a bad job and am returning to IBM XPages / PHP and Blueprint CSS with old fashioned, hand coded html5 / CSS3 and jquery / Ajax / JSon apps.
My reason for doing this: Application Architect keeps pushing you back to the command line. I love the command line, give me a bash shell and vi and I'm good to go. However for complex, multi file deplyoments such as mobile apps a good IDE is worth its weight in gold. Architect is not there yet. I keep needing to lift the hood and hack to get things working.
I originally looked at Sencha for a 12 year old who is interested in mobile apps and is looking for an ide to use. I tried it out - it is not suitable - even getting a hello world type app running is going to be too much for a newbie and the first app in the help files doesnt explain itself but has you copying code for pulling data from a web site you have to sign up for. (ccitybars app).
A big improvement for sencha will be when Architect works out of the box (possibly an installer with sdk, tools , touch and architect all in one) and the fisrt app -walk through is a simple hello world that then builds to entering data, saving data and then displaying data before going multi form.
I was faced with the same choice about half a year ago, then went for jQTouch instead of Sencha Touch, which I found to be extremely Javascript centered. I'm currently working on a port of that same project to jQuery Mobile and I think the transition will be much smoother than it would have been with a Sencha Touch project.
jQueryMobile wins but huge boost in arm is because of licensing. I prefer jQueryMobile because I don't want someone(thing) else to write my markup, that way hacking becoming difficult (at least for me), however, I do have couple of HTML5 apps under my belt now, one each in jQM and Sencha Touch. Sencha Touch makes it smoother, very hard to learn though while jQM gets you started in a day, there are bug but you usually get around them because of amazing web community around this framework.
I've built a nice production app in a few days using Sencha Touch 2.0 and it's delivering as documented. And, it's FAST. There might be some bugs, but, when I've run into one (which, is rarely), there seemed to be many ways to approach a solution so that it's really not that relevant.
Sencha Touch looks great but it is difficult to use. The Sencha support forums offer minimal support. Sencha Touch 2.x is still in alpha is quite buggy
Sencha touch will be the best option is you are just starting because it is well documented and it has a community support. Also, with phonegap, you spend more time on the development and less on things about other mobile platforms. Phonegap will build the application for you , once you upload it to the builder .
Comparing the two is like comparing apples and grapes...though you want to develop mobile apps with both, the level of comfort with either depends entirely on you.
Sencha Touch based apps can only work on WebKit based browsers. JQueryMobile based apps can work on all mobile web browsers.
I think you can go ahead with JQueryMobile for next 2 to 3 years. I am expecting in 2-3 years all mobile browsers will be based on WebKit engine. Once all mobile browsers start supporting WebKit, move to the Sench Touch mainly because of very good quality user interface.
It is unbeatable and fast performance in a training of couple of days. Not to mention the fast update and new features and support for server side wrappers (asp.net, php, jsp). It is unique!
I have used both and they each have conditions where one is better suited then the other.
In my opinion you would use JQueryMobile when 1. You need a quick and light weight mobile implementation of an web application. 2. You have time constraints (definitely faster to learn and implement then Sencha Touch). 3. Native look and feel is not a requirement.
When making an extension to an existing web application where relatively simple functionalities have to be extended to extended to mobile (really fast and easy) I found JQM to be extremely useful and straight forward.
In my opinion you would use sencha when 1. You want a native look and feel 2. You want a higher degree of functionality on the mobile side (possible access to native api's through phone gap) 3. Targeting the latest smartphones (performance is impressive)
发布评论
评论(20)
Sencha Touch 是一个应用程序框架(您通过 Javascript 以编程方式创建界面),而 jQuery Mobile 更像是一个移动增强库(您为内容编写常规 HTML,然后添加 jQuery mobile 进行转换/动画)。 jQuery Mobile 的学习曲线更容易,但 Sencha Touch 可以更好地模拟“本机”应用程序。
Sencha Touch is an application framework (you create your interface programmatically through Javascript) while jQuery Mobile is more of a mobile enhancement library (you write regular HTML for your content, then add jQuery mobile for transitions/animations). jQuery Mobile has an easier learning curve, but Sencha Touch can better simulate "native" apps.
您需要问自己的第一个问题是应用程序的目的是什么。如果您想在零售店之一(iTunes、Andoid App store)上发布一款应用程序进行销售,或者您需要访问尚未通过本地 API 访问的设备特定功能(加速计、相机、联系人等),那么您可以应该考虑 Native 或混合解决方案之一(Appcelerator、PhoneGap 等)。
如果您的受众更多地关注“移动 Web”领域,例如企业 Web 桌面站点的移动版本或 Intranet Web 应用程序端口,那么您应该考虑 Sencha Touch 和 jQuery Mobile。这两者之间的决定实际上取决于您的开发经验以及您感觉更舒服的内容。 Sencha Touch 是一个非常强大的平台,它有桌面版 (ExtJS) 和移动版 (Sencha Touch),它们相互镜像,因此对其中一个非常了解,您就可以启动并运行另一个。此外,Sencha 已在客户端上转向 MVC 模型,这确实有助于组织客户端代码并使其与服务器端开发平台更加一致。
上面的帖子实际上是不正确的,在客户端上使用 MVC 模式并结合调度命令上的 HistoryUrl 让您能够使用浏览器的后退和前进按钮,因此这并不是 jQuery Mobile 独有的。此外,Sencha 团队的产品套件还包括一个 Designer 应用程序,该应用程序提供 Designer,这是一个所见即所得编辑器,允许拖放创建 UI。该公司的路线图表明他们正在更新 Designer 应用程序,以允许对触摸移动屏幕和应用程序进行拖放设计,并使用 MVC 模式运行。他们还准备发布新版本的 Sencha Command 工具,该工具将在几分钟内自动为您生成整个 MVC 应用程序结构,然后您可以添加必要的自定义代码来完善您的应用程序。最后,新的 SASS 主题功能允许设计人员使用 CSS3 和 SASS 配置文件以及变量和 Mixins 为您的应用程序生成跨浏览器 CSS 样式表。
因此,决定采用哪种方式解决移动 Web 开发问题取决于您对面向对象 JavaScript 的熟悉程度。如果您对它非常满意,那么 Sencha Touch 是您的最佳选择,因为它内置于核心引擎中,可扩展的类系统可以根据您的喜好进行定制......但如果您对 JS 的经验很少,并且您想要服务器来提供您的 UI 并且不介意看到地址栏下拉以在页面之间移动(更少的 Web 2.0 外观),那么 jQueryMobile 就是最佳选择。
很明显,我偏向 Sencha Touch,因为它经过深思熟虑的类结构、可扩展性、非常活跃的用户社区、Web/移动连续性以及对核心框架和简化开发工作的新工具的不断改进。更不用说 Touch 平台更加成熟,因为 jQM 尚未达到生产模式。
The first question you need to ask yourself is what is the purpose of the application. If you want to release an application for sales on one of the retail outlets (iTunes, Andoid App store), or you need access to device specific functions that are not accessible via local APIs yet (accelerometer, camera, contacts, etc) then you should be thinking Native or one of the hybrid solutions (Appcelerator, PhoneGap, etc.).
If your audience is going to be more in the "mobile web" space, such as a mobile version of a corporate web desktop site, or intranet web application port, then you should be looking at Sencha Touch and jQuery Mobile. The decision between those two is really going to be based on you development experience and and what you feel more comfortable with. Sencha Touch is a VERY robust platform that has a Desktop (ExtJS) and mobile (Sencha Touch) that mirror each other so knowing one pretty much allows you to get up and running with the other. Also, Sencha has moved to an MVC model on the client which really helps to organize client side code and make it much more congruent with server-side development platforms.
The post above is actually incorrect, using the MVC pattern on the client combined with the historyUrl on your dispatch commands gives you the ability to use the browser back and forward buttons of the browser, so that is not exclusive to jQuery Mobile. Also, the Sencha Team's suite of products includes a Designer application that provides Designer which is a WYSIWYG editor that allows for the drag and drog creation of UIs. This company's roadmap has them in the process of updating the Designer app to allow for the drag and drop design of Touch mobile screens and application that will function with the MVC pattern. They are also getting ready to release a new version of the Sencha Command tool that will automatically generate entire MVC application structures for you in a matter of minutes, which you can then add the necessary custom code to round out your application. Lastly, the new SASS theming capabilities allow designers to use CSS3 and SASS config files along with variables and Mixins to generate cross-browser CSS style sheets for your application.
So, the decision of which way to go for the mobile web development question comes down to how comfortable you are with object oriented javascript. If you are very comfortable with it, then Sencha Touch is the way to go as it very extensible class system built into the core engine that can be customized to your hearts content...but if you have minimal experience with JS and you want the server to deliver your UI and don't mind seeing the Address bar drop down to move between pages (less web 2.0 looking), then jQueryMobile is the way to go.
It's pretty obvious that I am biased to Sencha Touch due to its well thought out class structure, extensibility, very active user community, web/mobile continuity, and constant improvement to the core framework and new tools that simplify development efforts. And not to mention that the Touch platform is more mature as jQM has not reached production mode yet.
我已经使用 jQuery mobile 一段时间了。它在 Blackberry 6、iPhone 和 Android 下运行良好。
我在这里写了一篇关于它的文章: jQuery mobile alpha
虽然还只是 alpha,但他们已经取得了良好的进展。我一直在 github 上研究他们的开发,看起来到 2011 年初将会有很酷的东西。
更新 2011-12-01 jQuery Mobile 发布了 1.0 版,终于摆脱了 alpha 版本。在这里阅读更多相关信息:http://jquerymobile。 com/blog/2011/11/16/announcing-jquery-mobile-1-0/
I've been using jQuery mobile for a while now. It works well under Blackberry 6, iPhone, and Android.
I wrote an article about it here: jQuery mobile alpha
Though it's alpha, they are showing good progress. I've been looking into their development in github, seems like there's going to be cool stuff by early 2011.
UPDATE 2011-12-01 jQuery Mobile relased version 1.0, finally out of alpha. Read more about it here: http://jquerymobile.com/blog/2011/11/16/announcing-jquery-mobile-1-0/
如果您要制作网站的移动版本,我将使用 jQuery Mobile。如果您要制作“本机”移动应用程序,我更有可能使用 Sencha Touch。
http://tysonlloydcadenhead.com/blog/jquery-mobile-vs-sencha-touch
If you're going to make a mobile version of a website, I am going to use jQuery Mobile. If you're going to make a “native” mobile application, I will be more likely use Sencha Touch.
http://tysonlloydcadenhead.com/blog/jquery-mobile-vs-sencha-touch
Sencha touch 的寿命比 jquerymobile 更长,但我发现 jquerymobile 处理设备后退按钮的能力比 SenchaTouch 好得多。
我始终认为后退/历史按钮处理在我的应用程序中很重要,所以我更喜欢 jquerymobile。
我一直认为自己是一名 JavaScript 程序员,但我喜欢这样一个事实:当我使用 jquerymobile 时,我很少需要键入任何 JavaScript 代码。
恕我直言,jquerymobile 的设计非常出色。
Sencha touch has lived longer than jquerymobile but I found that jquerymobile handles device back button much better than SenchaTouch.
I always consider back/history button handling is important in my apps, so I prefer jquerymobile.
I always consider myself a JavaScript programmer, but I like the fact that I rarely need to to type any JavaScript code when I use jquerymobile.
jquerymobile design is brilliant IMHO.
我也赞成 sencha,JQM 确实很慢,而且无法给人一种原生应用程序的印象。
I am also in favor of sencha, JQM is really slow and failed to give an impression of an native app.
为什么要限制自己...
查看 PhoneGap 和 Titanium Appcelerator
根据您想要完成的任务进行比较。我知道 Sencha Touch 需要支付许可费,而且正如您所说,jQM 尚未正式发布。
现在是进入移动领域的好时机,因为有很多可行的选择
why limit yourself...
Look into PhoneGap and Titanium Appcelerator
the make the comparison based on what you are trying to accomplish. I know Sencha Touch has a licensing fee and like you said jQM is not officially released yet.
This is a great time to be in the mobile space because there are so many viable options
我认为 jQuery mobile 更容易学习,而且似乎很有前途。 1.0 版本尚未推出,但它将是一个很好的产品。我发现它非常有吸引力,因为它基于 jQuery - 简单是座右铭
I think jQuery mobile is easier to learn and seems to be very promising. Version 1.0 is not yet available, but its going to be a good product. I find it very attractive because it is based on jQuery - simplicity is the motto
不要忘记还有 Dojo Toolkit Mobile。它看起来不错,至少乍一看是这样,而且它构建在经过验证且可靠的 Dojo Toolkit 核心之上。 http://dojotoolkit.org/features/mobile。
Dojo Toolkit 最近没有吸引太多观众,但看起来他们比以前有点重的时代取得了很大的进步,我认为值得一看。
Don't forget that there is also Dojo Toolkit Mobile. It looks nice, at least at first look and it is built on top of the proven and solid Dojo Toolkit core. http://dojotoolkit.org/features/mobile.
The Dojo Toolkit don't get too much audience recently but it looks like they made a lot of progress from the times it was a bit heavy, I think it is worth looking at it.
我一直在尝试 sencha 架构师,说实话,运行它是一场噩梦。
我的背景是 DotNet、html、javascript、VB、java,并且已经使用 eclipse 等有一段时间了,所以我不是一个弄清楚依赖关系等的大新手。
这是我的震惊:
我去了 Sench 网站,下载了 Architect。
然后它让我下载工具包和 sencha touch。我准确地下载了帮助文件/网站推荐/指示的内容。
我有 Sencha Architect V2.1.0 Build 584.、sencha-touch-2.0.1.1-commercial.zip、SenchaSDKTools-2.0.0-beta3-windows.exe
我还下载并安装了新的 java sdk / 运行时等。已在完全干净的 XP 机器 (vmware) 上完成。网络服务器是xampp。
Sencha 无法识别 SenchaSDKTools-2.0.0-beta3。你必须使用很难找到的指令来破解它。即使在破解之后,架构师也无法使用正确的 SDK,并在部署时给出错误消息。
在此过程中还存在许多错误需要解决,以及即使严格遵循说明也无法加载数据的问题。
我花了 11 个小时才达到应用程序可以正常运行但无法部署的程度。学习一个新的工具/框架等,如果没有 ide 造成的悲伤和“指导演示”引导你走上这条道路,那就够糟糕的了。
有很多人都犯了同样的错误。
经过 15 个小时的努力,我放弃了它,因为它是一项糟糕的工作,并返回到 IBM XPages / PHP 和 Blueprint CSS,以及老式的、手工编码的 html5 / CSS3 和 jquery / Ajax / JSon 应用程序。
我这样做的原因是:应用程序架构师不断将您推回命令行。我喜欢命令行,给我一个 bash shell 和 vi,我就可以开始了。然而,对于复杂的多文件部署(例如移动应用程序)来说,一个好的 IDE 是物有所值的。建筑师还没到。我一直需要打开引擎盖并进行修改才能使事情正常运行。
我最初为一名对移动应用程序感兴趣并正在寻找可用的 ide 的 12 岁孩子寻找 Sencha。我尝试了一下 - 它不适合 - 即使运行一个 hello world 类型的应用程序对于新手来说也太多了,并且帮助文件中的第一个应用程序没有解释本身,但让您复制代码以从网站提取数据你必须注册。 (城市酒吧应用程序)。
sencha 的一大改进将是当 Architect 开箱即用时(可能是一个包含 sdk、工具、触摸和架构师的安装程序),并且第一个应用程序 - 遍历是一个简单的 hello world,然后构建用于输入数据,保存数据,然后在进入多种形式之前显示数据。
I've been trying out the sencha architect and to be honest ithas been a nightmare to get running.
My background is DotNet, html, javascript, VB, java and have been using eclipse etc for a while so am not a huge newbie with figuring out dependencys etc.
Here is what I have struck:
I went to the Sench site, downloaded Architect.
It then got me to download toolkit and sencha touch. I downlaoded exactly what was recommend / instructed by the help files / site.
I have Sencha Architect V2.1.0 Build 584., sencha-touch-2.0.1.1-commercial.zip, SenchaSDKTools-2.0.0-beta3-windows.exe
I also downloaded and installed a new java sdk / run time etc. The install has been done on a dead clean XP box (vmware). Web server is xampp.
Sencha does not recognise the SenchaSDKTools-2.0.0-beta3. You have to hack it using hard to find instructions. Even after hacking it the architect fails to use the proper SDK and gives error messages on deployment.
There have also been numerous errors to figure out along the way and issues where data just wont load even having followed instructions to the letter.
I have spent 11 hours getting to the point where the application will run properly without whinging but it wont deploy. It is bad enough learning a new tool / framework etc without the ide causing grief and the "instructional demos" leading you up the path.
There are lots of people getting the same errors all over.
After 15 hours of effort I am giving it up as a bad job and am returning to IBM XPages / PHP and Blueprint CSS with old fashioned, hand coded html5 / CSS3 and jquery / Ajax / JSon apps.
My reason for doing this: Application Architect keeps pushing you back to the command line. I love the command line, give me a bash shell and vi and I'm good to go. However for complex, multi file deplyoments such as mobile apps a good IDE is worth its weight in gold. Architect is not there yet. I keep needing to lift the hood and hack to get things working.
I originally looked at Sencha for a 12 year old who is interested in mobile apps and is looking for an ide to use. I tried it out - it is not suitable - even getting a hello world type app running is going to be too much for a newbie and the first app in the help files doesnt explain itself but has you copying code for pulling data from a web site you have to sign up for. (ccitybars app).
A big improvement for sencha will be when Architect works out of the box (possibly an installer with sdk, tools , touch and architect all in one) and the fisrt app -walk through is a simple hello world that then builds to entering data, saving data and then displaying data before going multi form.
大约半年前我也面临着同样的选择,然后选择了 jQTouch 而不是 Sencha Touch,我发现它非常以 Javascript 为中心。我目前正在将同一个项目移植到 jQuery Mobile,我认为这个过渡将比 Sencha Touch 项目顺利得多。
I was faced with the same choice about half a year ago, then went for jQTouch instead of Sencha Touch, which I found to be extremely Javascript centered. I'm currently working on a port of that same project to jQuery Mobile and I think the transition will be much smoother than it would have been with a Sencha Touch project.
如果您了解基本的 PHP,我强烈推荐 jqmphp.com。不到 3 天的时间就建立并运行了一个基于移动设备的在线订餐网站!
If you know basic PHP I strongly suggest jqmphp.com. Up and running in less than 3 days a whole online mobile based site to order food!
MoSync 团队最近做了一个有趣的比较:
哪个移动 JavaScript 框架是最好的:jQuery Mobile、Sencha Touch、jQtouch 或 Kendo UI?
http://www.codefessions.com/2012/04/mobile -javascript-frameworks-evaluation.html
http://www.codefessions.com/2012/04/which-mobile-javascript-framework-is.html
http://www.codefessions.com/2012/05 /which-mobile-javascript-framework-is.html
jQueryMobile 获胜,但 ARM 的巨大提升是由于许可。我更喜欢 jQueryMobile,因为我不想让其他人(事物)编写我的标记,这样黑客攻击就变得很困难(至少对我来说),但是,我现在确实有几个 HTML5 应用程序,每个应用程序都在 jQM 和煎茶触摸。 Sencha Touch 使它更流畅,但很难学习,尽管 jQM 可以让您在一天内开始使用,但存在一些错误,但您通常可以绕过它们,因为围绕该框架的令人惊叹的网络社区。
MoSync team has recently done an interesting comparison:
Which Mobile JavaScript framework is the best: jQuery Mobile, Sencha Touch, jQtouch, or Kendo UI?
http://www.codefessions.com/2012/04/mobile-javascript-frameworks-evaluation.html
http://www.codefessions.com/2012/04/which-mobile-javascript-framework-is.html
http://www.codefessions.com/2012/05/which-mobile-javascript-framework-is.html
jQueryMobile wins but huge boost in arm is because of licensing. I prefer jQueryMobile because I don't want someone(thing) else to write my markup, that way hacking becoming difficult (at least for me), however, I do have couple of HTML5 apps under my belt now, one each in jQM and Sencha Touch. Sencha Touch makes it smoother, very hard to learn though while jQM gets you started in a day, there are bug but you usually get around them because of amazing web community around this framework.
我在几天内使用 Sencha
Touch 2.0
构建了一个不错的生产应用程序,并且它正在按文档交付。而且,速度很快。可能存在一些错误,但是,当我遇到一个错误(很少见)时,似乎有很多方法可以找到解决方案,因此它实际上并不那么相关。I've built a nice production app in a few days using Sencha
Touch 2.0
and it's delivering as documented. And, it's FAST. There might be some bugs, but, when I've run into one (which, is rarely), there seemed to be many ways to approach a solution so that it's really not that relevant.Sencha Touch 看起来很棒,但使用起来很困难。 Sencha 支持论坛提供最低限度的支持。 Sencha Touch 2.x 仍处于 alpha 版本,有很多 bug
Sencha Touch looks great but it is difficult to use. The Sencha support forums offer minimal support. Sencha Touch 2.x is still in alpha is quite buggy
如果您刚刚开始,Sencha touch 将是最好的选择,因为它有详细的文档记录并且有社区支持。此外,使用phonegap,您可以将更多的时间花在开发上,而不是花在其他移动平台上的时间上。一旦您将应用程序上传到构建器,Phonegap 就会为您构建该应用程序。
Sencha touch will be the best option is you are just starting because it is well documented and it has a community support. Also, with phonegap, you spend more time on the development and less on things about other mobile platforms. Phonegap will build the application for you , once you upload it to the builder .
比较两者就像比较苹果和葡萄......虽然您想用两者开发移动应用程序,但其中任何一个的舒适程度完全取决于您。
如果您想比较功能,此图表可能会有所帮助:http://www .markus-falk.com/mobile-frameworks-comparison-chart/
Comparing the two is like comparing apples and grapes...though you want to develop mobile apps with both, the level of comfort with either depends entirely on you.
This chart might be helpful if you want to compare the features : http://www.markus-falk.com/mobile-frameworks-comparison-chart/
基于 Sencha Touch 的应用程序只能在基于 WebKit 的浏览器上运行。基于 JQueryMobile 的应用程序可以在所有移动网络浏览器上运行。
我认为您可以在未来 2 到 3 年继续使用 JQueryMobile。我预计 2-3 年内所有移动浏览器都将基于 WebKit 引擎。一旦所有移动浏览器开始支持 WebKit,就会转向 Sench Touch,主要是因为质量非常好的用户界面。
Sencha Touch based apps can only work on WebKit based browsers. JQueryMobile based apps can work on all mobile web browsers.
I think you can go ahead with JQueryMobile for next 2 to 3 years. I am expecting in 2-3 years all mobile browsers will be based on WebKit engine. Once all mobile browsers start supporting WebKit, move to the Sench Touch mainly because of very good quality user interface.
我建议 KendoUI
它在几天的训练中具有无与伦比的快速性能。更不用说快速更新和新功能以及对服务器端包装器(asp.net、php、jsp)的支持。它是独一无二的!
I suggest KendoUI
It is unbeatable and fast performance in a training of couple of days. Not to mention the fast update and new features and support for server side wrappers (asp.net, php, jsp). It is unique!
我已经使用过这两种方法,并且它们各自都有一个比另一个更适合的条件。
在我看来,您会在以下情况下使用 JQueryMobile:
1. 您需要快速、轻量级的 Web 应用程序移动实施。
2. 你有时间限制(学习和实施肯定比 Sencha Touch 更快)。
3. 原生外观和感觉不是必需的。
当对现有 Web 应用程序进行扩展时,必须将相对简单的功能扩展到移动设备(非常快速且简单),我发现 JQM 非常有用且直接。
在我看来,你会在什么时候使用sencha
1.你想要原生的外观和感觉
2.您希望在移动端具有更高程度的功能(可以通过手机间隙访问本机api)
3. 针对最新的智能手机(性能令人印象深刻)
I have used both and they each have conditions where one is better suited then the other.
In my opinion you would use JQueryMobile when
1. You need a quick and light weight mobile implementation of an web application.
2. You have time constraints (definitely faster to learn and implement then Sencha Touch).
3. Native look and feel is not a requirement.
When making an extension to an existing web application where relatively simple functionalities have to be extended to extended to mobile (really fast and easy) I found JQM to be extremely useful and straight forward.
In my opinion you would use sencha when
1. You want a native look and feel
2. You want a higher degree of functionality on the mobile side (possible access to native api's through phone gap)
3. Targeting the latest smartphones (performance is impressive)