Great work from the KO team! I'm interested in the component child nodes - specifically trying to create a series of editors which have a common template around them, and custom editor within - are there are any examples/ fiddles out there?

I'll answer my own question.. I've put a JSFiddle together to create a common-template which can wrap around the contents of another component. http://jsfiddle.net/Quango/... if anyone wants to have a look.

Solid work guys, as usual.

Great job ! Sync loading of components was really missing.

Did you consider some components event communication ?
For now we use ko.dataFor to identify parent viewmodel/component and some mixin on component
viewmodel to add simple communication support.

However now with $component and you control of component viewmodel live cycle you should be able to
easily extend components viemodels and provide some methods for sending and receiving methods between components.

Thanks. I fixed it in the docs.

It still mentions sync Ryan: 'If your component configuration has a boolean sync property,'

Thanks- got that one too.

good work! I love KO!

I'm really enjoying components but I'm having a hard time with the "ko.components.register('my-component', { require: 'some/module' });" syntax since I'm using System.js. Can you help Ryan?http://stackoverflow.com/qu...

Great Work, I want to propose a new standard binding something called virtualize or maybe an option for the foreach binding, let explain me better, I refer to a Virtualized list, like the winjs (http://try.buildwinjs.com/#... listview or like how all the mobile platforms handle large lists of items, I found an working code for Knockout 2 that implement a lot of what I'm talking about (https://github.com/tkirda/b... there is a demo with 200000 items and it performs really fast, I tested this on my Surface RT and works fine, maybe I'm writing this in the wrong place but I want to share this to start talking about it and see what you thinks.

Hi,
Knockoutjs 3.3 is not using Shadow DOM, AFAIK. Can we still guarantee style encapsulation? How?

nice work, components in components is an awesome feature!

Thanks for the great post!
I had a question regarding the $componentTemplateNodes context variable.

I have a scenario where I have three html nodes that I'd like to access individually inside the template. You mention the following: "If would still be possible to manipulate (slice) $componentTemplateNodes directly in the binding, depending on the complexity of the markup/scenario."

I was trying to access the nodes inside of $componentTemplateNodes by slicing it or simply using the index, but so far I've had no luck. Any ideas how this actually works? I could not find anything on Knockout's documentation either.

Any ideas?
Thanks!

Are U still working with knockout or you migrate to other framework?

whats going on with knockout??

Please, could you post a step-by-step tutorial about how to secure a KnockoutJS SPA using JWT? :)