Data package differences in ExtJS and Sencha Touch

[tkolo]

Until today i was convinced that data package is shared between ExtJS and Sencha Touch, but i realized it's not. Since it'd be a hard work to browse all the documentation/code to just write down all the differences, could you provide me with a short summary? I'd be also nice to know why it's not shared.

[mitchellsimoens]

The biggest difference is the config object system that Touch uses but Ext JS does not. For instance, this is how you define a model in Ext JS:

Ext.define('MyModel', {
    extend : 'Ext.data.Model',

    fields : ['foo', 'bar']
});

But in Touch it should be:

Ext.define('MyModel', {
    extend : 'Ext.data.Model',

    config : {
        fields : ['foo', 'bar']
    }
});

[tkolo]

Does it mean that my ExtJS model cannot be simply reused if i want to write touch interface for my application?

[mitchellsimoens]

Not out of the box for Ext JS 4 and ST 2

[tkolo]

Oh well, thanks for your answers. Two questions remain for me.

1. As i already asked, what's the reasoning behind this? Thinking about it, i can't find a reason why not to share data package, but i don't know ST at all.
2. Is it a subject to change in the future?

[tobiu]

well, you can use it for both in case you do not put anything inside config but on class level. sencha touch will copy it over to config, but you will get lots of deprecated messages.

if you use config it will break for ext js.

if you try to create own logic to put the configs into the config object in case it is touch, you will still get those messages, because the sencha copying logic gets applied as an override as well and probably get executed before your own changes.

best regards
tobiu