- 25 Sep, 2015 1 commit
-
-
Hixie authored
Also: - Make Dismissable report when it starts squashing, since otherwise we don't invalidate the list early enough and it gets mad that it wasn't told one of its children had changed size. - Have Dismissable check that it gets removed after it's dismissed, to avoid having lots of redundant widgets around. - Start tracking the height of each child of a MixedViewport, so that we don't accumulate floating point errors when a child jiggles up and down. - Have _childOffsets reuse its storage space rather than newing up a new copy each time we reset the cache. - Avoid double-updating child sizes when handling mixed viewport invalidations.
-
- 24 Sep, 2015 2 commits
-
-
Hixie authored
ComponentState becomes State, for brevity. Instead of overriding its constructor, override initState(). This makes writing States much simpler.
-
Adam Barth authored
-
- 18 Sep, 2015 1 commit
-
-
Hixie authored
This fixes #1103.
-
- 16 Sep, 2015 2 commits
-
-
Adam Barth authored
This fixes an issue in the stocks app in horizontal mode where you could both scroll and drag the drawer at the same time.
-
Hixie authored
Move _activeCardDragEndPoint near build() so it's more obvious that it is part of the build state. Make a couple of functions use setState() since they modify variables that are used by build(). Add a more detailed comment to the empty setState() call, since those are dubious in general and need explaining when they occur, lest people start using them as magic incantations to Make Things Work.
-
- 11 Sep, 2015 1 commit
-
-
Hans Muller authored
Dismissable now only depends on GestureDetector. Added a unit test that verifies that issue #1068 has been fixed. It's commented out for now. Cleaned up VelocityTracker.cc et al a little.
-
- 10 Sep, 2015 1 commit
-
-
Adam Barth authored
That way the fling engages in the same direction as the scroll. For example, if you have a horizontal scroll nested inside a vertical scroll, the fling will take place in the same direction as the scroll.
-
- 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.
-
- 04 Sep, 2015 2 commits
-
-
Hans Muller authored
-
Hans Muller authored
``` enum DismissDirection { vertical, horizontal, left, right, up, down } ``` To only enable dismissing to the right create the `Dismissable` with `direction: DismissDirection.right`. By default direction is `DismissDirection.horizontal` (left or right). Updated the card_collection "Swipe Away" demo with a drawer that can be used to select one of the three X axis dismiss directions. Currently the MixedViewport class doesn't support horizontal scrolling, so the demo doesn't support the X axis dismiss directions.
-
- 03 Sep, 2015 1 commit
-
-
Hans Muller authored
Alternating scroll gestures would sometimes be ignored because _ScrollGestureRecognizer didn't always reset its _state when the pointer[s] went up. A Dismissable dismiss triggered by a drag and then a fling could cause the next attempt to drag-dimiss to fail. Fixed the definition of lerpColor().
-
- 02 Sep, 2015 1 commit
-
-
Adam Barth authored
Code outside of package:sky should import this code using package:sky/rendering.dart package:sky/widgets.dart Moving this code into the "src" directory is a convention that signifies that and it cleans up the generated dartdoc because the libraries in the src directory aren't included in the generated documentation. Instead, the classes are documented in the widgets.dart and rendering.dart libraries.
-
- 31 Aug, 2015 1 commit
-
-
Hans Muller authored
Convert Dismissable to use the ScrollStart, ScrollUpdate, and ScrollEnd gestures. Support for fling gestures is TBD. Included a basic unit test that checks that one item can be dismissed with a press-drag-release gesture. Fixed the scroll gesture recognizer: if the last pointer goes up and candidate recognizers still exist, then reject the gesture.
-
- 22 Aug, 2015 1 commit
-
-
Adam Barth authored
-
- 19 Aug, 2015 1 commit
-
-
Hans Muller authored
-
- 14 Aug, 2015 1 commit
-
-
Hans Muller authored
-
- 10 Aug, 2015 1 commit
-
-
Matt Perry authored
Just infer it from the sign of the velocity. That's what odeon does.
-
- 05 Aug, 2015 1 commit
-
-
Hans Muller authored
-
- 04 Aug, 2015 2 commits
-
-
Adam Barth authored
It was confusing to have both widget.dart and widgets.dart
-
James Robinson authored
This introduces the notion of event disposition and allows event targets (widgets and render objects) to consume events that should not be processed further. This is needed by the Switch component in the Drawer in the stocks example. The Switch is embedded in a DrawerItem. The Switch handles the gesture tap event to toggle its state and should handle pointer events to allow swiping and draw its own radial reaction. The DrawerItem also handles gesture taps to allow toggling the switch value when tapping anywhere on the drawer and to draw its own ink splash. When tapping on the switch, both the switch's render object and the DrawerItem's listener are in the event dispatch path. The Switch needs to signal in some fashion that it consumed the event so the DrawerItem does not also try to toggle the switch's state.
-
- 03 Aug, 2015 4 commits
-
-
Adam Barth authored
-
Matt Perry authored
-
Matt Perry authored
* Intentions => Behaviors * SlideIn => SlideTransition * FadeIn => FadeTransition * removed unused AnimatedContainer intentions
-
Matt Perry authored
Simplifies the code a bit.
-
- 30 Jul, 2015 1 commit
-
-
Adam Barth authored
-
- 28 Jul, 2015 2 commits
-
-
Chinmay Garde authored
-
Chinmay Garde authored
-
- 24 Jul, 2015 1 commit
-
-
Hans Muller authored
-
- 23 Jul, 2015 1 commit
-
-
Adam Barth authored
- Remove unused imports - Remove unused, broken constructor for MineDiggerApp
-
- 22 Jul, 2015 2 commits
-
-
Hans Muller authored
-
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.
-
- 21 Jul, 2015 2 commits
-
-
Matt Perry authored
-
Hans Muller authored
-
- 16 Jul, 2015 2 commits
-
-
Matt Perry authored
-
Collin Jackson authored
-