1. 12 Sep, 2018 1 commit
  2. 20 Jun, 2018 1 commit
  3. 19 Jun, 2018 1 commit
  4. 14 Mar, 2018 1 commit
  5. 05 Sep, 2017 1 commit
  6. 21 Apr, 2017 1 commit
  7. 13 Mar, 2017 1 commit
  8. 04 Mar, 2017 1 commit
  9. 17 Feb, 2017 1 commit
    • Adam Barth's avatar
      Two becomes one (#8253) · e0b12ca1
      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.
      e0b12ca1
  10. 09 Feb, 2017 1 commit
  11. 07 Feb, 2017 2 commits
    • Adam Barth's avatar
      Add ScrollController.initialScrollOffset (#7916) · 06f879b5
      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.
      06f879b5
    • Adam Barth's avatar
      Add ScrollController (#7910) · 7f2dc470
      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.
      7f2dc470
  12. 03 Feb, 2017 1 commit
    • Adam Barth's avatar
      Reparameterize Scrollable2 (#7853) · 072cce88
      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.
      072cce88
  13. 02 Feb, 2017 1 commit
  14. 27 Jan, 2017 1 commit
  15. 21 Jan, 2017 1 commit