If you care, here's an updated plunker (http://plnkr.co/edit/kCTnMaYNb91iuwWnQwRE?p=preview) which reveals where I'm headed. It uses the *compile* phase (not $compile) to shape up what will be the template and then hooks it to scope during *link* phase. I actually found a use for that distinction :-). Two uses actually: (1) I don't need to use $compile to get the scoped material in after manipulating the content (as I did when I tried w/o a compile phase) and (2) I don't encounter template-composition churn within an ng-repeat.
Note that a directive-local child scope is necessary because I expect the linker to add material to the scope that is only pertinent to the templatized instance; can't have that polluting the data-bound scope. To see what I mean, comment out the "scope: true" and it all goes to custard. Todo: figure out how I want to get the template into the directive. I have not updated the *readme.md* as all of this is work in progress. I'm developing this in the open. Let me know if you think I'm barking up the wrong tree. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
