19 Feb 2013 7:42 AM #31
- Join Date
- Mar 2007
- St. Louis, MO
- Vote Rating
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
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 firstname.lastname@example.org
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.
19 Feb 2013 8:08 AM #32
19 Feb 2013 12:29 PM #33
19 Feb 2013 5:51 PM #34
19 Feb 2013 7:52 PM #35
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.
19 Feb 2013 8:35 PM #36
It's been discussed a number of times
@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.
3 Apr 2013 9:02 PM #37
8 Apr 2013 5:36 AM #38
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?
10 Apr 2013 5:17 AM #39
10 Apr 2013 5:44 AM #40