Agreed. The renderer should not cache per-instance, there needs to be a central cache. I'm pretty sure SuperImage does that. But getting data on-demand will usually be the better way to go.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Wednesday, June 25, 2008 9:45 PM To: [email protected] Subject: Re: [flexcoders] Re: Problems with list using custom itemRenderer and variableRowHeight You make a good point, but I'd still use the model as the proxy + cache rather than the renderer. -Josh On Thu, Jun 26, 2008 at 2:38 PM, Alex Harui <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: I'm not sure I agree with that. Imagine pulling in 100 rows and only showing 7. You don't want your server fetch to pull 100 images if the user never scrolls to see the other 93. -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
