DHTMLX
Start Building Professional
Start Building Professional
Web Apps Today
| Categories | Question details Back To List | ||
Render with DIV's instead of TABLE's ? 2 Questions: 1) Is there work under way to make these grids use more CSS and DIV's rather than TABLE's? Browser rendering of large record sets, even with smart rendering and distributed parsing turned on, is slow. 2) If #1 is far away, or out of the question, can we easily manipulate the attributes that the table produces. e.g.: remove the valign="", align="left, title="xyz", etc? Thanks! Answer posted by Support on Feb 20, 2009 08:11 >>1) Is there work under way to make these grids use more CSS and DIV's rather than TABLE's? Nope. Usage of DIV based approach has its own problems. While it renders faster, such operation as column resize become performance killers - because hundreds of elements need to be resized in same time. We have few test projects and TABLE based structure works faster in most scenarios. In case of smartRendering enabled - grid renders only visible rows, and if you have reasonable amount of columns - it will work pretty good even for huge dataset. (By the way, tree component in process of migration to div based solution, which will give at least 2x boost in loading time ) >>can we easily manipulate the attributes that the table produces Do you mean add some customization or discard current logic? The grid provides onRowCreated event, which can be used to customize attributes of newly created row in any necessary way ( event handler receives row ID and row object ) To disable existing attributes you can modify _postRowProcessing method of grid. Actually attributes doesn't affect performance, not significantly. The two main performance criteria - count of rows, rendered at once, and count of columns. There was some experiments for improving speed of h-oriented grid ( column counts > 50 ), if necessary we can provide extension which can decrease loading time of such grids ( will not have effect on v-oriented grids ). Answer posted on Feb 23, 2009 11:02 Actually attributes doesn't affect performance, not significantly. The
two main performance criteria - count of rows, rendered at once, and
count of columns. There was some experiments for improving speed of
h-oriented grid ( column counts > 50 ), if necessary we can provide
extension which can decrease loading time of such grids ( will not have
effect on v-oriented grids ). ->Can you please provide this example. I have a h-oriented grid which have 20 rows an 100 columns. Thanx a lot Answer posted by Support on Feb 24, 2009 03:18 >>Can you please provide this example. I have a h-oriented grid which have 20 rows an 100 columns. Please contact us directly at support@dhtmlx.com and provide your ref. number |
