Comments on: Random notes on DataGroup and Spark Containers in Flex 4 (Gumbo) http://www.hulstkamp.com/2009/06/14/random-notes-on-datagroup-in-flex-4-gumbo/371 andy hulstkamp blog about rich internet applications, flex, flash, java, webapps, web, code, experiments Thu, 29 Jul 2010 16:09:27 +0000 http://wordpress.org/?v=2.6.1 By: Steven Shongrunden http://www.hulstkamp.com/2009/06/14/random-notes-on-datagroup-in-flex-4-gumbo/371#comment-91 Steven Shongrunden Fri, 10 Jul 2009 21:25:42 +0000 http://www.hulstkamp.com/?p=371#comment-91 In case you're interested I just posted a sample Flex application that visually demonstrates the difference between using the itemRenderer and itemRendererFunction properties: http://flexponential.com/2009/07/10/performance-implications-of-the-list-itemrenderer-vs-itemrendererfunction-properties/ In case you’re interested I just posted a sample Flex application that visually demonstrates the difference between using the itemRenderer and itemRendererFunction properties:

http://flexponential.com/2009/07/10/performance-implications-of-the-list-itemrenderer-vs-itemrendererfunction-properties/

]]> By: Andy Hulstkamp http://www.hulstkamp.com/2009/06/14/random-notes-on-datagroup-in-flex-4-gumbo/371#comment-83 Andy Hulstkamp Thu, 25 Jun 2009 06:25:55 +0000 http://www.hulstkamp.com/?p=371#comment-83 Steven, thanks for your remarks. You are right, this wasn't very clear, I actually stated the facts in this <a href="http://www.hulstkamp.com/2009/06/15/working-with-huge-amount-of-data-in-flex-4-gumbo/382" rel="nofollow">post</a> but missed to be more precise here. will update thanks Steven,

thanks for your remarks. You are right, this wasn’t very clear, I actually stated the facts in this post but missed to be more precise here.

will update

thanks

]]> By: Steven Shongrunden http://www.hulstkamp.com/2009/06/14/random-notes-on-datagroup-in-flex-4-gumbo/371#comment-82 Steven Shongrunden Wed, 24 Jun 2009 00:54:09 +0000 http://www.hulstkamp.com/?p=371#comment-82 One very subtle correction to your well said notes above: "Virtualization cannot be used when using the ItemRendererFunction. Well, the function can be set, but no virtualization will be used." Actually virtualization will be used even when an item renderer function is defined, but in that case item renderer recycling will not happen. Instead renderers will be created and destroyed roughly as they come in and out of view. (Compare this to the non-virtual case where every renderer is instantiated at startup). ItemRenderer recycling can be more performant than creation and destruction (depending on the renderers) so if you want to get the best performance it's typically better to define an itemRenderer rather than an itemRendererFunction. One very subtle correction to your well said notes above:

“Virtualization cannot be used when using the ItemRendererFunction. Well, the function can be set, but no virtualization will be used.”

Actually virtualization will be used even when an item renderer function is defined, but in that case item renderer recycling will not happen. Instead renderers will be created and destroyed roughly as they come in and out of view. (Compare this to the non-virtual case where every renderer is instantiated at startup). ItemRenderer recycling can be more performant than creation and destruction (depending on the renderers) so if you want to get the best performance it’s typically better to define an itemRenderer rather than an itemRendererFunction.

]]>