> One thing the OP might want to try in addition to lightening the repeated > components is to use a repeater and start out by just loading 5 (or however > many are visible without scrolling), and then add to the collection after > those are drawn.
Amy, thank you for your suggestion. I have one question which is related to UI design based on your suggestion. Let's say I have 50 posts to display. I only display first 5 and add rest of the posts after the first 5 are drawn. By doing this, if a user want to see older post, let's assume post number 46~50, the user should scroll down by using the vertical scroll generated by repeater. Doesn't the user still have to wait for a while before the vertical scroll bar is seen since repeater will need to render rest of posts before the vertical scroll bar can be generated correctly? Currently, I am implementing paging as a temporarily solution(5 posts per page), but I really prefer to squeeze in as many posts as possible initially. --- In [email protected], "Amy" <amyblankens...@...> wrote: > > --- In [email protected], Alex Harui <aharui@> wrote: > > > > Use the profiler to see where the time is being spent. If your attempt to > > use List had poor scrolling it implies that your post renderer is > > inefficient. > > No, List scrolling in Flex 3 (Halo) isn't really scrolling, it just "jumps" > to the next item, so no matter how you optimize your renderers, this is going > to happen. I believe this is fixed in Gumbo, so a move to Gumbo might help. > > One thing the OP might want to try in addition to lightening the repeated > components is to use a repeater and start out by just loading 5 (or however > many are visible without scrolling), and then add to the collection after > those are drawn. > > -Amy >
