- 27 Jun, 2017 1 commit
-
-
Jacob Richman authored
* Switch existings tests to use equalsIgnoringHashCodes and add more tests.
-
- 21 Apr, 2017 1 commit
-
-
Alexandre Ardhuin authored
* make @immutable const * fix build
-
- 12 Apr, 2017 1 commit
-
-
Ian Hickson authored
* Manually fix every use of Point.x and Point.y Some of these were moved to dx/dy, but not all. * Manually convert uses of the old gradient API * Remove old reference to Point. * Mechanical changes I applied the following at the root of the Flutter repository: git ls-files -z | xargs -0 sed -i 's/\bPoint[.]origin\b/Offset.zero/g' git ls-files -z | xargs -0 sed -i 's/\bPoint[.]lerp\b/Offset.lerp/g' git ls-files -z | xargs -0 sed -i 's/\bnew Point\b/new Offset/g' git ls-files -z | xargs -0 sed -i 's/\bconst Point\b/const Offset/g' git ls-files -z | xargs -0 sed -i 's/\bstatic Point /static Offset /g' git ls-files -z | xargs -0 sed -i 's/\bfinal Point /final Offset /g' git ls-files -z | xargs -0 sed -i 's/^\( *\)Point /\1Offset /g' git ls-files -z | xargs -0 sed -i 's/ui[.]Point\b/ui.Offset/g' git ls-files -z | xargs -0 sed -i 's/(Point\b/(Offset/g' git ls-files -z | xargs -0 sed -i 's/\([[{,]\) Point\b/\1 Offset/g' git ls-files -z | xargs -0 sed -i 's/@required Point\b/@required Offset/g' git ls-files -z | xargs -0 sed -i 's/<Point>/<Offset>/g' git ls-files -z | xargs -0 sed -i 's/[.]toOffset()//g' git ls-files -z | xargs -0 sed -i 's/[.]toPoint()//g' git ls-files -z | xargs -0 sed -i 's/\bshow Point, /show /g' git ls-files -z | xargs -0 sed -i 's/\bshow Point;/show Offset;/g' * Mechanical changes - dartdocs I applied the following at the root of the Flutter repository: git ls-files -z | xargs -0 sed -i 's/\ba \[Point\]/an [Offset]/g' git ls-files -z | xargs -0 sed -i 's/\[Point\]/[Offset]/g' * Further improvements and a test * Fix minor errors from rebasing... * Roll engine
-
- 07 Apr, 2017 1 commit
-
-
Ian Hickson authored
Aggressively apply the const lint.
-
- 13 Mar, 2017 1 commit
-
-
Ian Hickson authored
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 24 Feb, 2017 1 commit
-
-
Adam Barth authored
With slivers, the app bar is part of the scroll view. Naively, the overscroll appears at the beginning of the scroll view, but that's not the desired behavior. Instead, the app bar should remained pinned to the top of the scroll view and the overscroll should appear below the app bar, which is what this patch does. Fixes #8228
-
- 17 Feb, 2017 1 commit
-
-
Adam Barth authored
Rename all the "2" classes related to scrolling to remove the "2". Now that the old scrolling code is gone, we don't need to use the suffix.
-
- 09 Feb, 2017 2 commits
-
-
Alexandre Ardhuin authored
-
Ian Hickson authored
Move the back button and drawer opening logic into the app bar. Move the tap-status-bar-to-scroll-to-top logic to using ScrollControllers. Provide a PrimaryScrollController and a `primary` flag on scroll views. Make it possible to track when a route becomes or stops being poppable.
-
- 07 Feb, 2017 2 commits
-
-
Adam Barth authored
Also, move the creation of the ScrollPosition to ScrollController. Finally, remove TestScrollable in favor of CustomScrollView, which is the production version of this widget.
-
Adam Barth authored
If you pass a ScrollController to a Scrollable2, you can use the controller to read and write the scroll offset without having to find the Scrollable2State object.
-
- 06 Feb, 2017 1 commit
-
-
Ian Hickson authored
-
- 03 Feb, 2017 1 commit
-
-
Adam Barth authored
This patch makes a number of changes to how you can configure a Scrollable2: - The ScrollPhysics is now responsible for creating the ScrollPosition. You can override the ScrollPhysics by supplying a `physics` argument to `Scrollable`, and the new physics you supply will be applied to the default physics inherited from the ScrollBehavior. - This patch removes the ScrollPosition/AbsoluteScrollPosition split as all clients were operating in pixels anyway and the split made the code very difficult to follow. - ScrollPosition no longer depends directly on Scrollable2State. Instead, it depends on an abstract interface that Scrollable2State implements. This change has two benefits: a) It removes the circular dependency between ScrollPosition and Scrollable2State, which lets us split the code for these classes (and several other classes that got wrapped up in that cycle) into separate libraries for easier maintenance. b) ScrollPosition is no longer bound to Scrollable2, which means you could use the behavior machinery to drive other sorts of widgets. For example, we could use it to drive Scrollabe1 if we wanted.
-
- 02 Feb, 2017 1 commit
-
-
Ian Hickson authored
-
- 27 Jan, 2017 1 commit
-
-
Adam Barth authored
This structure makes it easier to customize the viewport used in a Scrollable. Now Scrollable2 doesn't commit to using slivers.
-
- 25 Jan, 2017 1 commit
-
-
Ian Hickson authored
-