Hi,
We enable setAutoFitFieldWidths on our grids, however this comes with a performance penaly (see quote below).
Some questions :
* would performance benefit from using this setting together with a fixed (min) width for some fields (or is width for all fields calculated first and only after that overridden with the fixed width)?
* would performance benefit from not setting AutoFitFieldWidths (and only use fixed widths)?
* what should we use for setting the width : minFieldWidth or width of the field?
* can we use setAutoFitClipFields and setAutoFitExpandField + autoFitFieldsFillViewport together with fixed width fields?
thanks,
We enable setAutoFitFieldWidths on our grids, however this comes with a performance penaly (see quote below).
Some questions :
* would performance benefit from using this setting together with a fixed (min) width for some fields (or is width for all fields calculated first and only after that overridden with the fixed width)?
* would performance benefit from not setting AutoFitFieldWidths (and only use fixed widths)?
* what should we use for setting the width : minFieldWidth or width of the field?
* can we use setAutoFitClipFields and setAutoFitExpandField + autoFitFieldsFillViewport together with fixed width fields?
Using this feature has a performance penalty roughly comparable to always rendering one additional field per field where autofitting is enabled. Specifically, enabling it for all fields would be comparable to both doubling the number of fields and disabling horizontal incremental rendering. In a grid where only half the fields are normally visible and hence only half are normally rendered, this would be roughly 4 times slower overall.This performance penalty is a result of ListGrid.getDefaultFieldWidth having to render out the data set offscreen and measure the rendered content - it does not apply for cases where this method can return a simple fixed values (as with icon fields).
thanks,
Comment