I want to upgrade the enterprise application that was developed in Ext JS 1.0 to the latest version? does anyone know any idea about the process? it seems that some of the methods/properties have been changed, in that case, do I have to rewrite the whole system?
I'm afraid that you would to rewrite it, when this is 1.0 vs. 7.5.
When creating a new project and then adding the legacy code, at least the config files would work - but likely nothing would work. The problem with partial rewrites is that commonly there's clutter left, rewriting from scratch and migrating class by class leaves the least clutter. That's alike comparing Windows 1.01 to 11; when the current version wasn't written in an IDE, the code quality may also be low. sencha-cmd will in best case update the config files, in case it can even read them, but it won't update JS classes.
Related
Currently our application is on the Angular 2.0 version.
How important is it to keep updating it as and when Angular releases a new update?
In the changelog i dont see any breaking changes that need to be addressed immediately going from 2.0.0 to 2.4.2.
So is it necessary to upgrade our application from 2.0.0 to 2.4.2? Or should we just wait till there is another big release?
I would suggest upgrading to newer version of major release when:
You came across the issue/bug which was fixed in newer version.
There's a new feature which will come in handy.
Changes positively affecting performance - e.g. AOT compiler which can be a deal breaker to some people, but it might require some code to be rewritten to make it AOT-friendly.
Angular uses semantic versioning. Going from 2.0.x to 2.0.y means that a bug has been fixed. It's usually a good idea to avoid having bugs. Going from 2.0.y to 2.1.0 means that a new feature is available. You might want or need to benefit from this new feature.
You won't have any breaking change until the next major version, which will be 4.0.0 (there won't be a 3.x version, in order to align angular and its router versions)
As mentioned on this link under Best Practices Section
Best practices
Keep current with the latest Angular library releases. We regularly update our Angular libraries, and these updates may fix security
defects discovered in previous versions. Check the Angular change log
for security-related updates.
Don't modify your copy of Angular. Private, customized versions of Angular tend to fall behind the current version and may not include
important security fixes and enhancements. Instead, share your
Angular improvements with the community and make a pull request.
Avoid Angular APIs marked in the documentation as “Security Risk.”
I have an AngularJS application written using AngularJS 1.4. We need to adapt this to work with different languages and of course sometime in the future we need to move to AngularJS 2.0.
Has anyone out there used the i18n and l10n features of both AngularJS 1.4 and 2? From what I understand 1.4 adds new features over 1.3 but I cannot find any information on what has changed :-(
What I would like to know is if there are some big differences. Big enough that we should wait until AngularJS 2.0 before starting internationalization.
Please do not close this question. Yes I know it may not fit exactly as a perfect question but I am pretty sure there are developers out there who are asking the same question as me.
Since AngularJS 2.0 will be a whole rewrite I don't think it is a good idea to rely on being able to migrate from previous versions. Moreover, it is not going to be released soon and even version 1.4 is not stable yet.
You should be always using the latest stable version. However, there is an official thread about migrating.
If you want to learn about specific changes e.g. l10n and i18n have a look at the changelog.
We want to convert our web app to angularjs, the problem is we need to support IE8 so only option is to stick with angularjs version 1.2. The question is it safe to go with this version? As 1.3 is already out and soon version 2.0 will be there too, so in near future (like 8-12 months) if we dropped IE8 support and then want to migrate to 1.3 or even 2 how much effort it will be?
Migration from Angular 1.2 to 1.3 is far more easier as compared to moving to Angular 2.0
There is even a migration guide to migrate from 1.2 to 1.3. So migrating would be possible to 1.3 or 1.4 or 1.x.
There is a bit of paradigm shift when it comes to Angular 2.0. The migration path is still not clear and we even don't know whether one is possible.
Update: This video from ngconf 2015, gives some useful insight into how build today with 1.3, that makes transition easy.
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?
What are the risks associated with
updating from ExtJS 3.x to Ext JS 4
Beta?
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.
Would you expect that user extensions
which work with Ext JS 3.x will work
with Ext JS 4 Beta?
No, not by default. I would expect most will need to be upgraded, but again, it depends on the specific component.
Would it be as simple as replacing Ext
Js 3.x with ExtJs 4?
No. You might want to watch this thread on the Sencha forums.
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.
My web project (to be launched in a few months) is currently using CakePHP 1.2.5 / PHP 5.1.6 / MySQL 5.0.77.
From a performance point of view, is it a good idea to upgrade to 1.3?
Will it make it easier to later upgrade to the (PHP5-only) CakePHP 2?
I'd say it depends on when you expect to get your site out the door. 1.3 is currently in alpha status and probably won't be officially stable for a while. While the changes being made between 1.2 and 1.3 shouldn't have a huge impact on the overall stability, the new features being put in might still be buggy. The question is, is there anything in 1.3 that you absolutely need now?
If you want to release your site soon on an unstable version of 1.3, you need to make sure through a lot of testing that the parts you're using are performing as expected. If your project will evolve over time together with 1.3, let's say over the next 6 months or so, and you continuously keep updating, you'll probably be in better shape. For example, I developed a project on the 1.2 beta and there were a few bugs in Set, which tripped me up, but got ironed out 'till the final release.
For a long-term project, I'd prefer the 1.3 branch, while for a near-future release I'd stick with 1.2.5 for now. You can keep an eye on the Migration Guide to avoid API calls that will be deprecated in 1.3, to allow for an easier later upgrade.
I think an upgrade is always a better opition IF you have time to do it. Im not into CataPHP but, i would do any upgraded if i have enough time before the release.
i'd upgrade early situation allows. if you haven't you might want to start using the cakephp/simpletest test to make sure things work just fine.
i took my time upgrading from 1.1 to 1.2 and had a lot of 'fun' going through my codes. :)