1. 08 Sep, 2015 1 commit
    • Adam Barth's avatar
      Introduce package:sky/animation.dart · b356d146
      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.
      b356d146
  2. 02 Sep, 2015 1 commit
    • Adam Barth's avatar
      Move widgets and rendering inside src · 693ddcd8
      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.
      693ddcd8
  3. 28 Aug, 2015 2 commits
  4. 22 Aug, 2015 1 commit
  5. 21 Aug, 2015 1 commit
    • Adam Barth's avatar
      Rename all the scrollable classes · 010589be
      Adam Barth authored
      Block -> BlockBody
      ScrollableBlock -> Block
      FixedHeightScrollable -> ScrollableWidgetList
      VariableHeightScrollable -> ScrollableMixedWidgetList
      BlockViewport -> MixedViewport
      010589be
  6. 20 Aug, 2015 1 commit
  7. 13 Aug, 2015 1 commit
    • Matt Perry's avatar
      Fix common asserts in animation API. · 8a729317
      Matt Perry authored
      1. We would assert if you tried to start an animation from within an
      animation status callback. This is a common pattern, so I fixed this
      assert (in Ticker._tick).
      2. We would assert for animations with duration under a millisecond.
      Fixed.
      
      Also removed the workarounds assocated with #1.
      8a729317
  8. 10 Aug, 2015 1 commit
  9. 06 Aug, 2015 1 commit
  10. 04 Aug, 2015 1 commit
    • James Robinson's avatar
      Teach event system about disposition and make 'consumed' disposition terminal · 53163f8b
      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.
      53163f8b
  11. 03 Aug, 2015 2 commits
  12. 02 Aug, 2015 1 commit
  13. 31 Jul, 2015 1 commit
  14. 30 Jul, 2015 2 commits
  15. 28 Jul, 2015 3 commits
  16. 22 Jul, 2015 4 commits
    • Adam Barth's avatar
      3d0b82eb
    • Hixie's avatar
      Introduce an explicit Key type. · 74575775
      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.
      74575775
    • Matt Perry's avatar
      Make SnackBar animate itself. · b31e06a5
      Matt Perry authored
      b31e06a5
    • Matt Perry's avatar
      rebase · 839e997e
      Matt Perry authored
      839e997e
  17. 21 Jul, 2015 2 commits
    • Hixie's avatar
      Rationalise usage of keys in navigator.dart. · 9da399b0
      Hixie authored
      Route (named routes) no longer have a key, and have their own storage for their names.
      RouseState no longer has a key, and uses an owner field pointing to a StatefulComponent instead.
      As such, RouteBase no longer has a key.
      
      HistoryEntry no longer uses a global int to ensure uniqueness.
      
      Propagated this to stocks app.
      9da399b0
    • Matt Perry's avatar
      Renamed AnimatedType to AnimatedValue · 0fd3302e
      Matt Perry authored
      0fd3302e
  18. 16 Jul, 2015 2 commits