Tobias Bosch

Under the cover, we would do the following: - for each property annotation with `@Content`, collect the list of matching elements from the content area of the component. Note that...

Inserting the nodes requires a container that keeps track of them: Given the following example: ``` ``` Here, the nodes of the nested `ngIf` template are siblings to the nodes...

Given the above comments / analysis, I think we should do the following: ``` class MySelect { // query for nodes: @ContentChildren('my-option') optionEls: QueryList; // inserting nodes: someAction() { this.someViewContainer.insertElements(this.optionEls);...

Applied to the use case of wrapping projected elements: ``` @Component({ template: ` ` }) class MySelect { @ContentChildren('*') allContentEls: QueryList; } ``` I.e. `ngViewOutlet` will support taking a element...

To get directives, you have to query for them as well: ``` class MySelect { @ContentChildren('*', read: MyOption) allContentOptions: QueryList; } ``` We could change this to allow an array...

@pkozlowski-opensource @mhevery I changed my proposal above to use `ElementRef`s instead of plain DOM elements. This more aligned to how we give users access to elements in DI. Also, I...

Talked with @mhevery a bit more how we can prevent breaking changes. We came up with the following: 1. Introduce a new `ElementContainerRef` which has a `addElements(els: QueryList)` -> no...

Hi, sorry, the notes above are just some hints for a future implementation, which is not going to be easy, as sencha touch does not support this itself. The workaround...

Hi, sorry, no, the adapter is not compatible with ST 2.x Please note that this adapter was only a proof of concept. Sencha Touch already includes an MVC framework, so...