This document outlines changes since 0.3.0. For older changelogs, see the dgrid wiki.
- Column plugins can now define the following functions on column definitions,
providing more opportune timing for initialization and tear-down:
init
, which will be executed at the time the grid's column configuration is (re-)applieddestroy
, which will be executed when the grid is destroyed, as well as before a new column configuration is applied
- The
tree
plugin now supports the following column definition properties:shouldExpand(row, level, previouslyExpanded)
, a function providing for conditional automatic expansion of parent rows (#141)indentWidth
, an integer specifying the size (in pixels) of each level's indent (note that the default is now9
, though it was previously19
)renderExpando()
, a function which can replace the default logic for rendering the expando node (the arrow next to the content of each cell)
- The
editor
plugin now augments the grid instance with anedit(cell)
method which can be used to programmatically activate the editor in a given cell. - A
util/mouse
module has been added, which exposes simulated events for the mouse entering and leaving grid rows and cells. (#165) - A
package.js
has been added in order to streamline the build process.package.json
has been updated to reflect the presence ofpackage.js
and reference the latest versions of xstyle and put-selector, each of which now have apackage.js
of their own.
- Mouse events for expanding/collapsing rows in tree grids should be a bit more reliable. (#112)
- Rows expanded in a tree grid which has been started up but is currently hidden will now be rendered properly when re-shown. (#140)
- The
tree
andeditor
plugins can now both be used on the same column, by wrappingeditor
withtree
. (#144) sortable
now defaults tofalse
for columns wherefield
is"_item"
or entirely unspecified (in which case there's nothing to sort by anyway). (#149)- The
Pagination
extension now behaves appropriately with empty result sets. (#173) - The
ColumnHider
extension now iterates oversubRows
rather thancolumns
, making it a bit more reliable in general. (#164) - A couple of issues with the
DijitRegistry
extension were identified and fixed. (#146, thanks jdohert)