1. 12 6月, 2015 1 次提交
  2. 11 6月, 2015 1 次提交
    • H
      Remove one more use of mirrors: Components now have to explicitly sync their fields. · 003083a1
      Hixie 提交于
      This also removes one bit of magic to make it more obvious what on is
      going on during a sync, which should hopefully help.
      
      Components have to decide if they support being stateful or not. If
      they do, then they must implement syncFields() and have mutable
      fields; if they don't, then they must have final fields. This isn't
      particularly enforced, though.
      
      This also renames _willSync() to _retainStatefulNodeIfPossible(), for
      clarity, and fixes some minor style issues and one typo that was
      breaking the drawer.
      
      R=abarth@chromium.org
      
      Review URL: https://codereview.chromium.org/1174023003
      003083a1
  3. 05 6月, 2015 1 次提交
  4. 28 5月, 2015 1 次提交
  5. 27 5月, 2015 1 次提交
  6. 20 5月, 2015 2 次提交
  7. 22 4月, 2015 2 次提交
    • H
      [Effen] fix warnings · 77ffda1e
      Hixie 提交于
      remove members that are never read
      remove imports that are never used
      
      R=eseidel@chromium.org
      
      Review URL: https://codereview.chromium.org/1099203002
      77ffda1e
    • H
      [Effen] Prevent scrolling past the bottom of a scrollable list. · 830f8bf0
      Hixie 提交于
      - make the ScrollBehavior instance long-lived, rather than recreating
        it each time we update the list contents.
      - have OverscrollBehavior track the total height of the contents and
        the height of the scrollable region, so that it can determine when
        to stop scrolling down.
      - teach OverscrollBehavior about how to determine when to stop
        scrolling down, and how to bounce when it's too far down.
      - replace the 'energy' concept in Particles with a method that sets
        the energy and direction at the same time, instead of assuming that
        the direction is always positive when setting energy.
      - make FixedHeightScrollable lists track the number of items in the
        list and have them update their ScrollBehavior regarding this
        information as it changes.
      - track how many items are currently showing in the list stock list.
      
      R=eseidel@chromium.org
      
      Review URL: https://codereview.chromium.org/1097373002
      830f8bf0
  8. 21 4月, 2015 1 次提交
    • H
      [Effen] Only skip rows we're showing, when skipping past the rows that we've... · c1dd855d
      Hixie 提交于
      [Effen] Only skip rows we're showing, when skipping past the rows that we've scrolled beyond in the stock list.
      
      Currently, if you then scroll down N items with a filter set, we select which
      stock to show by taking the entire list of stocks, skipping the first N, then
      filtering the list, then selecting as many stocks as needed to fill the list.
      
      So suppose the list is A, B, Cx, Dx, Ex, F, and the filter is "x", and you've
      scrolled down 1 item.
      
      Currently we'd show Cx, Dx, Ex.
      
      Scroll down 1 again.
      
      We still show Cx, Dx, Ex.
      
      What we _should_ show is Dx, Ex if you've scrolled down 1, and just Ex if you've
      scrolled two.
      
      This patch fixes this. We now skip rows _after_ filtering. This fixes
      the bug whereby if you set a filter then fling the list, we show the
      same item over and over as if in a loop.
      
      R=eseidel@chromium.org
      
      Review URL: https://codereview.chromium.org/1057603006
      c1dd855d
  9. 02 4月, 2015 1 次提交
  10. 27 3月, 2015 1 次提交
  11. 18 3月, 2015 1 次提交
  12. 14 3月, 2015 1 次提交
    • A
      Organize sky/framework/animation · 1eb13d01
      Adam Barth 提交于
      This CL cleans up the sky/framework/animation as follows:
      
      1) I've moved code that's used only by the custom elements framework into
         sky/framework/elements/animation. This code is based on AnimationDelegates
         rather than Streams.
      2) Rename ScrollCurve to ScrollBehavior because it encapsulates more behavior
         than just a curve.
      3) Make the Generator interface explicit and mark subclasses as actual
         subclasses.
      4) Move Simulation into generators.dart because it implements the Generator
         interface.
      5) Move Animation out of generators.dart because it does not implement the
         Generator interface.
      
      R=eseidel@chromium.org
      
      Review URL: https://codereview.chromium.org/1001373002
      1eb13d01
  13. 13 3月, 2015 2 次提交
  14. 12 3月, 2015 1 次提交
  15. 10 3月, 2015 2 次提交
  16. 03 3月, 2015 1 次提交