Results 1 to 2 of 2

Thread: reason for xtype?

  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 User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    40,050
    Vote Rating
    1381
      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
    Modus Create, Senior Frontend Engineer
    ________________
    Need any sort of Ext JS help? Modus Create is here to help!

    Check out my GitHub:
    https://github.com/mitchellsimoens

Posting Permissions

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