Results 1 to 4 of 4

Thread: Use up/down or Ext.ComponentQuery for better performace

  1. #1

    Default Use up/down or Ext.ComponentQuery for better performace


    I usually use up/down using xtypes to reach a element. Now i find another method like Ext.ComponentQuery. I am not using itemIds. Want to know

    a. When to use which 1?
    b. Which is good for performance doing like ob.up('panel').up('panel') or using Ext.ComponentQuery directly.
    c. Ext.ComponentQuery if second parameter is not defined it searches globally?

  2. #2

  3. #3


    The difference here is the up/down/query/child methods start at a point whereas Ext.ComponentQuery.query does not start anywhere and will start resolving components at any level.
    When he says "start resolving components at any level". What does any level mean? does he mean to say start at level 0?

    My scenario: I have a tab panel, each tab will have 4-5 components max. I would need to search components in a single tab. So it it better to do a up/down or use ComponentQuery for this scenario?

  4. #4
    Sencha Premium User
    Join Date
    Apr 2007
    Sydney, Australia


    down() uses component query, rooted at the current container. up() just loops up through the component hierarchy.

Similar Threads

  1. tbar combo performace issue
    By tinyue in forum Ext: Discussion
    Replies: 1
    Last Post: 17 Jan 2014, 9:08 PM
  2. Replies: 2
    Last Post: 2 Jan 2013, 2:42 AM
  3. gxt performace in FormPanel
    By diegolovison in forum Ext GWT: Discussion
    Replies: 2
    Last Post: 16 Oct 2009, 11:22 AM
  4. Window Performace in old machines
    By dtondo in forum Ext 2.x: Help & Discussion
    Replies: 2
    Last Post: 24 Aug 2009, 7:17 AM
  5. performace in form validation
    By fother in forum Community Discussion
    Replies: 11
    Last Post: 26 Jan 2009, 6:16 AM

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