Backwards compatibility (DEPRECATED)

[watrboy00]

Since we are in beta 3 (I believe) and this is a new framework with notes saying that things might change...should we already be seeing this?

// Backwards compatibility (DEPRECATED)
Ext.Container.LAYOUTS = Ext.layout.TYPES;

[watrboy00]

// Backwards compatibility with desktop
Ext.CompositeElementLite = Ext.CompositeElement;

It's a mobile platform...who cares about the desktop!

[Jamie Avins]

We're trying to keep some level of familiarity across the platforms, but this one in particular will probably go away.

[watrboy00]

Oh for sure. I think there should be HUGE similarities between the two. I just don't think there should be backward compatibility all over the place if there wasn't a previous version to be backward compatible with. Just want to see that the framework isn't being bloated for no apparent reason.

[watrboy00]

These are the other ones...

//backwards compatibility
Ext.data.DataProxy = Ext.data.Proxy;

//[deprecated 5.0]
Ext.ns('Ext.data.Record');

//Backwards compat
Ext.data.Record.id = Ext.data.Model.id;
//[end]

//backwards compatibility, remove in Ext JS 5.0
Ext.data.HttpProxy = Ext.data.AjaxProxy;

//backwards compatibility, will be deprecated in 5.0
this.nocache = this.noCache;

// backwards compat, convert idPath or id / success
// DEPRECATED - remove this in 5.0
Ext.applyIf(config, {
idProperty : config.idPath || config.id,
successProperty: config.success
});

// backwards compat
Ext.data.SimpleStore = Ext.data.ArrayStore;

//backwards compatibility - deprecate in next major release
this.label = this.label || this.fieldLabel;

[stever]

Well, I imagine it is because a site's data structure is often built on top of Ext classes. To provide a desktop and a mobile UI, one can switch out the UI layer to the appropriate one, but much of how your data works will be the same and so ought to be the underlying layers where appropriate.