**** BEGIN LOGGING AT Fri Jan 30 03:00:00 2015
Jan 30 04:30:25 <DougReeder> If you haven’t heard, in 2.5 you must set options: {parse: true} in Models to use a parse() method.
Jan 30 11:32:10 <kamil7> hi guys
Jan 30 11:33:00 <kamil7> i am looking for good tutorials (maybe screencasts) for enyojs
Jan 30 13:10:02 <Semanticfire_2> kamil7, http://dailyjs.com/2012/09/20/enyo-1/
Jan 30 13:10:13 <Semanticfire_2> kamil7, https://github.com/enyojs/enyo/wiki/Tutorial
Jan 30 13:10:18 * Semanticfire_2 is afk
Jan 30 13:10:29 <kamil7> Semanticfire_2: thanks
Jan 30 15:05:40 <trex0051> Maybe I'll have better luck asking today : Is there a stable way to display a loading screen for large enyo apps?
Jan 30 15:21:46 <GodGinrai> trex0051: I need you to elaborate on some things: 1) What do you mean by stable?  2) What kind of loading screen do you mean?
Jan 30 16:17:37 <trex0051> 1) I have read two options that all have pretty big down sides/instabilities a) loading a page that redirects to the app page b) have the html be the loading page then use javascript to load enyo/your app dynamically 2) What I'm looking for is an attractive loading screen which says "Please wait while the game loads, this takes on average one minute".  And has some animations.
Jan 30 16:49:18 <GodGinrai> trex0051: You could always have a containing kind that generates the loading screen at the beinning
Jan 30 16:49:43 <GodGinrai> with the loading screen having a high z-index
Jan 30 16:50:10 <GodGinrai> then, after the loading screen has rendered, you begin loading the game behind it
Jan 30 16:50:33 <GodGinrai> and once the gameReady event is thrown, tear down the loading screen
Jan 30 17:40:15 <GodGinrai> trex0051: does that make sense?
Jan 30 18:47:20 <sugardave> trex0051: you could take the easy way out and use enyo.Panels to do it
Jan 30 18:49:25 <sugardave> you could then just copy the html/css of your first rendered view and make that be your starting html; then load enyo/app after THAT is rendered
Jan 30 18:53:17 <trex0051> GodGinrai: and sugardave: sorry I disappeared. The problem is that all the enyo and app javascript downloading is what takes so long.  I need something before enyo is loaded.
Jan 30 18:54:22 <GodGinrai> hrm
Jan 30 18:54:36 <GodGinrai> dmanderson: enyo doesn't have lazy-loading of scripts yet, does it?
Jan 30 19:03:53 <GodGinrai> trex0051: is it loading enyo that takes too long? or loading all the files for your app specifically?
Jan 30 19:18:25 <trex0051> GodGinrai: it's a combination.  Really, I'm in debug for now, so I have no idea how deploy will go
Jan 30 19:21:44 <GodGinrai> well, if it's a matter of how long it takes the app files to load, and not enyo itself
Jan 30 19:22:00 <GodGinrai> then you can probably make an enyo app that is the loading screen
Jan 30 19:22:33 <GodGinrai> and have it load the game in an iframe after it has rendered the loading screen
Jan 30 19:22:59 <GodGinrai> due to it being in an iframe, you would be able to prevent any of the app's files from being loaded beforehand
Jan 30 19:23:09 <GodGinrai> so the loading screen should be able to show pretty quickly
Jan 30 19:23:48 <trex0051> or I could dynamically include that app's js file.
Jan 30 19:24:14 <GodGinrai> trex0051: yes and no.  I don't know how enyo deals with dynamically adding files
Jan 30 19:24:23 <GodGinrai> if that works, then yes, I would say to do it that way
Jan 30 19:26:27 <trex0051> I'll have to play and see how it goes.
Jan 30 19:26:49 <trex0051> now to make a really attractive, but very small loading screen.
Jan 30 20:15:27 <sugardave> trex0051: what I meant was, make an app with enyo.Panels and your loading screen as its only view; run it once; copy out the static html/css that was generated; make that the body of your index.html and strip out the parts that load enyo and app .js/.css; have a page load handler that lets you know it has rendered the static view; load enyo/app source
Jan 30 20:16:36 <sugardave> it will give the appearance of your loading page while it loads enyo/app behind it; once the app loads it will overwrite the existing body with the same view "seamlessly"
Jan 30 20:17:40 <sugardave> dmanderson and I are actually playing with some lazy loading experiments...you can't do it from debug enyo, you have to use built source
Jan 30 20:17:50 <sugardave> but it does work
Jan 30 20:32:42 <Semanticfire> I thought about that as a answer
Jan 30 20:32:52 <Semanticfire> but I though it was a bit on the edge ;)
Jan 30 20:34:41 <sugardave> it has some drawbacks I'm currently trying to work through when packaging it to a webos .ipk
Jan 30 20:35:02 <sugardave> but, I will be going to Hawaii in a couple of days, so I don't think I will solve it too soon :P
Jan 30 20:35:20 <Semanticfire> :)
Jan 30 20:43:18 <GodGinrai> lol
Jan 30 20:49:49 <trex0051> it seems that I can't load a script dynamically that does a document.write.  The browser prevents it because people generally don't want that.  it's stupid because that's exactly what I want
Jan 30 20:50:11 <GodGinrai> trex0051: why are you using document.write?
Jan 30 20:50:25 <trex0051> I'm not.  Enyo does to render my app
Jan 30 20:50:50 <GodGinrai> o.o
Jan 30 20:58:08 <sugardave> that's what I mean...you have to use the minified/deployed version to have any hope of it working
Jan 30 20:58:51 <sugardave> you can append the minified enyo.js script tag to head and it works; you cannot append the debug enyo.js script tag to head
Jan 30 20:59:46 <sugardave> same with using minified app.js vs. package.js
Jan 30 20:59:58 <trex0051> yeah, I was trying to use package.js
Jan 30 21:00:58 <sugardave> trex0051: similar to what I am doing now...you have to just rely on your logic to be sound while you use debug/unminified...then every once in a while, run tools/deploy.sh and hit index.html instead to test it "for real"
Jan 30 21:05:08 <trex0051> So, with app.js, we could asynchronously load it?
Jan 30 21:05:13 <sugardave> yes
Jan 30 21:05:39 <sugardave> I delay loading build/enyo.js, build/enyo.css, build/app.js, and build/app.css
Jan 30 21:05:59 <sugardave> one more caveat is that you want to make sure that enyo is ready before you try to load app.js
Jan 30 21:06:32 <trex0051> isn't there an enyo.ready?
Jan 30 21:06:32 <sugardave> and you won't be able to use enyo.ready for that, so we have a polling function that checks for enyo.ready function every 20ms
Jan 30 21:06:41 <sugardave> it won't be there until enyo.js is done loading
Jan 30 21:06:45 <sugardave> chicken and egg problem :D
Jan 30 21:06:50 <trex0051> duh :)
Jan 30 21:15:23 <trex0051> is there a way to undo a deploy?
Jan 30 21:27:20 <sugardave> trex0051: um, no?
Jan 30 21:27:42 <sugardave> but the next time you run the script it will overwrite the deploy directory
Jan 30 21:28:05 <sugardave> if you want, you can just delete the deploy directory and then load debug.html again
Jan 30 21:40:18 <trex0051> I was writing my async code, trying to handle both the debug and the "is enyo loaded yet?" and realized they are not compatible.
Jan 30 21:51:08 <sugardave> no, they are not...like George Michael says, "you got to have faith"
Jan 30 23:00:21 <dmanderson> lol morning enyos
**** ENDING LOGGING AT Sat Jan 31 02:59:58 2015