Hi Sander I'm sure there are going to be plenty of edge cases.. That's why I wanted >> something simple at first. I'm hoping to get 90% case coverage with 10% >> effort ? >> > I'm afraid that in this case the numbers will be more like 75% coverage > with 40% effort. But don't let me talk you out of it. If you get this > running it will be an enormous help to > a fair number of developers. >
Well, we can see how it goes.. . If I append the inject property defined in scope to $attr in ng-repeat's compile, it looks like it should work fairly cleanly. ng-repeat evaluates the $attrs properly, so if I'm careful to keep it simple, it should work. > > I haven't really explored angular 2.0, I'm not on the inside track, so >> I'll have to wait until its solid.. I believe this project will be >> significantly easier with 2.x and will require a ground up redesign. >> > Well, I keep my eye on 2.x and yes and yes ;) > > >> I do like the annotation driven compiler, specifically the ability to >> inject arbitrary annotations to specific objects. Annotations support >> becomes increasingly important in interpreted languages to easily create >> new features. I do recommend compile on the fly to reconfigure execution >> orders as lazy and on-demand modules are required. The documentation >> alludes to this, but its unclear whether the hierarchy just supports lazy >> compile or dynamic/modifiable configuration . Also, I see nothing wrong >> with the global state, other than static configuration. >> > Hi, If you are talking about the annotations from 2.0, those are part of > ATscript. ATscript compiles to ES5. As it is an language that does > compiling you can't use in the browser to do on the fly compilation(not in > a well performing way anyhow) > If the compile is done in the background in a private node which is then moved to the proper location in the DOM, it may work fairly transparently to the user. A wrapper around the compiler could perform those operations.. > Lazy loading will be supported, but this will be largely part of the new > router. And of course when ES6 modules become readily available, those will > be usable too. > Hmmm interesting b/r gary > > Regards > Sander > > -- > You received this message because you are subscribed to a topic in the > Google Groups "AngularJS" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/angular/ZNiEC50si2o/unsubscribe. > To unsubscribe from this group and all its topics, 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/d/optout. > -- 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/d/optout.
