Ban -

I don't think TextInput is nearly as lightweight as you might think. Do you really need them all to be editable at all times? Typically I use a lightweight itemrenderer derived from UIComponent etc. and use a separate itemEditor (TextInput, ComboBox, DateField), etc. when the user clicks on a particular data value (row/column).

hth
Scott

Scott Melby
Founder, Fast Lane Software LLC
http://www.fastlanesw.com



letterpigeon wrote:

Hi Scott,

Thanks for your post. But I'm on flex 2 now so the
AdvancedDataGridItemRenderer is not available to me. Also, in terms
of keeping the item renderer as light weight as possible, my item
renderer is just a TextInput and I change its background color by
calling this.styleName = "ErrorCell" where "ErrorCell" is defined in
my stylesheet. But even if I comment all this out, & have my item
renderer just to renderer the text, I'm still seeing a considerable
performance hit just by using custom item renderers on all the columns
of my datagrid. Is this a limitation in flex that we must trade off
performance for using custom renderers heavily?? Thanks.

Ban

--- In [email protected] <mailto:flexcoders%40yahoogroups.com>, Scott Melby <[EMAIL PROTECTED]> wrote:
>
> Check out this post <http://blog.fastlanesw.com/?p=25 <http://blog.fastlanesw.com/?p=25>> on my blog
where
> I discuss and demonstrate performance diffs using various item
renderers
> in Flex. Source code is available if you run the app and right click.
> Notice how the optimized renderer does not use layout containers
such as
> HBox, etc. Instead it extends the AdvancedDataGridItemRenderer class.
> In general you want to make your renderers as light weight as possible.
>
> hth
> Scott
>
> Scott Melby
> Founder, Fast Lane Software LLC
> http://www.fastlanesw.com <http://www.fastlanesw.com>
>
>
>
> letterpigeon wrote:
> >
> > Hi all,
> >
> > I'm seeing a huge performance degradation while using custom item
> > renderer with a datagrid. My datagrid is using a custom item renderer
> > for all its column. And even if my item renderer does nothing more
> > than :
> >
> > public override function data(value:object)
> > {
> > super.data = value;
> > }
> >
> > I'm still seeing a few more seconds delay compared to not using custom
> > item renderers for a data set of 50 rows or more.
> >
> > Just wondering if this is a known issue with flex due to heavy graphic
> > rendering? Any pointers on how to speed things up a little bit?
Thanks.
> >
> > Ban
> >
> >
>

Reply via email to