var fn = ignore(function() { setTimeout(function{ .... } } )
fn(); // You'll get the real setTimeout
but in 0.6.0 we added can-wait
which prevents the need for that
so you don't have to manually tell us all of your deferreds
I can think of dozens of cases in which we’ve used promises & timers in which we wouldn’t want those to prevent SSR
That is the purpose, to know when rendering is complete
It would result in UI changing, however there would be a sizable delay
use helpers to only render certain parts in the client
so if you're not using that, no it does not
once the page is loaded our overrides are gone
I like it because it leads to more elegant user code
you can do
new XMLHttpRequest() and we'll know to wait for that
or
return User.getList() and we know about it
I think the answer is yes because i don't know what that is :)
done-autorender is like the stache/system plugin but applies to the main template only
so if you know a little about stache/system it's similar in what it does
but it also inserts the rendered fragment into the page for you
define([
"module",
"can/view/stache/stache",
"can/view/stache/mustache_core"
],function(module, stache, mustacheCore){
var renderer = stache([{"tokenType":"start","args":["p",false]},{"tokenType":"end","args":["p",false]},{"tokenType":"chars","args":["I'm a little tea pot"]},{"tokenType":"close","args":["p"]},{"tokenType":"done","args":[]}]);
can.view.preload("test_stache", renderer);
return function(scope, options, nodeList){
var moduleOptions = { module: module };
if(!(options instanceof mustacheCore.Options)) {
options = new mustacheCore.Options(options || {});
}
return renderer(scope, options.add(moduleOptions), nodeList);
};
});
If I wanted to use done-autorender w/ something like that
My builds do *.stache -> .stache.js, and utilize configuration so that I don’t need the !plugin syntax
If I were to be using done-autorender, I would be loading the pre-compiled stache JS file
Not to mention the coupling w/ live-reload ;(
in the component?
