Unfortunately I'm also stuck with huge data grids in my current project,
performance is the number one issue, and having spent so much time on it, it
is hard to say it's "as good as it gets".
I have to use complex editable custom item renderers.
- I started out using the Spark grid
- Then transformed all the mxml to as for my item renderers, an obvious
choice, but it greatly reduces flexibility and development speed.
- Since I use Spark, and thus the TLF, I altered my code so that
RichEditableText would only render when the user focuses on an item
renderer, by default it's using a plain Label.
- Still too slow, so I went further creating a very simple grid component
myself.
- Then I started swapping the read only Label view from above, with the good
old Flash TextField.
And that's where I'm at now :)
The amount of resources needed to just generate even a simple ItemRenderer
is enormous!
I'd love a good grid component like many others do, hopefully we'll get the
core Flex code improved somehow.
-----Original Message-----
From: Roland Zwaga
Sent: Tuesday, January 17, 2012 5:48 PM
To: flex-dev@incubator.apache.org ; a...@kinesissoftware.com
Subject: Re: DataGrid perfomance
On 17 January 2012 17:20, Alex Bradley <a...@kinesissoftware.com> wrote:
On 17/01/2012 10:02, Roland Zwaga wrote:
> From what I heard the spark datagrid was a big improvement compared to
the
mx one,
perhaps this can be used to further optimize the performance.
There is a considerable amount of work just to get a full set of necessary
features into the Spark DataGrid - and that's without its current
performance issues. Whether these performance issues affect you as
developer really depends on the domain you're working in - but it's a
problem for large or dynamic data sources which may exclude it from many
Enterprise applications.
Ok, I haven't looked into the spark datagrid at all, I was just referencing
what I heard about it. But apparently, according to your findings, the
spark grid isn't fully up to the task either.
That's good to know, so thanks for the insight :)
A DataGrid component based on composition should automatically provide
full List, Tree, Color Picker, Date Chooser functionality so it's
certainly
a contender for starting component!
Despite compositional overhead, KineticGrid performs around 4-10 times
quicker than Spark grid in a dynamic scenario - if there's interest I can
see about finding time to document the architecture.
It sounds really interesting, sounds like a perfect contender for the
whiteboard. The grid is such a versatile component that will be used by
many developers that I'm sure there will be lots and lots of opinions about
it here on the list :)
But I think everyone will agree that indeed the grid needs to be
compositionally sound and offer a user-friendly plug-and-play kind of
extension mechanism. I believe a lot of people here would love to take a
look at your code, and who knows, it might become the basis for the Apache
Flex datagrid :)
cheers!
Roland
