**** BEGIN LOGGING AT Sun Apr 03 02:59:58 2016 Apr 03 06:03:16 DougReeder: I'll respond to your mailing list email in more detail tomorrow (as much as I can with my NDA) but I definitely want to caution against making assumptions about what next-gen Enyo will look like or what devices it will target. Apr 03 06:03:41 * DougReeder nods Apr 03 10:17:21 Morning Apr 03 10:23:24 DougReeder: that was a good mail; it's unfortunate that I know so little about mobile friendly web frameworks Apr 03 10:33:36 morning :) Apr 03 10:34:40 Tofe: Seems our audio in web is broken again :S Apr 03 10:34:57 Both WAV and MP3 doesn't play sound in Testr. But sounds in CardShell work Apr 03 10:37:04 Herrie: that would be a Chromium thing then Apr 03 10:37:29 I didn't fix my cpu heating yet, so no build here :p Apr 03 10:37:58 But I decided to buy an upgrade for my good ol' hardware, MoBo+Cpu+Ram Apr 03 10:38:44 Should be ready in about 10days Apr 03 10:40:07 :D Apr 03 10:58:40 10 days is quite long, long delivery times in France? Most hardware here is available next day or day after when you order it online ;) Apr 03 11:00:52 No, it's just because Amazon doesn't have the CPU I want yet Apr 03 11:01:07 I see ;) Apr 03 11:01:16 What's your new system gonna be? Apr 03 11:01:42 i5 6600, 4 cores at 3.9Ghz, 16Gb RAM Apr 03 11:01:54 (DDR4) Apr 03 11:02:06 That should hold a couple of years Apr 03 11:02:19 :D Apr 03 11:03:29 For my last hw I wanted a high-profile of the EOL generation (Core2); but that proved to be a mistake in the end, because today I can't upgrade anything without changing the whole thing Apr 03 11:04:00 Yeah that's a pitty Apr 03 11:04:06 So now, I'm doing a bit the opposite: a medium-profile of the next gen Apr 03 11:04:15 Maguro is not locking up since yesterday evening btw ;) Apr 03 11:04:30 Ah, that'd good! I think we can close the issue :p Apr 03 11:24:59 I guess so too :) Apr 03 11:25:12 TP ran out of battery because screen was on ;) Apr 03 12:40:06 Ok, last try for the thermal paste, and after that I'll just wait for my new PC :) Apr 03 12:43:18 nope, 72° under high load for the cores Apr 03 12:43:28 Let's just wait a couple of days Apr 03 13:29:21 I am developing under Ubuntu 14.04 (mostly). Thought I might look at Enyo 2.7. It needs nodejs v4 or greater... Apr 03 13:30:24 Any favourite ways to install and maintain vaguely up to date versions of nodejs on linux? Apr 03 13:59:17 Tofe: Hehe ;) Apr 03 13:59:26 If you have any suggestions for fixes, I can test locally here Apr 03 13:59:32 Moved to Ubuntu 15.10 y'day ;) Apr 03 13:59:41 In my VBox ;) Apr 03 14:02:46 Herrie: I think it's mainly just some configuration to do with qtwebengine Apr 03 14:33:40 Tofe: Well we have some odd error msg Apr 03 14:33:57 Apr 02 13:02:46 tenderloin LunaAppManager[1655]: Qt WebEngine ICU data not found at /usr/sbin. Trying fallback directory... The application MAY NOT work. Apr 03 14:34:44 Herrie: for this one I've already had a look: it nothing really scary actually Apr 03 14:35:00 just icu data aren't installed by default on embedded platforms Apr 03 14:35:19 there's a Qt bug about it (there is a link somewhere in the logs here) Apr 03 14:35:47 http://code.qt.io/cgit/qt/qtwebengine.git/commit/?id=eda6a3559b303c9e13d755efd4af17fbe2ac9c95&dt=1&context=7 Apr 03 14:35:51 I think we need that patch? Apr 03 14:36:03 Tofe: [21:01:21] Herrie: also we have this issue (not a serious one hopefully): https://bugreports.qt.io/browse/QTBUG-51156 Apr 03 14:36:06 But yeah seems just a warning Apr 03 14:37:00 We could use that patch yes Apr 03 15:06:58 Tofe: Seems there are quite some commits in upstream 5.6 qtwebengine repo. How do I update our? Seems there are merge conflicts. Apr 03 15:07:20 I guess due to your patches which now need to be applied elsewhere? Apr 03 15:08:04 depends on the commits, let's see Apr 03 15:09:15 If you tell me how to do it, I can take care of this going forward :) Apr 03 15:10:53 mmh looking at the commits, I think we could as well wait a bit until 5.6 is actually released Apr 03 15:11:07 Arg, I didn't want to write this -- forget it :) Apr 03 15:11:47 It's maybe better if I do the rebase and the merges I think Apr 03 15:12:14 I already know that code, and I know C++ well Apr 03 15:12:46 Tofe: Chromium seems to be able to straight merge :) https://github.com/webOS-ports/qtwebengine-chromium/pull/7 Apr 03 15:13:43 Let's merge both at the same time Apr 03 15:14:14 We are on master-next, isn't it? Apr 03 15:14:47 Tofe: Yeah Apr 03 15:14:59 master-next = 5.6 based. master = 5.5.1 Apr 03 15:15:39 ok, let's go Apr 03 15:19:09 Tofe: For later: https://bpaste.net/show/7dfb6877afd6 Apr 03 15:21:12 yup Apr 03 15:21:32 These segfaults with libc are weird... Apr 03 15:21:39 They happen at many places it seems... Apr 03 15:21:50 Almost thinking it's libc somehow Apr 03 15:22:54 I've done the rebase in https://github.com/Tofee/qtwebengine/tree/tofe/work-5.6, but it won't merge with our master-next, of course... I didn't think of that. Apr 03 15:23:51 I'd like to keep our modifications on top of the rest, to keep clear what has been tinkered with Apr 03 15:24:59 Ok, I've now put my tofe/work-5.6 in the webos-ports fork itself Apr 03 15:25:15 so that we can test it easily with a little recipe change Apr 03 15:26:54 I guess we can merge your chromium quite safely Apr 03 15:31:06 Tofe: OK :) Apr 03 15:31:14 Yeah chromium changes looked nothing too shocking to me Apr 03 15:31:32 I can create my own branch for those though, run a test and then merge both? Apr 03 15:31:49 too late Apr 03 15:32:02 anyway we can point to whatever commit we want Apr 03 15:34:31 Tofe: true Apr 03 15:34:34 Let me kick off a build Apr 03 15:52:23 Tofe: Seem that the UI slowdown is also gone with 5.6 :D Apr 03 15:52:57 I guess it was caused by DBUS too :D Apr 03 15:54:13 * notes that Enyo [2.7] doesn't want to use git submodules any more, so the difficulties they present to the build system have just gone away. Apr 03 15:56:26 (Oh yeah. /me not '*') Apr 03 18:00:55 elvispre: That's a plus. I didn't look too much into Enyo 2.7 yet. Been busy getting QT 5.6 and Jethro switch sorted :P Apr 03 18:04:10 Herrie: Well, this has largely been a wasted afternoon. The documentation on how to migrate from 2.5 to 2.7 turns out to be a super-minimal collection of clues. I can't get anything bar the one-file Hello World example to even remotely work. Apr 03 18:04:52 Hmmz that's not very helpful Apr 03 18:05:13 I might just be slow on the uptake. Apr 03 18:38:42 elvispre: Any questions I can answer? Apr 03 19:04:55 Andolamin: Well,... What does correct look like? Specifically, the templates don't seem to me to exist. Apr 03 19:05:05 "enyo init --template=enyo-app" seems to do exactly the same thing as "enyo init --template=moonstone-app". Apr 03 19:05:12 The same thing as enyo init, actually. Apr 03 19:05:17 And "enyo templates list" says "no such command 'templates'". Apr 03 19:06:16 s/enyo-app/onyx-app/ Apr 03 19:11:24 Not sure about the state of the templates. Apr 03 19:11:54 https://github.com/Andolamin/com.alanstice.cast/tree/receiver has a basic Enyo 2.7 app that I'm working on Apr 03 19:12:08 Or, I can migrate one of the LuneOS apps over to act as a sample Apr 03 19:14:58 Andolamin: Thank you. I'll take a look at your example. I strongly suspect the init with template commands are supposed to give me a basic working app; but they don't. (My main beef with http://enyojs.com/docs/latest/developer-guide/getting-started/conversion-to-2.7.html is that it starts from bootplate but doesn't show you what it should like afterwards.) Apr 03 19:15:36 s/like/look like/ Apr 03 23:46:13 Looks to me like my templates issue may be because Enyo 2.7 has been released but the corresponding enyo-dev npm package has not. Apr 03 23:57:23 Confirmed. (If you clone enyo-dev and install it from the source, the Enyo 2.7 getting started documentation works much better.) **** ENDING LOGGING AT Mon Apr 04 02:59:58 2016