**** BEGIN LOGGING AT Tue Jul 07 02:59:58 2015 Jul 07 13:34:16 is the hackathon using enyo 2.6? :) if so, i'll join. Jul 07 13:54:20 :) Jul 07 13:54:41 I'd rather have a 'releaseathon' Jul 07 14:00:50 lol Jul 07 14:01:49 I'd rather have webOS on my TV be more open, like on the phones. But maybe that's just me. Jul 07 14:18:22 anyone know how to overcome the 20px top margin / statusbar issue on ios / cordova (phonegap) apps? Jul 07 14:19:03 i tried: margin-top:20px which helps but then it shift everything down 20px (cutting off the bottom). i also tried the statusbar plugin which didnt work at all.. Jul 07 14:19:49 i think it has to do with the enyo-fill class that's causing it to take up whole screen rather than respecting the two suggested fixes...just wondering if anyone else figured it out and could lend me some pointers? Jul 07 14:26:56 Cage1___: what 20px top margin issue? Jul 07 14:28:03 Cage1___: also, what classes are you using? Can you put up a fiddle or a pastebin url? (don't use pastebin.com) Jul 07 14:28:36 http://devgirl.org/2014/07/31/phonegap-developers-guid/ Jul 07 14:30:21 it's just bootplate. Jul 07 14:31:21 i'm not adding any special classes beyond what it already does...it adds enyo-fill Jul 07 14:31:45 jsfiddle wont help because you would have to compile the app as a cordova/phonegap app and then run in ios to see it Jul 07 14:33:51 Cage1___: write it from scratch instead of using the bootplate Jul 07 14:34:12 ?? Jul 07 14:34:31 your html skeleton Jul 07 14:34:42 then you can class it as need be Jul 07 14:36:19 which class would you recommend? enyo-fill or enyo-fit or something else? Jul 07 14:40:48 Cage1___: http://jsfiddle.net/9bzwf8pt/ Jul 07 15:07:57 i'll try it out ..thanks Jul 07 15:08:04 yw Jul 07 17:42:33 hi derek Jul 07 17:42:43 morning dmanderson Jul 07 17:43:20 yo! Jul 07 17:47:00 news ? :) Jul 07 17:53:35 good morning Jul 07 18:41:57 ? Jul 07 18:42:58 Cage1___: hrm? Jul 07 18:43:10 did i miss the big news? Jul 07 18:43:21 Cage1___: nope. Semanticfire_2 is just starving for news Jul 07 18:46:42 :) Jul 07 18:57:15 dmanderson: are you guys implementing Facebook's Flux pattern in 2.6? Jul 07 18:57:42 we’ve been experimenting with adding some support for the pattern yea Jul 07 18:58:36 interesting Jul 07 18:58:58 how would renders be effected? Jul 07 18:59:15 Renders don’t really get affected in the Enyo world, since we do a single pass tree render anyway. Jul 07 18:59:40 It really allows us to get out from under observers and the overhead of Enyo’s component structure Jul 07 19:00:03 so is there any ETA :) Jul 07 19:00:06 We’ve done a few things like adding vanilla object support to DataRepeater Jul 07 19:00:11 I don’t speak ETAs! Jul 07 19:00:19 :) Jul 07 19:00:40 will Bindings still be able to be defined in the same way? Because I gotta say, I like how Bindings are defined in Enyo better than the way you have to pull off similar functionality using general flux techniques Jul 07 19:01:04 Yes, but when using a vanilla object you must manage the sync Jul 07 19:01:33 interesting Jul 07 19:02:17 so if you cant do ETAs when it be feature complete .) Jul 07 19:02:33 HAHAHA Jul 07 19:02:35 how much stuff will break with the 2.5 -> 2.6 release ? Jul 07 19:02:44 (all of it .)) Jul 07 19:02:55 no way to drop in and replace Jul 07 19:03:01 :( Jul 07 19:03:12 But the benefits are substancial. Jul 07 19:03:14 still struggling to migrate to 2.5 Jul 07 19:03:21 so its more a 3 then ? Jul 07 19:03:24 in 3 bullet points, what benefits :) Jul 07 19:03:27 We’ve managed to shave 50-70% of the code shipped with apps Jul 07 19:03:54 Basically it’s what we would have done in a 3, but want to put in a 2.x so we can get Korea to adopt it in the next few years Jul 07 19:04:06 Honestly, I don't feel like 2.6 will break too much, as long as you import like so: Jul 07 19:04:11 enyo = { Jul 07 19:04:30 Input: require('input.js'), Jul 07 19:04:58 then it would act similar to the global object Jul 07 19:05:12 Some what, you’ll still get warns for using strings Jul 07 19:05:19 oh yea Jul 07 19:05:32 I'm just dispelling the doom and gloom that Cage1___ has Jul 07 19:05:33 and a few things have moved. Jul 07 19:05:45 enyo.inherit is now kind.inherit Jul 07 19:06:03 large number of thing smoved to utils Jul 07 19:06:09 enyo.exists is now utils.exists Jul 07 19:06:21 that makes sense Jul 07 19:06:22 Other than that, the move is pretty seamless Jul 07 19:06:28 any improvements to data layer, especially related models/collections? Jul 07 19:06:38 utils probably contains all of the old browser compat stull, right? Jul 07 19:06:41 Other than offering an implimentation outside of them - no Jul 07 19:06:43 enyo.map, enyo.filter, etc. Jul 07 19:06:49 :( Jul 07 19:06:49 right Jul 07 19:07:07 I’m sure our data layer ill be re-examined soon. Jul 07 19:07:14 We know its very slow. Jul 07 19:07:30 It’s based on backbone < 0.9 Jul 07 19:07:37 any updates to the Onyx and layout ? Jul 07 19:07:46 Nothing substancial to either libs Jul 07 19:07:46 well, plus i haven't figured out a great way to get models related to each other - probrbably a way but i haven't figured it out... Jul 07 19:08:03 Cage1___: "related" to each other? Jul 07 19:08:13 Relational Models Jul 07 19:08:18 exactly Jul 07 19:09:05 Flux should help with that ;-) but not exactly what you want. Jul 07 19:10:31 can you mention a Q ? Jul 07 19:11:00 should i be learning flux now? Jul 07 19:11:29 Flux is a worthwhile pattern Jul 07 19:11:37 It’s basically a redesign of MVC Jul 07 19:11:43 where you have a monolithic controller Jul 07 19:12:00 Whats up Semanticfire_2? Jul 07 19:12:14 Cage1___: I would suggest not learning flux right now. It's a simple paradigm that everyone overcomplicates the explanations for (kind of like MVC) Jul 07 19:12:19 a Quarter :) Jul 07 19:12:23 i hate controllers. i'm sstill trying to get rid of the ones i have in my app from ??2.1 Jul 07 19:12:25 wait until they have enyo examples that show you how to use it Jul 07 19:13:44 dmanderson: he wants a general release date Jul 07 19:13:58 haha Jul 07 19:14:02 he's really trying Jul 07 19:14:09 lol yea Jul 07 19:14:12 how about a year? :) Jul 07 19:14:16 LOL Jul 07 19:14:31 I want to know, too. But I figure they've been told not to tell us this stuff. Jul 07 19:14:42 we wont tell anyone!!! Jul 07 19:15:18 Ha, no I just really don’t know :) Jul 07 19:15:22 Soon for sure Jul 07 19:16:48 soon?!! :) Jul 07 19:17:03 or are you pulling our leg Jul 07 19:17:15 dmanderson: enyo.ready() will now just be ready = require('ready.js'), I'm guessing? Jul 07 19:17:30 require(‘enyo/ready’); Jul 07 19:17:38 we rewrite the CJS paths Jul 07 19:17:43 ah, ok Jul 07 19:17:54 any new kinds/components? or mostly reworking of existing Jul 07 19:18:02 so it's a lot like what we're doing in our react stuff Jul 07 19:18:24 Nothing too exciting thats new, there are always feature enhancements, like we’ve got an SVG kind now Jul 07 19:18:32 Cage1___: I see NewDrawer.js and NewThumb.js Jul 07 19:18:53 We’ve been battling it out on the TV with QML, so a lot of the enhancements you’ll see are things we’re doing to get our selves closer to Native. Jul 07 19:19:07 dmanderson: will Mochi be updated to match the pattern? Jul 07 19:19:17 Nah, it’s safe to say Mochi is unsupported Jul 07 19:19:22 damn Jul 07 19:19:56 Nothing stopping someone from doing it :) But as far as LG’s objectives and the team, we’re pretty thin to support Mochi Jul 07 19:20:11 I see Jul 07 19:21:06 how about onyx / layout ? Jul 07 19:21:21 will that keep support ? Jul 07 19:21:43 Yeah we’re sill supporting those about as good as we have been…. :-| Jul 07 19:21:50 most of out resources are thrown at Moonstone Jul 07 19:21:57 Obviously that’s the active commerical platform atm. Jul 07 19:22:30 although for how long that will be, given LG's horrible policies regarding WebOS on TVs, remains to be seen. Jul 07 19:23:00 ;-) Jul 07 19:24:24 bbl, heading home Jul 07 19:26:53 leaves me in the blue if enyo is a solid choice Jul 07 19:49:04 Enyo is a great choice :) Jul 07 19:49:11 I’m still commited to pushing it farther and farther. Jul 07 19:49:26 I’m currently working on Hybrid Apps build with enyo Jul 07 19:49:33 1 JS file, that you either run with node Jul 07 19:49:39 or serve in an HTML page. Jul 07 19:50:06 I'm using it with bootstrap as wierd as that might sound Jul 07 19:50:11 https://s3.amazonaws.com/uploads.hipchat.com/43894/983790/2oEnlHvdNtlcRpN/Screen%20Shot%202015-07-07%20at%2012.37.48%20PM.png Jul 07 19:50:32 Semanticfire_2 I do that a lot, this is one of my current bootstrap enyo projects http://togglegreen.parseapp.com Jul 07 19:52:35 its doing the rendering through enyo with bootstrap UI ? Jul 07 19:52:43 * Semanticfire_2 is happy he is not the only one Jul 07 19:53:02 dmanderson, probably won't be in the bay area any time soon Jul 07 19:53:24 Semanticfire_2 yea using bootstrap to do the UI, and some jQuery plugins Jul 07 19:53:35 but enyo is the whole backbone of the view, controller stuff. Jul 07 19:55:46 so, what did I miss? Jul 07 19:55:54 did Semanticfire get a date out of dmanderson? :P Jul 07 19:56:07 LOL no Jul 07 19:56:14 I was just sharing my cool project for today Jul 07 19:56:15 https://s3.amazonaws.com/uploads.hipchat.com/43894/983790/2oEnlHvdNtlcRpN/Screen%20Shot%202015-07-07%20at%2012.37.48%20PM.png Jul 07 19:56:21 Hybrid Enyo apps Jul 07 19:58:50 Tell us more Jul 07 19:59:07 ha not much to say atm. Jul 07 19:59:08 :) Jul 07 19:59:18 Just a single minified js file. Jul 07 19:59:21 ‘helloworld.js" Jul 07 19:59:25 you can serve it in a browser Jul 07 19:59:34