1. #1
    Sencha Premium Member
    Join Date
    Sep 2012
    Posts
    12
    Vote Rating
    1
    brettAV is on a distinguished road

      0  

    Default reason for xtype?

    reason for xtype?


    Can anyone explain why we have xtype? I understand that it allows for lazy instantiation but why was this alias implementation chosen over just using the class name. Why do we have:
    items [
    {
    xtype: something
    }
    ]

    ..instead of...

    items [
    {
    cls: "org.view.Something"
    }
    ]

    Why do we have namespaces if we're just going to refer to classes by their xtype/alias?

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    St. Louis, MO
    Posts
    33,641
    Vote Rating
    434
    mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of

      0  

    Default


    xtype is something that has been in Ext JS for many many years and allowed for lazy instantiation and smaller code. Today you can use xclass instead of xtype to instantiate but resolving a component via ComponentQuery uses xtypes
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    http://www.JSONPLint.com - Source to lint your JSONP!

    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!

    When posting code, please use BBCode's CODE tags.