Boris Kaul

I've looked at different ways on how to remove boilerplate with virtual dom nodes for components, and I can't find any reasonable way to implement it right now. There is...

I will add optional library `liquid/dynamic.dart' that will use mirrors, and API will look something like that: ``` dart class MyComponent extends Component { ... } final vMyComponent = vComponentFactory(MyComponent);...

What about API for components like this: ``` dart class TodoItem extends Component { @property Item item; TodoItem(Context context) : super(context); build() => new VRoot([vdom.t(item.text)]); } final vTodoItem = vComponentFactory(TodoItem);...

And to those who likes OOP inheritance I am almost implemented Component Decorators :) ``` dart class Button extends Paper { Ripple _ripple; html.DivElement content; @property bool disabled; html.DivElement get...

I don't see any problems with mirrors for development mode and replacing them with transformers for production. Polymer and AngularDart using this model.

I don't see any other way to implement good API, and all other solutions that I can think of is way much worse. Javascript world is moving toward ES6/7 compilers...

Didn't tried it yet, maybe use `call()` method for children. ``` dart v.div(#key, styles: {'width': '100%', 'margin': '0 auto'})([ v.div(1)('line one'), v.div(2)('line two') ]); ```

Implemented new API for basic virtual dom elements, didn't notice any performance regressions in the VDom Benchmark. ``` dart v.div(#key, styles: {'width': '100%', 'margin': '0 auto'})([ v.div(1)('line one'), v.div(2)('line two')...

Just `v.div(1)` for empty element. I thought about making it implicit, and it is a tough choice. If I make it implicit, there will be different kinds of problems for...

To create complex web apps, we will need to create stateful components like this [button](https://github.com/localvoid/liquid/issues/2#issuecomment-64961430), and it doesn't matter which way we choose to do it, with WebComponents that described...