-
about 6 min
The column knows it holds metres
In most grids a unit is a formatter, and a formatter is a lie that shows the moment someone sorts. Lattice Grid makes a quantity a data type, so the column stays a number.
-
about 3 min
When the grid became the interface
Grids are sold to developers, so they are built for developers. Why Lattice Grid ships redaction, annotation and presentation tools to every user as standard.
-
about 3 min
Two ways to show a row's detail
A row that expands into a nested grid, or a pane beside the list where nothing moves. They solve different problems, and one config field switches between them.
-
about 3 min
Hierarchies that survive real data
Every tree demo uses data that is already a tree. Yours will not be. Here is what happens to the orphan, the cycle and the missing level.
-
about 4 min
Width is the harder problem
Everybody demos a long grid. The one that hurts is the wide one, where the row you are reading loses its name somewhere around column nineteen.
-
about 4 min
A million rows, timed on your machine
Every grid vendor has a benchmark number from a laptop you have never seen. The grid in this post times itself in your browser instead.
-
about 4 min
Types are not labels
In most grids a column type picks an alignment. Here it decides storage, comparison, parsing, formatting and the editor, from one word.
-
about 4 min
A column definition should read like a description
Forty flat properties per column is a config file nobody reads twice. Grouping them by concern, and naming the repeats, makes a column list readable.
-
about 3 min
Get going in two minutes
One script, one stylesheet, a div with a height and a list of columns. Sorting, filtering, resizing and reordering are already there.