Sencha Touch VS JQTouch [英] Sencha Touch Vs JQTouch

问题描述

我和我的初创公司正在决定使用哪个移动触摸框架来构建我们的移动网络应用程序.我无法弄清楚 Sencha Touch 和 JQTouch 之间的区别.我了解 Sencha 许可的产品和 Sencha Touch 都需要付费许可才能将其用于商业用途.除了法律和财务问题，这两个框架之间的区别、优缺点是什么.

My startup and I are deciding which mobile touch framework to use to build our mobile web application. I'm having trouble figuring out the difference between Sencha Touch and JQTouch. I understand that both products licensed by Sencha and that Sencha Touch requires a paid license to use it commercially. Besides legal and financial issues, what are the differences, pros and cons between both frameworks.

谢谢.

推荐答案

Sencha touch 对于那些习惯于网页设计的人来说使用起来有点复杂，因为它几乎是一个纯粹的程序模型(你不会在html，您以编程方式将元素添加到页面).然而，它确实有一个更丰富的小部件模型，并且比 jQTouch 更加充实(它也更大)...

Sencha touch is a little more complicated for those used to web design to use, in that it is almost a purely programmatic model (you don't design pages in html, you programmatically add elements to a page). It does, however, have a much richer widget model and is a lot more fleshed out than jQTouch (it is also a lot bigger)...

JQTouch 更容易即时运行(您基本上在单个页面上设计 div 中的页面)，但是，如果您计划拥有很多屏幕，则必须非常明智地将应用程序分成多个页面或在 Javascript 中动态创建页面，因为(至少在许多 Android 版本和 iPhone 3G 上)对大量页面的 DOM 操作往往是缓慢发生的地方.

JQTouch is much easier to get running on the fly (you basically design pages in div's on a single page), however, if you plan to have a lot screens you have to be very judicious about either breaking the app into multiple pages or creating your pages dynamically in Javascript as (at least on a lot of versions Android and on the iPhone 3G) DOM manipulation with a lot of pages tends to be where slowness happens.

尽管 Sencha touch 似乎有更多的文档(至少它确实更有条理并且位于中心位置)，但我实际上发现运行一个简单的 3 或 4 页应用程序更难.jQtouch 的文档遍布网络，您需要花一些时间查找资源(Jonathon Stark 的两本书(iphone , android)，窥视代码 截屏.现在网页反映了代码移动到 Github 而不是谷歌代码，实际的 git 存储库更容易找到(谷歌代码的一个分支曾经是谷歌上的前几次点击).现在乔纳森斯塔克已经接管了大卫肯内达在他从事 Sencha touch 时有点让步的项目的管理权，事情似乎变得更有条理.

Although Sencha touch appears to have a lot more documentation (at least it is certainly more organized and in a central place), I've actually found it harder to get a simple 3 or 4 page app running. The doc for jQtouch is kind of all over the web, and you need to spend some time finding the resources (Jonathon Stark's two books (iphone , android), the peepcode screencast. Now that the webpage reflects the code's movement to Github rather than google code, the actual git repository is easier to find (a fork of the google code used to be the first few hits on google). And now that Jonathon Stark has taken over stewardship of the project which David Keneda had kind of let lapse while he was working on Sencha touch, things seem to be getting more organized.

我不知道这是否有帮助，但我的建议是尝试在每个网站中编写一个 2 或 3 页的网站，看看您和您的开发人员认为什么最简单.目前，我坚持使用 jQTouch，但随着 Sencha(或其他技术)的改进，这种情况可能会改变.重要的是尽可能保持你编写的大部分 Javascript 代码与库无关...

I don't know if this helps, but my suggestion is to try to write a 2 or 3 page site in each and see what you and your developers find easiest. For now, I am sticking with jQTouch, but that could change as Sencha (or another technology) improves. The important things is to keep most of Javascript code your write as library agnostic as possible...

这篇关于Sencha Touch VS JQTouch的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！