- 22 Oct, 2015 1 commit
-
-
Hixie authored
-
- 12 Oct, 2015 1 commit
-
-
Adam Barth authored
These examples haven't been ported to fn3 yet. Before this patch, they caused a lot of noise in the analyzer output.
-
- 10 Oct, 2015 3 commits
-
-
Adam Barth authored
-
Adam Barth authored
-
Adam Barth authored
-
- 09 Oct, 2015 1 commit
-
-
Adam Barth authored
These are now part of material.dart.
-
- 03 Oct, 2015 1 commit
-
-
Adam Barth authored
This patch prepares us to switch to using integers when handing off the animation time from the engine to the framework.
-
- 26 Sep, 2015 1 commit
-
-
Adam Barth authored
-
- 11 Sep, 2015 1 commit
-
-
Adam Barth authored
-
- 08 Sep, 2015 1 commit
-
-
Adam Barth authored
Move the animation libraries into src/animation and change importers to use package:sky/animation.dart. Also, move scheduler.dart into the animation library so that the animation library can be self-contained.
-
- 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.
-
- 19 Aug, 2015 2 commits
-
-
Adam Barth authored
Similar to widgets.dart, rendering.dart exports the entire rendering layer. Also, update the examples to use rendering.dart and widgets.dart. Also clean up some exports so that the examples have more sensible imports.
-
Adam Barth authored
Sadly, box.dart has grown much longer than 1000 lines. This patch splits it up into several files based on the class hierarchy. Fortunately, many of these classes are loosely coupled to each other.
-
- 08 Aug, 2015 1 commit
-
-
Ian Fischer authored
-
- 04 Aug, 2015 1 commit
-
-
Adam Barth authored
It was confusing to have both widget.dart and widgets.dart
-
- 28 Jul, 2015 2 commits
-
-
Chinmay Garde authored
-
Chinmay Garde authored
-
- 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.
-
- 16 Jul, 2015 1 commit
-
-
Collin Jackson authored
-