Comments on: Performance implications of the List itemRenderer vs. itemRendererFunction properties http://flexponential.com/2009/07/10/performance-implications-of-the-list-itemrenderer-vs-itemrendererfunction-properties/ Programming under the influence of Flex Sun, 22 Jan 2012 01:08:12 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Flexponential » Grouping items in a Flex mobile List http://flexponential.com/2009/07/10/performance-implications-of-the-list-itemrenderer-vs-itemrendererfunction-properties/comment-page-1/#comment-2104 Flexponential » Grouping items in a Flex mobile List Tue, 30 Nov 2010 07:37:30 +0000 http://flexponential.com/?p=88#comment-2104 [...] your List won’t be able to take advantage of item renderer recycling. See this post for more [...] [...] your List won’t be able to take advantage of item renderer recycling. See this post for more [...]

]]> By: Franto http://flexponential.com/2009/07/10/performance-implications-of-the-list-itemrenderer-vs-itemrendererfunction-properties/comment-page-1/#comment-631 Franto Tue, 23 Feb 2010 10:42:24 +0000 http://flexponential.com/?p=88#comment-631 I've found one problem with virtual layout: There is problem with correct size of Spark List when useVirtualLayout is used for VerticalLayout. Here is ADobe bug ticket: http://bugs.adobe.com/jira/browse/SDK-25605 please vote for it. Thank you I’ve found one problem with virtual layout:

There is problem with correct size of Spark List when useVirtualLayout is used for VerticalLayout. Here is ADobe bug ticket:

http://bugs.adobe.com/jira/browse/SDK-25605

please vote for it. Thank you

]]> By: Flexponential » Different ways of assigning an item renderer in Flex 4 http://flexponential.com/2009/07/10/performance-implications-of-the-list-itemrenderer-vs-itemrendererfunction-properties/comment-page-1/#comment-149 Flexponential » Different ways of assigning an item renderer in Flex 4 Mon, 02 Nov 2009 19:38:41 +0000 http://flexponential.com/?p=88#comment-149 [...] Flex 4 introduced the concept of an “item renderer function” that provides the ability to define multiple item renderers within one DataGroup depending on the item. This is accomplished in DataGroup via the itemRendererFunction property. Read more about using the itemRendererFunction property. [...] [...] Flex 4 introduced the concept of an “item renderer function” that provides the ability to define multiple item renderers within one DataGroup depending on the item. This is accomplished in DataGroup via the itemRendererFunction property. Read more about using the itemRendererFunction property. [...]

]]> By: Steven Shongrunden http://flexponential.com/2009/07/10/performance-implications-of-the-list-itemrenderer-vs-itemrendererfunction-properties/comment-page-1/#comment-12 Steven Shongrunden Thu, 23 Jul 2009 22:05:14 +0000 http://flexponential.com/?p=88#comment-12 Actually, to correct my last comment it looks like if you define a new layout on a List then useVirtualLayout="true" will be pushed into the layout unless the List has specifically defined useVirtualLayout="false". Actually, to correct my last comment it looks like if you define a new layout on a List then useVirtualLayout=”true” will be pushed into the layout unless the List has specifically defined useVirtualLayout=”false”.

]]> By: Steven Shongrunden http://flexponential.com/2009/07/10/performance-implications-of-the-list-itemrenderer-vs-itemrendererfunction-properties/comment-page-1/#comment-11 Steven Shongrunden Mon, 20 Jul 2009 02:39:14 +0000 http://flexponential.com/?p=88#comment-11 The VerticalLayout/HorizontalLayout/TileLayout classes each support virtualization, but it is off by default. However the default List skin uses a VerticalLayout and sets useVirtualLayout to true. So if you were to use a List out of the box like this: <s:List> <fx:String>item 0</fx:String> <fx:String>item 1</fx:String> ... </s:List> Then virtualization would be on. You could turn it off by setting the useVirtualLayout property on the List to false. This value then gets pushed down to the List's layout: <s:List useVirtualLayout="false"> ... </s:List> But if you were to define a new layout on the List then virtualization will not be on by default unless you specify useVirtualLayout="true" on the List (or the layout): <s:List useVirtualLayout="true"> <s:layout> <s:HorizontalLayout /> </s:layout> ... </s:List> The VerticalLayout/HorizontalLayout/TileLayout classes each support virtualization, but it is off by default.

However the default List skin uses a VerticalLayout and sets useVirtualLayout to true. So if you were to use a List out of the box like this:

<s:List>
<fx:String>item 0</fx:String>
<fx:String>item 1</fx:String>
…
</s:List>

Then virtualization would be on. You could turn it off by setting the useVirtualLayout property on the List to false. This value then gets pushed down to the List’s layout:

<s:List useVirtualLayout=”false”>
…
</s:List>

But if you were to define a new layout on the List then virtualization will not be on by default unless you specify useVirtualLayout=”true” on the List (or the layout):

<s:List useVirtualLayout=”true”>
<s:layout>
<s:HorizontalLayout />
</s:layout>
…
</s:List>

]]> By: Clint Modien http://flexponential.com/2009/07/10/performance-implications-of-the-list-itemrenderer-vs-itemrendererfunction-properties/comment-page-1/#comment-10 Clint Modien Sun, 19 Jul 2009 18:52:16 +0000 http://flexponential.com/?p=88#comment-10 The spark List component in Flex 4 has virtualization enabled by default. Is there a but in the docs? According to the gumbo beta docs virtualization is false by default... http://livedocs.adobe.com/flex/gumbo/langref/spark/layouts/supportClasses/LayoutBase.html#useVirtualLayout The spark List component in Flex 4 has virtualization enabled by default.

Is there a but in the docs?

According to the gumbo beta docs virtualization is false by default… http://livedocs.adobe.com/flex/gumbo/langref/spark/layouts/supportClasses/LayoutBase.html#useVirtualLayout

]]>