Sencha Touch与JQTouch [英] Sencha Touch Vs JQTouch

问题描述

我的初创公司和我正在决定使用哪种移动触摸框架来构建我们的移动Web应用程序.我在弄清楚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对于那些用于Web设计的人来说要复杂一些，因为它几乎是一个纯粹的编程模型(您无需在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的移动，而不是Google代码，因此实际的git存储库更易于使用找到(谷歌代码的分支曾经是google上的热门搜索).现在，乔纳森·史塔克(Jonathon Stark)接手了大卫·肯尼达(David Keneda)从事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与JQTouch的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！