Thanks! Originally I just wanted a way to add a src attribute to any element, I eventually realized that it could be used to finally fix my issues with templates; too much javascript scaffolding.
It's a nice fun little tool -- but it's rather inefficient in terms of the number of AJAX requests that it needs to do in order to fetch the templates. The rather simple linked page needs a total of 3 AJAX requests, one for each template. As your app (especially mobile apps) needs more templates, it probably won't be very performant. There's a reason why Ember and other frameworks prefer their templates to be embedded right in the HTML -- no need for separate AJAX fetching.
I believe Angular will search for inline templates first, so as long as you use the same path for the template name it won't attempt any AJAX fetching.
If you added a build process that actually pulled in the source files for a bundled production file you might have something similar to RequireJS for templates.
Doesn't require.js include plugins that will pull in compiled templates for you for the major templating libraries already? (underscore, mustache etc)?
13 comments
[ 3.2 ms ] story [ 38.9 ms ] threadThis is functionnality very similar to http://www.aimath.org/knowlepedia/ but done much better.
example usage of knowl.js here (loads proofs inline) http://linear.ups.edu/html/section-HSE.html
Cool stuff.