**** BEGIN LOGGING AT Tue Oct 30 02:59:58 2012
Oct 30 15:24:05 <katratxo> sugardave: ping?
Oct 30 15:25:22 <katratxo> any ideas on this enyo.load question? http://forums.enyojs.com/discussion/921/enyo-load-and-callback-when-everything-is-loaded
Oct 30 15:33:52 <fxspec06_> woah enyo.load, i had no idea you could even do that
Oct 30 15:34:39 <fxspec06_> why don't you just list them the other way
Oct 30 15:35:00 <fxspec06_> or
Oct 30 15:35:21 <summatusmentis> the question in that thread suggests why, if the js is being created dynamically
Oct 30 15:35:51 <fxspec06_> enyo.load(['path/to/dynamic1.js'], function () {enyo.load(['path/to/dynamic2.js'], function() {})});
Oct 30 15:36:06 <fxspec06_> *workaround
Oct 30 15:36:59 <fxspec06_> actually that's pretty bad
Oct 30 15:37:30 <fxspec06_> enyo.load(['script1], enyo.load(['script2'], function(){console.log("callback")}));
Oct 30 15:37:49 <fxspec06_> even that is bad, but it should work, and looks nicer
Oct 30 15:38:31 <katratxo> fxspec06_: yes, that is the workaround i have thought ... chaining enyo.load calls as callbacks
Oct 30 15:39:08 * fxspec06_ wonders where enyo.load is defined
Oct 30 15:39:15 <katratxo> boot.js
Oct 30 15:39:23 <katratxo> there is a link in the forum post ;)
Oct 30 15:39:30 <fxspec06_> heh
Oct 30 15:39:43 <fxspec06_> i know most of the source 3/4 like back of my hand
Oct 30 15:40:14 <fxspec06_> mayb 1/2-3/4. somewhere in between. but there still new fns and stuff i don't go near
Oct 30 15:41:05 <katratxo> i like to go bottom-up ;) and try to see how enyo solves common problems
Oct 30 15:42:28 <fxspec06_> si
Oct 30 15:43:15 <fxspec06_> enyo.loader = new enyo.loaderFactory(enyo.machine); // << pretty badass line right there
Oct 30 15:43:29 <katratxo> yeap
Oct 30 15:51:04 <fxspec06> var args = runtimeLoadQueue.shift();
Oct 30 15:51:38 <fxspec06> that's what loads the next in line.. then it sets the callback to args[1] ......
Oct 30 15:52:42 <fxspec06> then defines finishCallback, and finally applies it which loads the scripts
Oct 30 15:53:07 <fxspec06> you COULD bind the callback to an enyo.async
Oct 30 15:53:14 <fxspec06> that mightr just fix yoru issue
Oct 30 15:53:27 <fxspec06> o.O
Oct 30 15:53:58 <fxspec06> enyo.load(['script1','script2'], enyo.async(function(){console.log("callback")}));
Oct 30 15:54:13 * katratxo checks
Oct 30 15:57:06 <katratxo> fxspec06: enyo.async doesn't exists .. we have enyo.asyncMethod, but it just delaying the execution with a setTimeout
Oct 30 15:57:39 <katratxo> for now, i'll chain the calls
Oct 30 15:58:13 <fxspec06> asyncMethod is what i meant
Oct 30 15:58:42 <fxspec06> the setTimeout should force it to wait until other processes are finished
Oct 30 16:00:06 <fxspec06> i can't explain why the callback happens after the first file, though. i'm not sure it was designed to do what you're trying to do, best way mgiht be just to chain the calls
Oct 30 16:00:16 <fxspec06> although it does seem backwards
Oct 30 16:01:01 <fxspec06> you COULD define your own private enyo.loader
Oct 30 16:01:19 <fxspec06> and force fix it to do what you need. but that seems.. overkill
Oct 30 16:03:56 <katratxo> fxspec06: thanks, is not really a big deal i have done similar things using LABjs
Oct 30 16:05:35 <fxspec06> cool.
Oct 30 16:05:45 * fxspec06 resumes not having school today
Oct 30 17:27:50 <sugardave> katratxo: I took a stab at the enyo.load question
Oct 30 17:28:02 <katratxo> sugardave: thanks!
Oct 30 17:28:11 <sugardave> short answer: chain enyo.loads together to enforce ordering
Oct 30 17:29:28 <katratxo> sugardave: ok, thanks
Oct 30 22:24:04 <sugardave> katratxo: so, I did a little more digging and my initial assessment was incorrect.  The enyo.loaderFactory clearly should be loading your sources, in order, and then executing the finalCallback
Oct 30 22:24:29 <sugardave> sorry for the confusion :)
**** ENDING LOGGING AT Wed Oct 31 02:59:58 2012