1. 23 Sep, 2015 4 commits
    • Hixie's avatar
      fn3: Minor cleanup · 2a5fad93
      Hixie authored
      - Remove the unique objects used as slots since we decided 'null' was
        fine after all
      - Rename 'slot' to 'newSlot' when it's used as an argument to change the
        _slot field, to clarify which variable has the newer value
      - Remove the RenderObject registry since we'll do listeners a different
        way. This also removes handleEvent for the same reason.
      - Remove the TODOs for mount/unmount becoming didMount/didUnmount since
        the methods do in fact do the mounting/unmounting.
      2a5fad93
    • Hixie's avatar
      fn3: Binding to RenderView · 555138e6
      Hixie authored
      In the old world, we had two ways to bind a Widget tree to a
      RenderObject node, one way for RenderView and one mostly untested way
      for other cases (it's only tested by the spinning_mixed.dart demo). For
      fn3, I made these the same code path.
      
      This patch also introduces GlobalKey, though the GlobalKey logic isn't
      hooked in yet.
      
      This is Hello World in the new world:
      
      ```dart
      import 'package:sky/src/fn3.dart';
      
      void main() {
        runApp(new Text('Hello World!'));
      }
      ```
      555138e6
    • Adam Barth's avatar
      Add tests for MultiChildRenderWidget · 8b162b59
      Adam Barth authored
      8b162b59
    • Adam Barth's avatar
      Add support for multichild widgets to fn3 · 436fb0ee
      Adam Barth authored
      436fb0ee
  2. 22 Sep, 2015 20 commits
  3. 21 Sep, 2015 13 commits
  4. 20 Sep, 2015 1 commit
  5. 19 Sep, 2015 2 commits
    • Adam Barth's avatar
      27e6381e
    • Adam Barth's avatar
      Prototype of fn3 · b4ff5ca6
      Adam Barth authored
      This patch contains a prototype of a new widget framework. In this framework,
      Components can be reused in the tree as many times as the author desires. Also,
      StatefulComponent is split into two pieces, a ComponentConfiguration and a
      ComponentState. The ComponentConfiguration is created by the author and can be
      reused as many times as desired. When mounted into the tree, the
      ComponentConfiguration creates a ComponentState to hold the state for the
      component. The state remains in the tree and cannot be reused.
      b4ff5ca6