- 11 Jan, 2016 1 commit
-
-
Adam Barth authored
Previously we used a positional argument for widgets that had multiple children. Now we use a named argument that defaults to an empty list. Fixes #241
-
- 10 Dec, 2015 1 commit
-
-
Ian Hickson authored
-
- 02 Dec, 2015 1 commit
-
-
Ian Hickson authored
Heroes with the same tag have to have keys that are unique across the entire subtree. Since we can now show both stock lists, this means we have to include the tab in the heroes' keys. Fixes #668.
-
- 11 Nov, 2015 1 commit
-
-
Hans Muller authored
-
- 21 Oct, 2015 2 commits
- 12 Oct, 2015 1 commit
-
-
Hixie authored
Add type annotations in many places. Fix some identifiers to have more lint-satisfying names. Make all operator==s consistent in style. Reorder some functions for consistency. Make ParentData no longer dynamic, and fix all the code around that.
-
- 03 Oct, 2015 2 commits
-
-
Adam Barth authored
After this patch, InkWell is driven by gesture recognizers, which lets us cleanly cancel splashes when the user actually scrolls. I've also refactored all the clients of InkWell to use InkWell to detect gestures instead of wrapping InkWell in a GestureDetector. Fixes #1271
-
Adam Barth authored
* Rename GestureTapListener (and friends) To GestureTapCallback to match the other gesture callbacks. * Replace "ensureFoo" pattern with ??= operator.
-
- 02 Oct, 2015 1 commit
-
-
Hixie authored
Identify specific parts of a Stock row with a Global Key that can be regenerated later, and pass that key back to event handlers so they can use them to do the transition.
-
- 01 Oct, 2015 1 commit
-
-
Hixie authored
- Rename EdgeDims constructor to EdgeDims.TRBL(). - Add operator== to Size and Offset so that you can compare Size to DebugSize in checked mode. - Add Size.lerp(). - Add various operators to EdgeDims. (*, /, ~/, %) - Add EdgeDims.lerp(). - Update style guide. I went there to fix an EdgeDims constructor example, and stayed because some recent things came up and I wanted to add them before I forgot.
-
- 30 Sep, 2015 2 commits
-
-
Hixie authored
Make it possible for named routes to be generated on the fly. To demonstrate this, you can now long-press a stock to open it. Next steps: - transitions between (named) states that follow full material logic, e.g. in the case of the stock row to stock page transition, expanding the row into a raised sheet of material and expanding it to fit the screen, leaving the toolbar in place but cross-fading the old contents to the new contents. - more information in the stock view. While I was here I also made Material have an opinion about default text style, so if you forget to set one, it just uses body1. Also, fixed bugs introduced recently that made RouteState and MenuRoute not work properly.
-
Hixie authored
Not having them clickable was making it hard to notice InkSplash bugs. Also, this paves the way to having a stock page.
-
- 26 Sep, 2015 1 commit
-
-
Hixie authored
-
- 26 Aug, 2015 1 commit
-
-
Hixie authored
This still leaves Flex and FlexDirection available. At some point once people have transitioned to Row/Column we should rename Flex to _Flex and stop reexporting FlexDirection from basic.dart.
-
- 11 Aug, 2015 1 commit
-
-
Eric Seidel authored
And also Material Design of course. @abarth
-
- 08 Aug, 2015 1 commit
-
-
Ian Fischer authored
-
- 28 Jul, 2015 2 commits
-
-
Chinmay Garde authored
-
Chinmay Garde authored
-
- 24 Jul, 2015 1 commit
-
-
Jim Simon authored
Converted demo launcher example to library Converted fitness example to library Converted hello world example to library Converted mine digger example to library Converted stocks example to library
-
- 22 Jul, 2015 1 commit
-
-
Hixie authored
This fixes some theoretical bugs whereby we were using hashCode to try to get unique keys for objects, but really we wanted object identity. It also lays the groundwork for a new GlobalKey concept. I tried to keep the impact on the code minimal, which is why the "Key" constructor is actually a factory that returns a StringKey. The code has this class hierarchy: ``` KeyBase | Key--------------+---------------+ | | | StringKey ObjectKey UniqueKey ``` ...where the constructors are Key and Key.stringify (StringKey), Key.fromObjectIdentity (ObjectKey), and Key.unique (UniqueKey). We could instead of factory methods use regular constructors with the following hierarchy: ``` KeyBase | LocalKey---------+---------------+ | | | Key ObjectIdentityKey UniqueKey ``` ...with constructors Key, Key.stringify, ObjectIdentityKey, and UniqueKey, but I felt that that was maybe a more confusing hierarchy. I don't have a strong opinion on this.
-
- 18 Jul, 2015 1 commit
-
-
Collin Jackson authored
-
- 17 Jul, 2015 2 commits
-
-
Collin Jackson authored
-
Collin Jackson authored
-
- 16 Jul, 2015 1 commit
-
-
Collin Jackson authored
-