Results 1 to 2 of 2

Thread: Why config for Touch MVC applications?

  1. #1
    Sencha User
    Join Date
    Nov 2011
    Location
    Toronto
    Posts
    105
    Vote Rating
    2
      0  

    Exclamation Why config for Touch MVC applications?

    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?

    Code:
    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?

  2. #2
    Sencha User jay@moduscreate.com's Avatar
    Join Date
    Mar 2007
    Location
    DC Area =)
    Posts
    16,364
    Vote Rating
    86
      0  

    Default

    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.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •