Hi Lach, you should be able to test it very easily by creating 300 rows of your view. Normally the biggest problem is startup time. Creating and populating 300 views takes some time.
Cheers, Ralf. On 12/14/06, Lachlan Cotter <[EMAIL PROTECTED]> wrote:
The collection view classes in Flex such as List, TileList, DataGrid etc. have an optimisation so that the component only instantiates enough item renderers to display the items currently on screen. This is presumably a necessary optimisation to keep from consuming massive resources when rendering large collections. The Flex 2 Store example implements a custom collection view that does animation of renderers and state changes etc. and does live filtering of the collection as the user drags a slider. It's considerably cooler than the standard classes. I want to do something similar in my app. *The question* As far as I can tell, the Flex Store isn't optimised for renderer minimisation the way the standard collection classes are. I would like to know at what point this approach is likely to run into performance issues with collections approaching say two – three hundred items. Does anyone have any experience with this kind of thing? Cheers, Lach
-- Ralf Bokelberg <[EMAIL PROTECTED]> Flex & Flash Consultant based in Cologne/Germany
