TNS 3.0 Android Runtimes compatibility with TNS 2.5 Core-Modules #740

Closed
NathanaelA opened this Issue Apr 6, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@NathanaelA
Contributor

NathanaelA commented Apr 6, 2017

This is more a kudo's & continued feature request.

Tell us about the FEATURE!

I installed the 3.0RC command line, and also started creating a new 2.5 app around the same time. A couple days later I installed the runtimes (didn't even think to specify for 2.5) and it installed the 3.0RC runtimes while I still had the the 2.5 TNS-Core-Modules & 2.5 widgets installed in this app.

I decided what the hell, lets see what happens. I am very impressed; I haven't seen any issues using the 3.0RC android runtimes with the 2.5 TNS core modules. So much so, that I am going to ask that this be supported for a while in the future. The changes in 3.0 are drastic enough that I will have to wait for a while to update enough of my plugins before I can even switch to 3.0. But in the meantime if I can continue to use the 3.0 engine and get the bug fixes in the runtimes that would be awesome.

So kudo's to the team! Can I request that we continue to maintain backwards compatibility with the 2.5 TNS core modules and widgets?

If you can think of any breaking changes in the engine against 2.5 widgets/core please let me know. Thanks!

@NathanaelA

This comment has been minimized.

Show comment
Hide comment
@NathanaelA

NathanaelA Apr 6, 2017

Contributor

@Pip3r4o - I just thought of another reason why this is really important feature. I shared a private link with you the other day; this would be VERY VERY helpful if I can continue to run both 2.5 and 3.0 core-modules on the same 3.0 runtime (the app for this project is also currently using 3.0RC Android runtimes w/ TNS 2.5 core-modules).

This is an extremely important that this feature remains for this project at least for the next several months... I know at some time this may not be possible, but as long as it can, the happier I will be...

Contributor

NathanaelA commented Apr 6, 2017

@Pip3r4o - I just thought of another reason why this is really important feature. I shared a private link with you the other day; this would be VERY VERY helpful if I can continue to run both 2.5 and 3.0 core-modules on the same 3.0 runtime (the app for this project is also currently using 3.0RC Android runtimes w/ TNS 2.5 core-modules).

This is an extremely important that this feature remains for this project at least for the next several months... I know at some time this may not be possible, but as long as it can, the happier I will be...

@Pip3r4o

This comment has been minimized.

Show comment
Hide comment
@Pip3r4o

Pip3r4o Apr 7, 2017

Contributor

@NathanaelA Thank you for your words!

We develop the runtimes with compatibility in mind and don't usually intend to break that compatibility, unless there are valid reasons to do otherwise. Still, should there be any breaking changes we need to communicate them in a timely manner, and provide a smooth migration path.

Contributor

Pip3r4o commented Apr 7, 2017

@NathanaelA Thank you for your words!

We develop the runtimes with compatibility in mind and don't usually intend to break that compatibility, unless there are valid reasons to do otherwise. Still, should there be any breaking changes we need to communicate them in a timely manner, and provide a smooth migration path.

@Pip3r4o Pip3r4o closed this Apr 12, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment