1. 02 Aug, 2018 1 commit
  2. 27 Jul, 2018 1 commit
  3. 23 Jul, 2018 1 commit
  4. 16 Jul, 2018 2 commits
  5. 12 Mar, 2018 1 commit
  6. 11 Jan, 2018 1 commit
  7. 01 Nov, 2017 1 commit
  8. 05 Sep, 2017 1 commit
  9. 31 Aug, 2017 1 commit
  10. 27 Apr, 2017 1 commit
  11. 12 Apr, 2017 1 commit
    • Ian Hickson's avatar
      Move Point to Offset (#9277) · bf017b79
      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
      bf017b79
  12. 07 Apr, 2017 1 commit
  13. 04 Apr, 2017 1 commit
  14. 13 Mar, 2017 1 commit
  15. 04 Mar, 2017 1 commit
  16. 22 Feb, 2017 1 commit
  17. 18 Feb, 2017 1 commit
  18. 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
  19. 09 Feb, 2017 3 commits
  20. 07 Feb, 2017 1 commit
  21. 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
  22. 02 Feb, 2017 1 commit
  23. 27 Jan, 2017 1 commit
  24. 21 Jan, 2017 1 commit