Parallel usage for BIG projects.

[Arthur Kovacs]

Hello, 

I am not certain this is the place to put this issue, but last night I had an interesting thought.

Me and my colleagues, we have started a really big project in the last 6-7 months, and we are still in the phase where we can switch versions ... freely ... But switching from now to 2.0 beta is a big commitment. (And doing this down the road is completely out of the question, 2 years of work at the end of if rewritten in 2.0 is a complete unicorn from an economical standpoint).

So I had the following idea, a big project it should have most of its components decoupled, and we could actually use two versions of angular (1.3-1.4 and 2.0b) for different modules.

This particularly applies in our case because we have a the base of the project, the infrastructure to say so, and then we have several modules already developed in a alpha-beta stage, now, one of those modules is a mammoth that needs JointJS and a lot black-magic angular 1.4 work, the initial thought of switching that module to 2.0 now I think is ... suicide :).

So my idea / question / conversation starter is couldn't we run angular 2.0 or the 1.3-1.4 in a different namespace than the other one ? The infrastructure of the project and the new, more usual modules can be developed in angular 2.0, while the more difficult ones could remain in 1.3-1.4 up until 2.0 is stable enough to make the transition to. In the end, we are trying to develop our modules lile IN  > [ ] > OUT, we are not interested what is in the middle as long as the result is what we want.

Thanks,

Arthur.

[Sander Elias]

Hi Arthur,

The ngNewrouter that comes with 1.4 will support just that. You can mix and match 1.x and 2.x version in the app.

Regards

Sander

[Arthur Kovacs]

That is awesome news, I can hardly wait to start messing with 2.0 :).

It isn't yet clear to me how the router could enable the usage of both versions, but I'll go and read this http://angular.github.io/router/ asap.

Thanks Sander!

--
You received this message because you are subscribed to a topic in the Google Groups "AngularJS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/angular/kYhYWf_qbqI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to angular+u...@googlegroups.com.
To post to this group, send email to ang...@googlegroups.com.
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

--

Arthur Kovacs - Senior FrontEnd Developer linkedin.com/in/arthurianx
Senior FrontEnd Developer S.C. SHE Informationen Technologies S.R.L. Cladirea mica TCI Invest Str. Alexandru Vaida Voievod, nr. 2-3, parter. Cluj Napoca ROMANIA Web: http://www.she.net/ Mobile : +4(0721).55.66.00 Yahoo: m3s_...@yahoo.com Skype: arthur.kovacs85

[Sander Elias]

Hi Arthur,

There isn't much there to read yet. I have yet to read it somewhere, however, Brian explained this at ng-conf. In its current state the router isn't yet very useful. Brian is still working on a few issues before he can go and finishes all the details.

However, if you go and play with it, you can already see its potential!

Regards

Sander