Hi Guys, I've noticed that the performance of tables seems to degrade almost exponentially with the number of columns in the table.
I realise there is a bug relating to this issue already (http://bugzilla.qooxdoo.org/show_bug.cgi?id=4237) but I think the problem is something other than what's described in that bug report. What makes me think there is another issue at play is, when you create a table with 10 rows of 16 columns the table generates almost instantly. But if you create a table with one row, and 160 columns the table takes so long to generate that the browser issues a warning about a long running script. I don't think the issue is that only the rows are virtualised, because in both the aforementioned cases I had the browser window maximized and all the cells were visible, meaning in each case there was a total of 160 cells created. I've created a playground example to illustrate the point. Try different combinations of rows & columns and you can see the table doesn't handle large numbers of columns at all well. http://tinyurl.com/3hfx8sg Thanks for the great framework, any advice is sincerely appreciated. Nick Tindall -- View this message in context: http://qooxdoo.678.n2.nabble.com/Table-perfomance-with-many-columns-tp6883678p6883678.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
