How best to move to 3.0?

[Sesshomurai]

Hi,
Congrats on the core release. It looks as though the framework is getting layered and broken apart with core being the base?

So for those of us using 2.2.1 what is the suggested migration technique to 3.0? Is it backwards compatible or will there be a list of things we should expect to change to move to 3.0?

thanks and awesome work as usual.

[evant]

There should be a minimal amount of changes you'll need to make to upgrade from 2 to 3. In fact, I can't think of any breaking changes off the top of my head, though there are a few minor ones.

[Sesshomurai]

Thanks Evan.

I presume the other packages will combine on top of core and be similarly backward compatible?

[evant]

Correct, if you're using the full Ext then the core stuff will just be transparent.

[iamleppert]

Are we still waiting on Ext.Direct, the flash charting API, etc? Is there going to be a new widget layer released the replaces 2.2, or are the "old" widgets going to be backwards compatible? If so, how to combine the two?

[evant]

The container/component model is staying the same. Ext.direct is a completely new namespace, so there's no backwards compat issues there. The flash charts extend box component, so they can be used in layouts.

[Giraf]

I'm kinda time restrained, so after reading this thread I'll start a new development on 2.2.1 today, and then upgrade to v3.

Can I use the full public version, and wait to buy and upgrade the code to a V3 license, that shouldn't be a problem right!?