1. 20 Mar, 2018 1 commit
  2. 02 Mar, 2018 1 commit
    • Chris Bracken's avatar
      Eliminate RenderView orientation, timeForRotation (#15044) · 73a1a74b
      Chris Bracken authored
      Orientation, and by extension time for rotation between orientations,
      was aspirational and never used.
      
      While this is technically a breaking change, this code never actually
      did anything. If you were setting either orientation or timeForRotation,
      simply delete those parameters and the code will continue to behave
      identically to how it had been.
      73a1a74b
  3. 21 Sep, 2017 1 commit
  4. 14 Sep, 2017 1 commit
  5. 23 Aug, 2017 1 commit
  6. 03 Aug, 2017 1 commit
  7. 25 Jul, 2017 1 commit
  8. 16 May, 2017 1 commit
  9. 19 Apr, 2017 2 commits
  10. 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
  11. 19 Mar, 2017 1 commit
  12. 04 Mar, 2017 1 commit
  13. 23 Feb, 2017 1 commit
  14. 13 Feb, 2017 1 commit
  15. 16 Nov, 2016 1 commit
  16. 15 Sep, 2016 1 commit
  17. 30 May, 2016 1 commit
  18. 27 May, 2016 1 commit
  19. 20 May, 2016 1 commit
  20. 16 May, 2016 1 commit
    • Ian Hickson's avatar
      Make it possible to run tests live on a device (#3936) · 32527017
      Ian Hickson authored
      This makes it possible to substitute 'flutter run' for 'flutter test'
      and actually watch a test run on a device.
      
      For any test that depends on flutter_test:
      
      1. Remove any import of 'package:test/test.dart'.
      
      2. Replace `testWidgets('...', (WidgetTester tester) {`
            with `testWidgets('...', (WidgetTester tester) async {`
      
      3. Add an "await" in front of calls to any of the following:
          * tap()
          * tapAt()
          * fling()
          * flingFrom()
          * scroll()
          * scrollAt()
          * pump()
          * pumpWidget()
      
      4. Replace any calls to `tester.flushMicrotasks()` with calls to
         `await tester.idle()`.
      
      There's a guarding API that you can use, if you have particularly
      complicated tests, to get better error messages. Search for
      TestAsyncUtils.
      32527017
  21. 12 May, 2016 1 commit
  22. 22 Apr, 2016 2 commits
  23. 24 Mar, 2016 1 commit
  24. 14 Mar, 2016 1 commit
  25. 08 Mar, 2016 1 commit
  26. 14 Feb, 2016 1 commit
  27. 12 Feb, 2016 1 commit
  28. 11 Feb, 2016 1 commit
    • Ian Hickson's avatar
      Clean up imports and exports. · a94999ba
      Ian Hickson authored
      Each layer is supposed to reexport the parts of the previous layer
      that are part of its API.
      
      - In painting.dart, export from dart:ui all the Canvas-related APIs
        that make sense to be used at higher levels, e.g. PaintingStyle.
      
      - Delete painting/shadows.dart. It was dead code.
      
      - In rendering/object.dart, export all of painting.dart.
      
      - In widgets/basic.dart, export all of painting.dart and
        animation.dart. Some classes in animation/ are renamed to make this
        less disruptive and confusing to the namespace.
      
      - Split out Stocks back into an import model rather than a part model,
        so that it's easier to manage its dependencies on a per-file basis.
      
      - Move Ticker to scheduler library.
      
      - Remove as many redundant imports as possible now.
      
      - Some minor nit picking cleanup in various files.
      a94999ba
  29. 05 Feb, 2016 1 commit
    • Hixie's avatar
      Improve exceptions and asserts for rendering lib. · 1a0484cc
      Hixie authored
      * Use actual exceptions rather than assertions containing code
        containing strings when trying to give messages to authors.
      * Introduce RenderingError which is an AssertionError that takes a
        string argument, to support the above.
      * Provide a BoxDimensions.hasBoundedWidth/hasBoundedHeight API.
      * Document BoxDimensions.isNormalized.
      * Provide more useful information when we assert isNormalized and find
        that it is false.
      * When finding the size is infinite, crawl the tree to figure out which
        render box is likely responsible for the infinite constraints.
      * Provide more information when size doesn't match the constraints.
      * Provide more information when intrinsic dimension methods violate the
        constraints.
      * Only spam a huge amount of information for the first exception from
        the rendering library. I've noticed a lot of people looking at the
        last exception printed rather than the first and that's very
        misleading -- after the rendering library hits an exception, all bets
        are off regarding what'll happen in the future. All kinds of asserts
        might fire.
      * Improve docs around the debug methods and flags for the above.
      * Make Block default to have no children. Previously, giving no children
        crashed with a confusing message about a null deref in an assert.
      1a0484cc
  30. 27 Jan, 2016 1 commit
  31. 16 Jan, 2016 1 commit
  32. 11 Jan, 2016 1 commit
    • Adam Barth's avatar
      Rename RenderObject.hasLayer to isRepaintBoundary · 0b775984
      Adam Barth authored
      Also, introduce alwaysNeedsCompositing to force the "needs compositing"
      bit to true without necessarily introducing a ContainerLayer into the
      layer tree. A future patch will make use of alwaysNeedsCompositing to
      optimize opacity layers.
      0b775984
  33. 16 Dec, 2015 1 commit
  34. 14 Dec, 2015 1 commit
  35. 02 Dec, 2015 1 commit
  36. 26 Nov, 2015 1 commit
  37. 20 Nov, 2015 1 commit
  38. 19 Nov, 2015 1 commit