1. #31
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    35,672
    Vote Rating
    747
    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


    Think of a tab panel with deferred rendering. You may still need to resolve components that haven't been rendered yet.
    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.

  2. #32
    Sencha User Daniil's Avatar
    Join Date
    Jun 2010
    Location
    Saint-Petersburg, Russia
    Posts
    972
    Vote Rating
    105
    Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light

      0  

    Default


    OK, thank you.

    Generally, it was just thoughts of somehow improve something Thank you for your time!
    Ext.NET - ASP.NET for Ext JS
    MVC and WebForms
    Examples | Twitter

  3. #33
    Sencha User skirtle's Avatar
    Join Date
    Oct 2010
    Location
    UK
    Posts
    3,338
    Vote Rating
    248
    skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of

      0  

    Default


    Quote Originally Posted by Daniil View Post
    Yes, it is how the things are now.

    But I rather talking about a possible enhancment. Does it really need to instantiate something if it might not be rendered at all?
    It's been discussed a number of times but it isn't totally trivial to implement as a general feature. Occasionally I implement it myself in my apps. e.g. If I have a main tabpanel in my app then I populate the tabs in their beforeRender methods. Done correctly it can be very effective at improving performance in applications that have a lot of unrendered components.

  4. #34
    Sencha User
    Join Date
    Jun 2008
    Posts
    137
    Vote Rating
    6
    jchau has a little shameless behaviour in the past

      0  

    Default


    Quote Originally Posted by skirtle View Post
    It's been discussed a number of times but it isn't totally trivial to implement as a general feature. Occasionally I implement it myself in my apps. e.g. If I have a main tabpanel in my app then I populate the tabs in their beforeRender methods. Done correctly it can be very effective at improving performance in applications that have a lot of unrendered components.
    This is an interesting approach. How much overhead is it to have unrendered components? Since no dom elements for them have been created, is the overhead mostly the time to instantiate those objects and their memory footprint? AFAIK, most of the performance issues with ExtJS happens during layout and rendering.

  5. #35
    Sencha User skirtle's Avatar
    Join Date
    Oct 2010
    Location
    UK
    Posts
    3,338
    Vote Rating
    248
    skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of skirtle has much to be proud of

      0  

    Default


    Quote Originally Posted by jchau View Post
    Since no dom elements for them have been created, is the overhead mostly the time to instantiate those objects and their memory footprint? AFAIK, most of the performance issues with ExtJS happens during layout and rendering.
    The time taken to instantiate a component is usually much smaller than the time taken for rendering or layout but if you have huge numbers of unrendered components then it can add up. A tabpanel with many tabs is a good candidate. It should be noted that all I'm proposing is to shuffle time around: cut the time taken for the initial load in favour of slightly slower tab transitions. This is what Daniil seemed to be asking for.

    It's just another technique to have in your arsenal. As ever, the only golden rule for optimizing is to take some meaningful measurements before you do anything else.

  6. #36
    Sencha User Daniil's Avatar
    Join Date
    Jun 2010
    Location
    Saint-Petersburg, Russia
    Posts
    972
    Vote Rating
    105
    Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light

      0  

    Default


    It's been discussed a number of times
    Probably, I missed that. It is a little time ago I started to ponder about performance and, in general, dive deeper into Ext JS

    @skirtle, thank you! It is nice to know that the idea makes sense at all and even implemented and works.

    I will bear in mind that approach to instantiate components in a beforeRender listener. Thank you again.
    Ext.NET - ASP.NET for Ext JS
    MVC and WebForms
    Examples | Twitter

  7. #37
    Sencha User Daniil's Avatar
    Join Date
    Jun 2010
    Location
    Saint-Petersburg, Russia
    Posts
    972
    Vote Rating
    105
    Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light Daniil is a glorious beacon of light

      1  

    Default


    Carefully use Ext.suspendLayouts/Ext.resumeLayouts. A possible problem is discussed here.
    http://www.sencha.com/forum/showthread.php?260320
    Ext.NET - ASP.NET for Ext JS
    MVC and WebForms
    Examples | Twitter

  8. #38
    Ext JS Premium Member
    Join Date
    Feb 2009
    Posts
    422
    Vote Rating
    1
    Jangla is on a distinguished road

      0  

    Default


    We have some pretty heavy grids that have extensive templates in the main column to give the user a really nice view of a lot of data in one hit.

    So, for performance, what's quicker; a templatecolumn (which would likely require more fields on the grid store to pre-format the data nicely) or a renderer that creates a data object from manipulations on the store on a per row basis and applies an xtemplate on it?

    I suppose nested within this question are a few other performance details - like what's quicker, a convert function on a store field or manipulating the store data for each row before applying the template?

  9. #39
    Sencha Premium Member vadimv's Avatar
    Join Date
    Sep 2010
    Location
    Chisinau, Moldova
    Posts
    647
    Vote Rating
    25
    vadimv will become famous soon enough vadimv will become famous soon enough

      0  

    Default


    Quote Originally Posted by Jangla View Post
    I suppose nested within this question are a few other performance details - like what's quicker, a convert function on a store field or manipulating the store data for each row before applying the template?
    I prefer a convert function since what's about data should be done in data layer, as much as possible...and the code is cleaner, easy for others to understand and templates are lighter.

  10. #40
    Ext JS Premium Member
    Join Date
    Feb 2009
    Posts
    422
    Vote Rating
    1
    Jangla is on a distinguished road

      0  

    Default


    Quote Originally Posted by vadimv View Post
    I prefer a convert function since what's about data should be done in data layer, as much as possible...and the code is cleaner, easy for others to understand and templates are lighter.
    Yea, that's a good point even if performance were the same - keeping all the data trasforms in the model (or store fields) makes for more readable code. My only concern with this is having a store with many more fields if your data needs to be represented many different ways in the grid. But I'm hoping the performance hit for this would be more minimal than having to transform it on the fly each time a row in the grid was rendered.

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