Why config for Touch MVC applications?

[basememara]

I am noticing more and more differences between the Touch and Ext JS 4 MVC conventions. Why in a Touch app must I put everything under 'config' or else it does not work?

Ext.define('MyApp.view.Viewport', {    extend: 'Ext.Panel',


    config: {
        fullscreen: true,
        layout: 'fit',
        items: [
            {
                xtype: 'panel',
                layout: {
                    type: 'card',
                    align: 'stretch'
                },
                items: [
                    {
                        xtype: 'somelist'
                    }
                ]
            }
        ]
    }
});

It is a bit unintuitive that I must put everything in the config because this is not the way it is done in non-MVC or even in the Ext JS 4 MVC way. Is this going to change in the Touch release, or is this intentional?

[jay@moduscreate.com]

That's because the new class system updates for Touch 2.0. "config" is insanely more powerful and diverse when it comes to Touch 2.0 relative to Ext JS 4.

In Ext 4, I rarely use config, because it doesn't necessarily buy you too much. In touch 2.0, you get a ton more out of the box. The framework code actually uses config all over the place.