从 Ext JS 3.x 升级到 Ext JS 4 Beta?
从 ExtJS 3.x 更新到 Ext JS 4 Beta 有哪些风险?
您是否期望与 Ext JS 3.x 配合使用的用户扩展也能与 Ext JS 4 Beta 配合使用?
难道就像用 ExtJs 4 替换 Ext Js 3.x 一样简单吗?
我应该更新还是等到官方稳定版本发布?
What are the risks associated with updating from ExtJS 3.x to Ext JS 4 Beta?
Would you expect that user extensions which work with Ext JS 3.x will work with Ext JS 4 Beta?
Would it be as simple as replacing Ext Js 3.x with ExtJs 4?
Should I update or wait until there is an official stable release?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
Ext 4 不向后兼容 Ext 3。预计需要花费大量时间进行升级和测试,具体取决于您现有应用程序的大小。一旦您看到对特定应用程序的影响,您将能够评估自己的特定风险。这一切都取决于。将会有迁移文档,因此希望这能在一定程度上减轻风险。
不,默认情况下不会。我预计大多数都需要升级,但这又取决于具体的组件。
不。您可能想观看此帖子 在 Sencha 论坛上。
Ext 4 is not backwards-compatible to Ext 3. Expect to spend significant time upgrading and testing, depending on how large your existing application is. Once you see the impact on your specific app, you'll be able to evaluate your own specific risk. It all depends. There will be migration documentation, so hopefully that will mitigate the risk somewhat.
No, not by default. I would expect most will need to be upgraded, but again, it depends on the specific component.
No. You might want to watch this thread on the Sencha forums.
我认为这个问题根本不是特定于 ext js 的。我认为以下问题的答案相同:“从
<我正在使用的某个库>
升级到<我正在使用的库的下一个版本的 Beta 版本>?
”答案是推荐的“否”。第三方库的测试版与网站的测试版不同。当最终版本发布时,它们可能会发生重大变化,并且您在测试版之上编写的任何代码都可能变得毫无用处。老实说,我对测试版所做的最多的事情就是尝试将其插入到我的项目中,以衡量最终版本发布后升级将涉及多少工作。
I think this question isn't specific to ext js at all. I think the answer to the same for the following question: "Upgrade from
<some library i'm using>
to<Beta version of next release for library I'm using>?
"And the answer is a recommended no. Betas for 3rd party libs aren't like betas for websites. They could have major changes by the time the final release comes out and any code you write on top of a beta could become useless. To be honest, the most I would do with a beta release is just try and plug it in to my project to gauge how much work is going to be involved in upgrading once the final release comes out.