Results 1 to 2 of 2

Thread: reason for xtype?

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Sencha Premium Member
    Join Date
    Sep 2012
    Posts
    13
    Vote Rating
    1
      0  

    Default 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 - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    39,412
    Vote Rating
    1288
      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 @LikelyMitch
    Sencha Inc, Senior Software Engineer
    ________________
    Learn BBCode and use it!

    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 in print!

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

Posting Permissions

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