1. #1
    Sencha User Surykat's Avatar
    Join Date
    Jul 2011
    Location
    BIALYSTOK, Poland
    Posts
    58
    Answers
    1
    Vote Rating
    1
    Surykat is on a distinguished road

      0  

    Default Answered: [PR2] Multiple opened views couse performance problem

    Answered: [PR2] Multiple opened views couse performance problem


    I observed a strange behavior with opening some view for many times and I want to know is it normal..

    When I switch my view with:
    Code:
    Ext.Viewport.setActiveItem({ xtype: 'myviewwidget'});
    In page resources there are created component with id for example:
    Code:
    id = "ext-myviewwidget-1"
    I switch now my view to another, but this component stays in page code. I checked it in PR1 release and the same situation is there, BUT...

    In PR2 when I open many views, speed of my application slows a lot. In PR1 application still works like a charm.

    I want to know if that strange problem is coused by my bad component initialization, or mayby I need to somehow destroy earlier created components when I switch view to another?

    What is the best practice? Or mayby it's a PR2 bug which would be fixed in next release?

  2. The problem was coused by selectfield listeners of 'change' event, which was loaded every time the view was created (there was couple of sort methods and binding).

    I rewrite that listeners to MVC pattern (into controller class) and problem is gone.

  3. #2
    jay@moduscreate.com's Avatar
    Join Date
    Mar 2007
    Location
    Frederick MD, NYC, DC
    Posts
    16,360
    Answers
    102
    Vote Rating
    81
    jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all

      0  

    Default


    Can you post an example for the dev team to toy with?

  4. #3
    Sencha User Surykat's Avatar
    Join Date
    Jul 2011
    Location
    BIALYSTOK, Poland
    Posts
    58
    Answers
    1
    Vote Rating
    1
    Surykat is on a distinguished road

      0  

    Default


    Is it possible that it is coused by my modification of not deleting listeners during constructor which i described in that topic?
    http://www.sencha.com/forum/showthread.php?155631-PR2-delete-config.listeners-purposeful-behavior

    I
    tried to build a simple solution to show that example but I didn't notice nothing strange in performance with original source of PR2 ;/ Now I'm trying to modify a project to not use a hard binded listeners but to wrap that code in controller.

  5. #4
    Sencha User Surykat's Avatar
    Join Date
    Jul 2011
    Location
    BIALYSTOK, Poland
    Posts
    58
    Answers
    1
    Vote Rating
    1
    Surykat is on a distinguished road

      0  

    Default


    The problem was coused by selectfield listeners of 'change' event, which was loaded every time the view was created (there was couple of sort methods and binding).

    I rewrite that listeners to MVC pattern (into controller class) and problem is gone.

Thread Participants: 1