- 17 May, 2016 2 commits
-
-
Hans Muller authored
* ScrollableBuilder tweaks
-
Hans Muller authored
* Add a Scrollable builder, refactor ScrollableList, et al * Add space between the dialog demo buttons * removed vestigial code
-
- 29 Apr, 2016 1 commit
-
-
Ian Hickson authored
Note that the /// part of the doc was published, only the // line was omitted. This means that we can safely put // comments between /// docs and the member they are documenting.
-
- 12 Apr, 2016 3 commits
-
-
Adam Barth authored
-
Adam Barth authored
Also fill in some related dartdocs.
-
Hans Muller authored
* ClampOverscrolls Inherited Widget
-
- 09 Apr, 2016 1 commit
-
-
Hans Muller authored
* Remove ScrollableListPainter
-
- 06 Apr, 2016 2 commits
-
-
Hans Muller authored
Overscroll indicator for MaterialList
-
Adam Barth authored
This patch adds dartdoc to LazyBlock. Also, this patch fixes the scrolling physics of LazyBlock. Previously, we updated a running simulation only when the change in scroll behavior changed the current scroll offset. Now we update running simulations every time the behavior changes because the simulation might depend on quantities other than the current scroll offset.
-
- 05 Apr, 2016 1 commit
-
-
Adam Barth authored
LazyBlock is intended as a replacement for MixedViewport. Rather than maintaining a table of all the observed child sizes (like MixedViewport), LazyBlock works by dead reckoning the location of the children based on the existing viewport. This approach makes it easier to resize children because LazyBlock doesn't cache any additional information that would need to be invalidated. This patch contains a first draft of LazyBlock that works in a simple usage scenario. Subsequent patches will replace ScrollableMixedWidgetList with LazyBlock and port the existing ScrollableMixedWidgetList tests over to LazyBlock. Related to #3075
-
- 23 Mar, 2016 1 commit
-
-
Adam Barth authored
Previously, when the content extent changed during a scroll interaction, we'd stop the current scroll interaction and reset the scroll offset. Now we try to continue the scroll interaction (e.g., drag, fling, or overscroll) even through the underlying scroll behavior has changed. For physics-based scroll interactions, we keep the current position and velocity and recompute the operative forces. For drag interactions, we keep the current position and continue to let the user drag the scroll offset. After this patch, we still disrupt non-physical scroll animations that are operating outside the new scroll bounds because it's not clear how we can sensibly modify them to work with the new scroll bounds.
-
- 14 Mar, 2016 2 commits
-
-
Hixie authored
-
Hans Muller authored
-
- 12 Mar, 2016 7 commits
-
-
Adam Barth authored
Fixes #1382
-
Adam Barth authored
Fixes #774
-
Adam Barth authored
-
Adam Barth authored
Fixes #581
-
Hixie authored
And fix the zillion issues that uncovered.
-
Ian Hickson authored
This reverts commit f41b3411, reversing changes made to e33d8d96. This was a bad check-in due to my mangling uploading a new version of the branch from a different machine. This reverts https://github.com/flutter/flutter/pull/2639 and will be replaced by https://github.com/flutter/flutter/pull/2640
-
Hixie authored
And fix the zillion issues that uncovered.
-
- 11 Mar, 2016 1 commit
-
-
Adam Barth authored
We'll need this for RTL support because the RTL state will live in the widget tree. Also, remove the `oldWidget` argument to updateRenderObject because there aren't any clients for it.
-
- 04 Mar, 2016 1 commit
-
-
Adam Barth authored
-
- 12 Feb, 2016 2 commits
-
-
Adam Barth authored
Previously we had totally wrong behavior. Now we have more correct behavior and testing. Fixes #1808
-
Hixie authored
Remove the SizeObserver you need to use snap alignment in lists by having the lists provide the size themselves in the callback. Also, remove snapAlignmentOffset since we couldn't figure out how to explain it and it's not really needed.
-
- 10 Feb, 2016 2 commits
-
-
Adam Barth authored
We need to subtract the padding instead of adding it.
-
Adam Barth authored
-
- 06 Feb, 2016 1 commit
-
-
Adam Barth authored
The virtual viewport machinery now handles all of these use cases. Previous clients of ScrollableWidgetList can use ScrollableLazyList instead.
-
- 03 Feb, 2016 1 commit
-
-
Hans Muller authored
Add support for the appbar behavior described in the "Flexible space with image" section of https://www.google.com/design/spec/patterns/scrolling-techniques.html#scrolling-techniques-scrolling.
-
- 21 Jan, 2016 1 commit
-
-
Adam Barth authored
Previously this code was in the animation layer, which didn't make much sense because scrolling is a widget concern.
-
- 14 Jan, 2016 1 commit
-
-
Adam Barth authored
We were recomputing which widgets to show only when we were on the other side of the repaint boundaries. That doesn't work well for pageable lists because we come to rest exactly on a repaint boundary, which means we don't cull the other page. After this patch, we recompute the set of widgets using an edge-trigger when we hit the boundary. That's better than using a level-trigger so that we don't continuously recompute the set of widget as we sit at the boundary.
-
- 11 Jan, 2016 2 commits
-
-
Adam Barth authored
We use the ScrollDirection for more than just scrolling. Fixes #151
-
Adam Barth authored
Instead of taking a builder and a generic type, we can just take a List<Widget>.
-
- 06 Jan, 2016 4 commits
-
-
Adam Barth authored
This patch moves PageableList off HomogeneousViewport and onto RenderList and friends, making it match the new ScrollableList.
-
Adam Barth authored
ScrollableList2 is complete and subsumes all the use cases for the original ScrollableList.
-
Adam Barth authored
When paging a scrollable list, we were trying to read the render object's size at a time when we're not allowed to read it. Instead, encode the information into the repaint limit, which is more correct (and faster) anyway.
-
Adam Barth authored
This patch also changed ScrollableList2 to use an Iterable instead of an List for its children. This change lets clients map their underlying data lazily. If the clients actually have a concrete list, we skip the extra copy and grab the child list directly.
-
- 05 Jan, 2016 2 commits
-
-
Adam Barth authored
This patch implements the remaining missing features of ScrollableList2. It should now be nearly a drop-in replacement for ScrollableList. The next patch will switch callers over to the new machinery.
-
Adam Barth authored
ScrollableList2 uses the same pattern as ScrollableGrid, which requires the client to allocate widgets for every list item but doesn't inflate them unless they're actually needed for the view. It improves on the original ScrollableList by not requiring a rebuild of the whole visible portion of the list when scrolling. In fact, small scrolls can often be handled entirely by repainting.
-