是从Sencha Touch 2还是Sencha Touch 1.x开始? [英] Is it better to start with Sencha Touch 2, or Sencha Touch 1.x?

查看:173
本文介绍了是从Sencha Touch 2还是Sencha Touch 1.x开始?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近使用PhoneGap构建了一个演示应用程序,我选择将JQuery Mobile作为UI框架。这是...好的。

I've recently built a demo application using PhoneGap, and I chose to try JQuery Mobile as a UI framework. It was... okay. I'd like to try out Sencha Touch now and see if I like it better.

截至目前(11月中旬),似乎Sencha Touch 2已经作为预览发布,并且在性能方面有显着的改进(这是我的一个关键因素)。但是,它缺少一些功能,似乎没有在Sencha网站上有很多演示/教程。

As of now (mid-December '11), it appears that Sencha Touch 2 has been released as a preview, and has significant improvements in performance (which is a key ingredient for me). However, it's missing some features, and doesn't seem to have many demos / tutorials yet on the Sencha website.

在SO的经验丰富的Sencha Touch开发者的宝贵意见(通过经验丰富,至少在移动领域,我的意思是你至少玩了一个周左右),你会建议我从开始Sencha Touch 2开始,或者通过学习1.x的运动,只是升级到2后?使用这个和其他框架的预览版本有什么优点/缺点,特别是在移动开发的不断变化的世界中工作?

In the valuable opinion of SO's seasoned Sencha Touch developers (and by seasoned, at least in the mobile realm, I mean that you've at least played with it for a week or so), would you recommend I start with Sencha Touch 2 from the get-go, or go through the motions of learning 1.x and just upgrading to 2 later on? What are the advantages / disadvantages of using "preview" versions of this and other frameworks, particularly when working within the ever-shifting world of mobile development?

感谢任何输入!

推荐答案

我在jQuery Mobile中为我的公司创建了一些概念证明。虽然我个人喜欢jQuery,jQM没有准备好生产环境,如果你想要一个光滑,响应,无bug的用户界面。这是在v1.0RC3天。这是一个稳定的版本,但我仍然感觉相同的方式,希望未来的版本将解决的缺点。我在运行了一些基准,一个焦点小组和一个试点计划(6 ppl)后作出了这个决定。所有说和做,我决定评估ST。

I created a few proof of concepts for my company in jQuery Mobile. While I personally love jQuery, jQM was not ready for a production environment if you wanted a slick, responsive, bug-free user interface. That was in the v1.0RC3 days. It is a stable release at the moment but I still feel the same way, hopefully future versions will address the shortcomings. I made this decision after running a number of benchmarks, a focus group and a pilot program(6 ppl). All said and done, I decided to evaluate ST.

Sencha Touch有最好的UI,IMO。然而,这个框架有一个强大的学习曲线。 API文档是完整的,虽然有教程潜伏在这里和那里,有没有说明从开始到结束的ST框架。我经常发现自己在深处寻找一个简短的一瞥,没有决心的解释。我觉得令人沮丧的是,Sencha团队没有解决这个问题。我听到很多关于 EXTjs 的刷牙,因为是ST的胎盘。 (是的,我只是说)真相是,如果一个人必须学习另一个框架来利用你感兴趣的,只是为了理解它是如何工作的,它的一个主要的失败。我不是学习EXTjs只是为ST ...

Sencha Touch has the best UI, IMO. However, there is a strong learning curve with this framework. API documentation is complete and while there are tutorials lurking here and there, there is NOTHING that spells out the ST framework from start to finish. I often find myself searching in the depths for a brief glimpse of an explanation with no resolve. I find it frustrating that the Sencha team hasn't addressed this. I hear a lot about brushing up on EXTjs first as that is the placenta of ST's birth. (yes, I just said that) Truth is, if one has to learn another framework to utilize the one you are interested in, just to understand how it works, its a major fail. I'm not learning EXTjs just for ST...

对于Sencha Touch,你应该精通MVC,面向对象编程,调试网络技术,并有一个坚实的理解的JavaScript。

For Sencha Touch, you should be versed in MVC, object oriented programming, debugging web technology and have a solid understanding of JavaScript.

现在真正的问题是1.x或2.x.像这样的情况是非常有争议的。应该在两个版本上进行资源和成本分析,以显示如果您将1.x代码移动到2.x以及与学习曲线等相关的任何其他开销,您的开发时间如何增加。因此,不是给我偏见的意见,我会告诉你我为我的公司(7k +员工)做了什么。

Now the real question is 1.x or 2.x. Situations like this are highly debatable. Resource and cost analysis should be done on both versions to show how your development time increases if you were to port 1.x code to 2.x and any other overhead associated with learning curves, etc. So instead of give you my biased opinion, I'll just tell you what I did for my company (7k + employees).

我的项目需要在某一特定日期达到某个里程碑,我当然可以不部署不处于生产状态的东西。简单来说,我不能使用beta的任何东西。因为ST2.x处于PR3阶段,所以它没有准备好生产。更不用说ST的许多主要功能目前从ST 2.x版本中缺失,虽然会在未来的版本中添加,因为它们可以继续生产稳定。

My project needed to be at a certain milestone by a certain date and I certainly can't deploy something that isn't in production status. Simply meaning I cannot use a beta for anything substantial. As ST2.x is in the PR3 stage, it isn't ready for production. Not to mention a lot of key features of ST are currently missing from the ST 2.x release, though will be added in future releases as they progress to production stable.

我在1.x中开发了我的应用程序,因为它是稳定的,有许多示例和文档可用,所以我可以生成一个应用程序 TODAY 。如果我在ST2开始,我将无法完成该应用程序。 API未冻结,缺少完整的文档,稀疏的示例,有限的社区资源和缺少的功能。我不能等待ST2(将是伟大的!),但不能冒险我的项目。

I developed my app in 1.x because it was stable, has numerous examples and documentation available so I could produce an app TODAY. If I started in ST2, I wouldn't be able to finish the app. The API is not frozen, lacking full documentation, sparse examples, limited community resources and missing features. I can't wait for ST2(going to be great!) but can't risk my project over it.

底线...如果你需要一个应用程序,去ST1,如果你可以搁置另外几个月,有时间更新您的应用程序,因为ST2 API冻结和功能添加回来,然后我会去那条路线。干杯。

Bottom line... if you need an app today, go with ST1, if you can hold off for another few months and have the time to make updates to your app as the ST2 API is frozen and features are added back in, then I would go that route. Cheers.

这篇关于是从Sencha Touch 2还是Sencha Touch 1.x开始?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆