- 25 Jan, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 21 Dec, 2017 1 commit
-
-
Ian Hickson authored
This cleans up lerp, lerpFrom, lerpTo, and scale methods, and their documentation. Fixes https://github.com/flutter/flutter/issues/12377.
-
- 22 Nov, 2017 1 commit
-
-
Ian Hickson authored
This fixes the popup menu code to do a better job of expanding smoothly regardless of which side of the screen it's on. It still results in a bidirection growth when positioned at the bottom of the screen, so maybe we'll need to animate menus differently, but that's a problem for another patch. Also, improve some docs and provide RelativeRect.toSize which I needed at one point while building this patch (though it didn't survive all the way to the end).
-
- 09 Nov, 2017 1 commit
-
-
Greg Spencer authored
UnconstrainedBox will allow its child to size itself as if it had no constraints, and then attempt to fit around that object, until its own constraints are exceeded, in which case it will clip and display an overflow warning. I also factored out DebugOverflowIndicator, which will draw overflow indicators on containers which overflow but aren't expected to.
-
- 01 Nov, 2017 1 commit
-
-
Ian Hickson authored
Various improvements (in particular a new painting fuzzer) to the text manual test. Some additional documentation. A fix to Stack to remove an LTR bias: make unpositioned children apply "alignment". Some more debugging information on RichText and Text. A fix to the flutter tool to not crash when an RPC call throws an exception.
-
- 22 Oct, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 02 Oct, 2017 1 commit
-
-
Adam Barth authored
Unlike FractionalOffset, Alignment uses the center as the zero of the coordinate system, which makes the RTL math work out much cleaner. Also, make FractionalOffset into a subclass of Alignment so that clients can continue to use FractionalOffset.
-
- 24 Sep, 2017 1 commit
-
-
Ian Hickson authored
-
- 23 Sep, 2017 1 commit
-
-
Adam Barth authored
Also, fix asserts in TableBorder#paint to match documentation. Fixes #12009
-
- 08 Sep, 2017 1 commit
-
-
Adam Barth authored
Notice that the default alignment for Stack needs to know the directionality.
-
- 03 Aug, 2017 1 commit
-
-
Jacob Richman authored
Add Diagnosticable base class and documentation
-
- 25 Jul, 2017 1 commit
-
-
Jacob Richman authored
Refactor RenderObject.toStringDeep and Widget.toStringDeep code to use DiagnosticsNode.
-
- 11 Jul, 2017 1 commit
-
-
Michael Goderbauer authored
-
- 05 Jun, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 02 Jun, 2017 1 commit
-
-
Ian Hickson authored
This prevents some of our mixins from being subclassed. Also, move mixins to using 'extends' instead of 'implements' for future compatibility with Dart changes. Also, rename a class that had Mixin in the name but was not a mixin.
-
- 12 May, 2017 1 commit
-
-
Adam Barth authored
The default is topCenter, which is sensible, but someone might want to use a bottomCenter alignment, for example.
-
- 10 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 05 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 26 Apr, 2017 1 commit
-
-
Adam Barth authored
The enum is called StackFit, so the property name "fit" makes more sense.
-
- 25 Apr, 2017 1 commit
-
-
Ian Hickson authored
Also: * Add three explicit sizing modes to Stack for non-positioned children: loose, expand, and passthrough. (All three are used.) * Fix a bug whereby layers would try to paint in the same frame as they were removed from layout (but not detached). * Fix a bug whereby Offstage wasn't properly marking the parent dirty when changing its sizedByParent flag. * Explicitly make Overlay expand non-positioned children. * Explicitly have InputDecoration pass through the constraints from its Row to its Stack children.
-
- 19 Apr, 2017 1 commit
-
-
Adam Barth authored
Turns out we have many immutable classes. Fixes #6892
-
- 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
-
- 05 Apr, 2017 1 commit
-
-
Adam Barth authored
The Wrap widget is a layout that places children in a run in order along its main axis until it runs out of space. At that point, starts placing children in a new run that is adjacent in the cross axis. Fixes #8831
-
- 31 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
* add @required when there's an assert not null * address review comments
-
- 19 Mar, 2017 1 commit
-
-
Adam Barth authored
Fixes #4301
-
- 10 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
Covers lib/ in package:flutter.
-
- 14 Feb, 2017 1 commit
-
-
Ian Hickson authored
Since RelativeRect's whole purpose in life is to make work with Stack easier, it's silly that you can't directly use it with Positioned. Also, tests for RelativeRect. And fixes for the bugs that found...
-
- 01 Dec, 2016 1 commit
-
-
Alexandre Ardhuin authored
-
- 22 Nov, 2016 1 commit
-
-
Hans Muller authored
-
- 19 Nov, 2016 1 commit
-
-
Ian Hickson authored
-
- 29 Aug, 2016 1 commit
-
-
Ian Hickson authored
Fixes https://github.com/flutter/flutter/issues/5283 Other changes in this patch: Rename OffStage to Offstage. Fixes https://github.com/flutter/flutter/issues/5378 Add a lot of docs. Some minor punctuation and whitespace fixes.
-
- 11 Aug, 2016 1 commit
-
-
Dragoș Tiselice authored
Added a flag that instructs Stack how to deal with overflowing children: they can either be clipped or not.
-
- 08 Jun, 2016 1 commit
-
-
Ian Hickson authored
Also, make sure that the parent is notified when they change. Fixes #2298
-
- 02 Jun, 2016 1 commit
-
-
Adam Barth authored
All of the public APIs in rendering.dart now have dartdocs.
-
- 31 May, 2016 1 commit
-
-
Ian Hickson authored
-
- 27 May, 2016 1 commit
-
-
Adam Barth authored
There are still many more left before rendering.dart is complete.
-
- 12 May, 2016 1 commit
-
-
pq authored
It's safe to remove the unneeded `void`s from setters since the blocking issues in the `always_declare_return_types` lint have been fixed (https://github.com/dart-lang/linter/). We can also safely flip the bit on `avoid_return_types_on_setters`.
-
- 24 Apr, 2016 1 commit
-
-
Adam Barth authored
A flow layout is optimized for reposition children with transformation matrices. A flow layout can animate the position of its children very efficiently.
-
- 11 Apr, 2016 1 commit
-
-
Ian Hickson authored
I ran into a case where I was setting minHeight=∞ and then calling layout() with that constraint, which is all kinds of bad. To try to catch this earlier, this patch now provides a way to catch constraints that are requiring infinite values. We don't _always_ check this because there are valid uses for BoxConstraints.biggest, e.g. as an additionalConstraint.
-