Scott Hyndman
Scott Hyndman
Nice work!
Hi there, Stumbled across your library while I was trying to debug a pipeline problem I was having, and it was a _huge_ help. Just wanted to say thanks :)
The process is a little opaque at the moment during development.
They're very difficult to read right now. The important information should be front and center.
We currently support * Property listings in DevTools for many core object * Debug painting * Flags for debugPrinting layout passes * Overflow indication We should tell people about it
The README [has a description](https://github.com/madewithfelt/flutter_layout_grid/#accessibility-and-placement) of how to get a screenreader to announce grid items in a sensible order, independently of how they appear visually. This is roughly equivalent to...
Auto tracks are generated automatically when the placement algorithm places an item outside the range of the templated tracks. This could be useful in some cases.
Currently we report overflows considering all children as a group, but we have the ability to report which children are responsible.
The improvements to the layout algorithm mean that allowing a user to explicitly set the min and max size for a track should be possible (similarly to how CSS' [`minmax()`](https://developer.mozilla.org/en-US/docs/Web/CSS/minmax())...