I am curious about some "construction" decisions. Is there reasoning behind making QxListView from "div" components rather than "table"? My main curiosity is we are evaluating QooxDoo for some major internal applications, and want to make sure we understand as much as possible before making a decision.
One reason I ask this is we have had to deal with large tables and sorting here, and have had to do some interesting stuff to make them fast - we have at least one app with a requirement for tables containing 5000 rows with sorting capability - with IE support a must. For QooxDoo, if you load QxListView with 5k rows in the demo, it dies.. it has actually crashed my IE, and when it dosnt, it just falls asleep.. even with only a few k rows, sorting is unacceptably slow...
Thanks
Russell
- [qooxdoo-devel] QxListView question J. Russell Smyth
- Re: [qooxdoo-devel] QxListView question Sebastian Werner
- Re: [qooxdoo-devel] QxListView question J. Russell Smyth
- Re: [qooxdoo-devel] QxListView question Sebastian Werner
- Re: [qooxdoo-devel] QxListView questio... Dietrich Streifert
- Re: [qooxdoo-devel] QxListView qu... J. Russell Smyth
- Re: [qooxdoo-devel] QxListVie... Kent Olsson
- Re: [qooxdoo-devel] QxLis... Sebastian Werner
- Re: [qooxdoo-devel] QxLis... Sebastian Werner
- Re: [qooxdoo-devel] QxLis... Kent Olsson
- Re: [qooxdoo-devel] QxLis... Kent Olsson
