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.
Related
I know many of you are asking how to migrate from Angular 1 to Angular 5. Or from 2 to 5. But my question is a little different. I have my personal application written in Angular 1.2.16 and I would like to know:
1. Is it worth to migrate at all?
2. How complicated that will be?
I know there is a change log in Angular's gitlab which is good thing but it is huge in between two versions. Most of the changes are bugfixes. But is there a lot of incompatibilites between those two versions?
I think that you cannot migrate directly from angularJS 1.2 to 1.6.9, it will be more difficult this way.
You have to make it step by step by looking to this migration guide:
https://docs.angularjs.org/guide/migration
They exposed detailed way to do it from:
1- Migrating from 1.2 to 1.3
2- Migrating from 1.3 to 1.4
3- Migrating from 1.4 to 1.5
Last step:
4- Migrating from 1.5 to 1.6
So you can look at each step and see the changes that you can modify and test if it works as expected.
it can be more time consuming this way but the level of success can be more important.
The existing code base in Angular 1.2 is huge with many custom directives, so I thought I will ask some experts before attempting.
I have studied the angular doc and am happy to see provision for an incremental upgrade using UpgradeAdapter. However, I am not clear the minimum version of Angular 1.x for the coexistence to work.
Specifically, can Angular 1.2 code co exist with Angular 2 in the same application such that I can incrementally upgrade it to Angular 2?
Do I have to upgrade Angular 1.2 to 1.4 first (for ng-router) and then try the co existence and incremental upgrade strategy?
I tried searching for a definitive answer on this and could not locate one.
Not a definite answer, but the source throws an error when not finding angular 1.x : https://github.com/angular/angular/blob/master/modules/%40angular/upgrade/src/angular_js.ts#L128
One of their first recommandation in the upgrade guide is the use of components, available in angular 1.5 though.
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.
Iam trying to implement my applicaion in ext js 2.3 using mvc architecture.
Can someone suggest me the classes available in ext 2.3 version to implement MVC.
Any links to extjs 2.3 tutorials will be highly useful.
Thanks in advance.
MVC has never been implemented in Ext 2.3, as far as I know. I also think that it is not worth the effort as 2.3 is three versions back and it is really outdated today.
If you have a motivation and resources to upgrade the existing app then opt to update the app to Ext 5.x. It would be much better spent development time.
In Extjs4.x, the MVC appears for the first time. So it can't be used in previous versions. It becomes mvvm in Extjs5.x. I recommend you to learn Extjs4.x or Extjs5.x.
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. :)