1. #1
    Ext JS Premium Member Steffen Hiller's Avatar
    Join Date
    Mar 2008
    Posts
    767
    Vote Rating
    23
    Steffen Hiller will become famous soon enough Steffen Hiller will become famous soon enough

      0  

    Default Ext.ComponentQuery cache disabled?

    Ext.ComponentQuery cache disabled?


    Anybody know why in 2.1 Beta 3 (not sure since which version) the Ext.ComponentQuery cache is disabled? At least it seems so, since the following lines are commented in the query method:

    Code:
    //                query = this.cache[selector];
    //                if (!query) {
    //                    this.cache[selector] = query = this.parse(selector);
    //                }
    I was just checking to see if there is any performance gain by using refs in the controller.
    If one component is referenced more than once, it seems so, but if the Ext.ComponentQuery cache would work, there wouldn't be any benefit performance wise using refs in controllers, am I right?

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    35,704
    Vote Rating
    750
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    Better perf would be to start from a root to resolve a component instead of using Ext.ComponentQuery.query as it starts from the beginning and will go through all levels to find matches.

    This change was done way back in January also. Comment was only "Remove infinite cache in ComponentQuery."
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    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.

  3. #3
    Ext JS Premium Member Steffen Hiller's Avatar
    Join Date
    Mar 2008
    Posts
    767
    Vote Rating
    23
    Steffen Hiller will become famous soon enough Steffen Hiller will become famous soon enough

      0  

    Default


    Quote Originally Posted by mitchellsimoens View Post
    Better perf would be to start from a root to resolve a component instead of using Ext.ComponentQuery.query as it starts from the beginning and will go through all levels to find matches.

    This change was done way back in January also. Comment was only "Remove infinite cache in ComponentQuery."
    Hmm 'infinite cache' sounds like it had a memory leak then.
    Yeah, I know that of the root, but refs don't use a root either.

Thread Participants: 1

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar