1. 25 7月, 2015 2 次提交
    • H
    • H
      Use the navigator to stack dialogs. · 9c851767
      Hixie 提交于
      This removes the need to manually include the dialog builder in the main window's build() function.
      It also removes the need to track if a dialog is visible.
      
      Other changes:
      - I made dialog.dart a bit more readable.
      - I renamed transitionFinished to fullyOpaque since that's what actually matters.
      - I made Routes track if they're opaque. Eventually this should probably be more configurable when creating the route.
      
      Directions for Future Research:
      - Use this for focus management somehow.
      - The popup menu should use something like this.
      - We should factor the following out into a showDialog() function that returns a future for the dialog's exit result:
          navigator.push(new DialogRoute(builder: (navigator, route) { ... }));
      - Maybe navigator.pop() should take a value to return to that Future.
      9c851767
  2. 23 7月, 2015 1 次提交
    • H
      Introduce an explicit Key type. · 383e504f
      Hixie 提交于
      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.
      383e504f
  3. 22 7月, 2015 2 次提交
    • H
      Rationalise usage of keys in navigator.dart. · 761ab683
      Hixie 提交于
      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.
      761ab683
    • M
      Renamed AnimatedType to AnimatedValue · a421da3c
      Matt Perry 提交于
      a421da3c
  4. 18 7月, 2015 3 次提交
  5. 17 7月, 2015 4 次提交
  6. 15 7月, 2015 1 次提交
  7. 12 7月, 2015 1 次提交
  8. 07 7月, 2015 1 次提交
  9. 19 6月, 2015 2 次提交
  10. 18 6月, 2015 1 次提交
  11. 17 6月, 2015 3 次提交