从Jquery Mobile切换到AppFramework [英] Switching from Jquery Mobile to AppFramework
问题描述
我使用Jquery Mobile构建了一个项目。 JQM似乎完美的快速原型，但最终结果在iphone 3GS / IOS 5.1是远离流体。我试过了很多的hacks /技巧，使它更快，摆脱过渡，但仍然，我不能得到满意的结果。
I've built a project using Jquery Mobile. JQM seems perfect for fast prototyping but the end result on an iphone 3GS/IOS 5.1 is far from fluid. I've tried a lot of hacks/tricks to make it faster and got rid of transitions but still, I cannot get a satisfying result.
我一直在环顾四周。我需要的是一个轻量级的解决方案与一个体面的UI（JQM是完美的我需要在该领域）。
I've been looking around. What I need is a lightweight solution with a decent UI (JQM is perfect for what I need in that domain).
trigger.io和AppFramework似乎是2个解决方案可用（也许我错过了一些其他）。
trigger.io and AppFramework seem to be the 2 solutions which are available (maybe I'm missing some others).
我想给AppFramework一个去，但我想从已经做出改变的人那里得到反馈。
I'd like to give AppFramework a go but I'd like to have feedback from people who have made the change.
谢谢。
推荐答案
简介
还可以找到此答案的更大版本 这里 。
Intro
A larger version of this answer can also be found HERE.
jQuery Mobile 从未旨在仅用作HTML5 / CSS3混合移动应用程序框架。在类似的轨道上，像他的哥哥 jQuery 和 jQuery UI ，用于在不断增长的移动网络应用市场中提供强大的响应解决方案。它从它的哥哥采取的是一个全方位的浏览器支持。在每个可能的主要平台上运行它，它应该工作相同。
jQuery Mobile was never intended to be used only as an HTML5/CSS3 hybrid mobile app framework. On a similar track like its older brother jQuery and jQuery UI it was intended to be used as a robust, responsive solution in the ever growing mobile web application market. What it took from its older brother was an all around browser support. Run it on every possible major platform and it should work just the same.
同样广泛的浏览器支持也带来了另一个问题，这是平台优化。因为jQM不能偏爱特定的平台也意味着它没有被优化以使用任何它的最多。
That same broad browser support also brought another problem and that is platform optimization. Because jQM can't favor specific platforms also means it is not optimized to use most in any of it.
让我们还谈谈 Phonegap 。虽然伟大的应用程序打包系统，当它与一个更大的 jQuery Mobile 应用程序一起使用时，它成为一个地狱洞。这就像两个伟大的父母做了一个畸形的混蛋孩子或大的赞美给予一个更大的减号。
Let us also talk about Phonegap a bit. While great app packaging system it becomes a hell hole when used with a larger jQuery Mobile application. It's like two great parents made a deformed bastard child or to large pluses gave as an even bigger minus.
像人类历史上一样，另一群开发者来填补这个漏洞。来了 jqMobi （现在 AppFramework ）， jqTouch ， Zepto ， Sencha Touch ， Trigger.io 和其他。
Like always in human history another groups of developers came to fill this evident hole. And here came jqMobi (now AppFramework), jqTouch, Zepto, Sencha Touch, Trigger.io and others.
在进一步比jQuery Mobile之前，一件事必须了解，获得速度（并相信我，你会得到它），你会失去社区支持。虽然每一个前面提到的框架都有一个相当大的开发者社区，但它们都不能接近 jQM 。
Before going any further than jQuery Mobile one thing must be understood, whatever you gain in speed (and trust me you will get it), you will lose in community support. While every earlier mentioned framework has a sizable developer community behind them, all of them combined can't even come close to jQM.
说，让我们深入细节。根据我的经验，目前有两个最佳解决方案，HTML5 / CSS3 Android和iOS混合应用程序框架是 AppFramework 和 Sencha Touch 。首先，让我说，他们是快，比 jQuery Mobile 将永远（如果jQ开发人员在这个课程）。 UI支持是类似的，如果不是甚至更好的情况下 Sencha触摸，更不用说UI是更本土的看起来是这样的情况下jQuery Mobile。
With this said, let us delve into specifics. From my experience currently two best solutions as HTML5/CSS3 Android and iOS hybrid app frameworks are AppFramework and Sencha Touch. First, let me say, they are fast, faster than jQuery Mobile will ever be (if jQ developers stay on this course). UI support is similar if not even better in the case of Sencha Touch, not to mention UI is more native looking that it is the case with jQuery Mobile. Listviews are faster, scrolling is better, transitions do not stutter.
在某人问起来之前为什么人们会选择使用 jQuery Mobile ？明显的原因是社区支持，在某种程度上，这是真相。但在这里还有一些其他紧迫的事情。虽然 jQMoby 会将其自行宣传为
Before someone asks why do people then choose to use, jQuery Mobile instead? The obvious reason would be community support and to some extent, this is the truth. But there are some other pressing matters here. While jQMoby advertise it self as a truer jQuery alternative to jQuery Mobile it is a big lie. While still a great an excellent framework they are using this saying as a marketing trick. They have indeed cloned (redone them) a lot of jQuery features but this is only a partial job, and veteran jQuery developers are going to find them self in a problem. They will not be able to make fully the most of their previous knowledge thus spending more time trying to find how to do something that was supposed to work than working on an app.
另一方面， Sencha Touch 不会遇到这个问题，因为它有一个不同的，几乎外星人的语法。与 jqMoby 一样，您需要花很多时间来了解其语法。
On the other hand Sencha Touch doesn't suffer from this problem because it has a different, almost alien syntax. Like with jqMoby you will need a lot of time to get into its syntax. But have no fear, the result will be satisfactory in the end.
另一件事，不像jQuery Mobile和 Phonegap ， AppFramework 和 Sencha Touch 拥有其原生应用打包系统。我认为，这个系统比 Phonegap 更好，因为他们使用他们的js框架。
One other thing, unlike jQuery Mobile and Phonegap, AppFramework and Sencha Touch has their native app packaging system. In my humble opinion, this system is better than Phonegap because they are made to work with their js frameworks. Only thing Phonegap have over them is a HUGE plugin development community.
jQuery vs Zepto vs jQMobi - 哪一个是最快的？
jQuery vs Zepto vs jQMobi - which one is the fastest?
在这种情况下jQuery是像jQuery Mobile，因为测试在这里继承
一个底层框架的功能jQM从jQ。
In this case jQuery is like jQuery Mobile because test here relays on an underlying framework functionality which jQM takes from jQ.
jQuery Mobile与Sencha Touch的良好竞争< a>
标题全部。
Title says it all.
AppFramework forum
只有良好的jqMoby支援网站
Only good jqMoby support site
Sencha Touch forum
只有良好的Sencha Touch支持网站
Only good Sencha Touch support site
/ h1>
AppFramework可能是你的最佳选择。它有一个类似于
的设计作为jQuery Mobile，所以语法不会是一个问题。
Conclusion
AppFramework is probably the best choice for you. It has a similar design as jQuery Mobile so the syntax is not going to be a problem.
这篇关于从Jquery Mobile切换到AppFramework的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
