**** BEGIN LOGGING AT Tue Oct 27 02:59:59 2015 Oct 27 06:21:15 morning Oct 27 06:21:25 DougReeder: You have any reservations about newer NodeJS ? Oct 27 08:07:49 Morning Oct 27 08:12:39 Herrie|2: I still need to review my changes of yesterday, because the userscripts (or webchannel, not sure which one) stopped working when I tried the new build Oct 27 08:15:26 Herrie|2: for the luna-platform.conf, maybe "HasHardwarePowerButton" ? I think it's the only button causing issues if not present Oct 27 08:28:07 morning Oct 27 08:28:23 Tofe: Well we might want to add something for volume button as well? Oct 27 08:28:45 Because some might have both or one of them. Oct 27 08:29:03 So would be good if could be distinguished between them. Oct 27 08:34:44 Herrie|Veer: but we can change volume easily through UI, isn't it? With system menu? Oct 27 08:35:34 Tofe: We don't have it currently, only brightness slider and mute. Not sure we'd want to have volume slider for targets with volume buttons? Oct 27 08:37:05 Ah ok, I thought we had one, I don't know why :) Then, yes, let's have HasHardwareButtons Oct 27 08:37:47 I propose we use Tweaks, and we set different default values depending on HasHardwareButtons Oct 27 08:38:16 Tofe: Well I think 2 separate values might be better. So if a target has only power or only volume we can do it based on that? Oct 27 08:38:50 Why would you want to use Tweaks for something that's depending on a target? Or you want to give the user the options somehow? Oct 27 08:39:19 So they can opt to have them even if it's not really required for their target? Oct 27 08:40:30 Herrie|Veer: yes, for example if someone likes to use system menu to initiate shutdown, or something like that Oct 27 08:41:49 Herrie|Veer: What we can do is have a list of hardware buttons that are present: "HasHardwareButtons=Power,Volume,Home" for TP for instance Oct 27 08:41:50 OK. So we do the changes to luna-device.conf, luna-next and enable the options in system menu based on Tweaks? Oct 27 08:42:16 yup Oct 27 08:42:43 though there is certainly something to change in luna-sysmgr-common to actually read the settings :) Oct 27 08:43:05 And we'd take the luna-device.conf value as default and overwrite it with Tweaks value when set? Oct 27 08:43:30 Herrie|Veer: yes, if you think it's not nonsense Oct 27 08:43:56 Tofe: I'm all for flexibility Oct 27 08:44:11 Saves the user hassling with luna-device.conf :P Oct 27 08:44:23 Also useful when a hardware button is "broken" Oct 27 08:44:44 Personnally, if there would be a shutdown option from system menu, I wuold use it. Push power button for so long has always been awkward to me Oct 27 08:46:44 OK I'll get it sorted together with Andolamin Oct 27 08:49:10 ok thanks Oct 27 08:55:03 morphis: ^ you OK with this from architecture point of view? Oct 27 09:02:08 Tofe: What should be the type for such enum? I guess not std::string but std::set as with some of the others that allow multiple values? Oct 27 09:24:58 I'd say same as for Applications Oct 27 09:45:52 OK let me work out some bits for luna-sysmgr, luna-sysmgr-common and luna-next and PR Oct 27 09:48:15 i'm having some problems building luneos-dev-image for qemuarm: ERROR: qtwebengine was skipped: incompatible with machine qemuarm (not in COMPATIBLE_MACHINE) Oct 27 09:51:11 lzm: Can you post a whole log somewhere (pastebin or bpaste?) Oct 27 09:51:24 Will have a look to see if I can find it. Oct 27 09:55:05 Herrie|Veer: https://gist.github.com/lessandro/db62f25442939a2021d6 Oct 27 09:56:08 Seems last qemuarm build we did (10 days ago) still had qtwebkit no qtwebengine Oct 27 09:59:04 JaMa: ^ Oct 27 10:01:16 can i just replace qtwebengine with qtwebkit? Oct 27 10:02:51 I guess so in general Oct 27 10:03:06 For your tests it shouldn't matter too much I'd say Oct 27 10:03:25 I guess you'd just want to boot to command line and test the compiler there? Oct 27 10:04:02 i need to compile all of webos/luneos Oct 27 10:04:21 i suppose i can checkout an older version Oct 27 10:04:25 So you wouldn't care too much about our browser and firstuse app to be working or not? Oct 27 10:05:10 lzm: Yes we switched org.webosports.app.browser to qtwebengine a few weeks ago. org.webosports.app.firstuse was this weekend I think. Oct 27 10:05:22 Older recipe with dependancy on qtwebkit should do the trick Oct 27 10:08:25 Tofe: You reckon we should put the Hardwarebuttons under UI or Hardware header in luna-device.conf? I'd say hardware? Oct 27 10:43:11 JaMa: morning Oct 27 10:45:34 morning Oct 27 10:46:24 Any reason why qtwebengine couldn't build for qemuarm? lzm was trying and got a qemuarm not in COMPATIBLE_MACHINE Oct 27 10:51:14 qemuarm is armv5 Oct 27 10:51:20 qtwebengine does not suppor tthat Oct 27 10:52:27 lzm: Ah that explains :) Oct 27 10:52:45 Our targets are armv7+ I believe :) Oct 27 10:53:15 is mako hardfloat or softfloat? Oct 27 10:54:30 also, my bitbake seems stuck in "NOTE: Preparing RunQueue" Oct 27 10:56:20 JaMa is OE/BB expert :) Oct 27 11:05:39 took 15 minutes to prepare the runqueue, but now it's building :) Oct 27 11:12:03 lzm: softfloat Oct 27 11:12:16 :) Oct 27 11:12:25 lzm: it was probably fetching a lot of sstate packages so the rest should be faster now Oct 27 11:13:01 JaMa: lzm is testing a compiler against OE/qemuarm :P Oct 27 11:14:24 ? Oct 27 11:16:11 just making sure this works with webos stuff: https://github.com/vectorfabrics/meta-pareon Oct 27 11:17:16 Herrie|Veer: I've just created jethro branch in meta-oe and meta-qt5, if you're still so interested in upgrade to Yocto 2.0 :) Oct 27 11:17:57 lzm: ah ok, have you seen secondary toolchain oe feature? is that what scripts/generate-conf.sh is using? Oct 27 11:19:40 JaMa: Sure interested! We're skipping 1.9 altogether? I.e. 1.9 = 2.0? Yocto wiki confuses me :P Oct 27 11:21:35 JaMa: the one meta-clang uses? Oct 27 11:22:30 meta-pareon has a recipe for the cross-compiler, and we just change the CC/CXX of the recipes we want to compile with pareon Oct 27 11:27:57 Herrie|Veer: yes, there won't be any 1.9 Oct 27 11:28:10 Herrie|Veer: current master branch will be released as 2.0 Jethro Oct 27 11:32:09 OK. Let me know once you have something to test. Got Mako, Tenderloin & Maguro lined up for it :) Oct 27 11:35:37 Herrie|Veer: Hardware is fine Oct 27 11:47:27 lzm: http://www.openembedded.org/wiki/Adding_a_secondary_toolchain Oct 27 11:47:39 not sure if it's used by meta-clang Oct 27 12:25:03 Herrie, I have had much chance to use newer node.js, but I don't knownof anything problematic. Oct 27 12:27:39 did you build node-dbus, node-sqlite3, node-taglib with it? Oct 27 13:04:27 JaMa: I guess those need some work. I might have a chance to look at it based on the documentation provided by the NodeJS team about breaking changes Oct 27 14:44:52 both qtwebengine and qtwebkit are failing during the linking stage Oct 27 14:46:50 https://gist.github.com/lessandro/6012241a68b5e42f624e Oct 27 14:47:00 it cant find libraries it just compiled Oct 27 15:17:35 Tofe: I think code wise it would be easier to have 3 separate values, otherwise I'm gonna need help for the C++ part :P Oct 27 15:22:27 Herrie|Veer: Ok; anyway, hardware buttons are not spreading out these days Oct 27 15:24:14 Tofe: Yeah I'm just a bit stuck on how to read the values. I think I got it pretty OK for the rest. 3 separate boolean values, 1 for each button would be less headache :P Oct 27 15:24:35 If it's just reading them, I can help Oct 27 15:26:04 Tofe: Well I have examples that puts them in an array but not sure how to do it further. I looked at appsToLaunchAtBoot for example. But 3 booleans would be a lot easier. Seems there are 100's of UI settings anyway already :P Oct 27 15:26:28 So 3 for actual buttons wouldn't make much difference :P Oct 27 15:27:17 Well, ok Oct 27 15:32:39 Tofe: I'll also expose "ShowNotificationsAtTop" so we can use this in the future for having notifications 2.x style at bottom like we have currently or 3.x style on top once we implement that Oct 27 15:32:47 Since I'm anyway busy now :P Oct 27 15:32:49 Herrie|Veer, Tofe: Should we add a 4th for brightness control or leave it? Currently, no way to control the Raspberry Pi backlight brightness, but it's something they're working on so I'd be fine leaving it Oct 27 15:33:33 Andolamin: I'd say each screen technically has brightness support? Oct 27 15:34:06 Unless you have some e-ink maybe? Oct 27 15:34:25 Most, for sure. With the Raspberry Pi it really depends on what display you're using. Many of the screens don't have brightness control Oct 27 15:35:06 The official touchscreen *technically* has brightness control, but access to it hasn't been implemented so there's no current way to modify it Oct 27 15:35:27 Andolamin: that's what I mean :P Oct 27 15:35:33 Well I can add a 4th value Oct 27 15:35:37 It's not much work Oct 27 15:35:40 For e-ink, I'd guess that the whole UI would have to be re-done so I'm not worried about that. Oct 27 15:38:16 Andolamin: Yes true Oct 27 17:51:09 Andolamin: Feel free to PR your QML changes to Luna-next-cardshell. I'll take it from there and sort the Tweaks/luna-device.conf integration then Oct 27 18:21:19 grrr... Qt guys really never test the window.open scenario... Oct 27 18:21:56 We now have a crash when setting the background color because they didn't take that scenario into account. Oct 27 18:27:57 Ah: https://github.com/qtproject/qtwebengine/commit/8b6bd564eddafe9b3fd42e19367c0f94e860ceed Oct 27 18:28:06 * Tofe goes cherry-picking... Oct 27 18:29:23 Well it are only a few lines Oct 27 18:29:26 Could've been a lot worse Oct 27 18:29:35 But I guess it means another number of hours for building? Oct 27 18:32:10 Yep! Oct 27 18:32:50 Hopefully, in the meantime, I've solved the async initialization of webos-api.js Oct 27 18:33:00 :D Oct 27 18:33:10 So that was the latest showstopper? Oct 27 18:33:16 How about the other backports? Oct 27 18:33:18 Those work? Oct 27 18:33:37 I didn't test them yet; where can I find a URL link in an app ? Oct 27 18:34:13 Not sure what you want to test exactly/ Oct 27 18:34:14 ? Oct 27 18:34:25 Accounts opens external URL for Google C+DAV Oct 27 18:34:57 but I mean I think I should click on a link myself to trigger a navigationRequest, right? Oct 27 18:35:09 Ah that could be... Not sure let me see Oct 27 18:35:45 Maybe maintainer URL in PReware 2 for app? Oct 27 18:36:01 I found a license link in Maps, but it opens in same window Oct 27 18:36:35 That looks wrong, I can't go back Oct 27 18:36:37 URL in preware app Oct 27 18:36:51 So open the maps app description and click on the URL Oct 27 18:36:59 It will open a browser window for me with URl Oct 27 18:37:41 ah! me too. Oct 27 18:37:45 Or you mean something else? Oct 27 18:37:52 great, that one is fine Oct 27 18:37:54 Or this is the scenario you're looking for? Oct 27 18:38:07 yes yes, I wanted to trigger this signal Oct 27 18:38:29 now for the webengineprocess crash, that'll be easy, I'll just kill it :) Oct 27 18:40:06 It bascially does a call to palm://com.palm.applicationManager/open Oct 27 18:40:28 Going by the code in https://github.com/webOS-ports/preware/blob/master/source/PackageDisplay.js#L20 Oct 27 18:40:46 Which I guess calls org.webosports.app.browser with launchparams Oct 27 18:40:49 ok, webengineprocess crash detected and luna-webappmanager restarted Oct 27 18:41:30 Herrie: ah wait, then maybe it isn't what I wanted Oct 27 18:41:46 I want to go in that code: Oct 27 18:42:06 You want inAppBrowser? Oct 27 18:42:10 https://github.com/webOS-ports/luna-webappmanager/blob/master/src/qml/ApplicationContainer.qml#L149 Oct 27 18:42:11 Not sure what you're looking for :P Oct 27 18:43:25 maybe links in pivotce webapp? Oct 27 18:44:10 Shouldn't I test it in an enyo app ? Oct 27 18:47:00 What does it do with webkit when clicking on the Apache license link in the Maps app in info tab ? Oct 27 18:49:21 If window.open works again, I think we'll be ok for the switch Oct 27 18:52:44 Herrie: please wait for confirmation before merging https://github.com/webOS-ports/qtwebengine/pull/7 Oct 27 18:53:07 It should be fine, but I'm still waiting for my build :) Oct 27 19:16:50 Copy of the License link? Oct 27 19:17:38 Ah wait it opens the page Oct 27 19:17:40 App is gone Oct 27 19:18:26 With Apache 2.0 license. Back gesture doesn't work. That's not very nice :P Oct 27 19:18:53 Herrie: ok, so it's not a regression at least Oct 27 19:28:30 Tofe: Any regressions left as far as you know? Oct 27 19:30:29 The loading splashscreen disappear a little bit too soon Oct 27 19:30:59 Otherwise, no. Oct 27 19:31:11 But I certainly missed some Oct 27 19:31:14 And the fonts I guess? Oct 27 19:31:29 That's not a reg :) but the issue is there too Oct 27 19:31:53 webOS without Prelude is horrible :P Oct 27 19:31:58 yep Oct 27 19:31:58 It's a really nice font Oct 27 19:37:57 Tofe: So when your build is done and OK, we're ready to complete the migration? Oct 27 19:38:22 Include it in nightly and I can stress test it :P ? Oct 27 19:38:49 yup Oct 27 19:39:17 compile step is finished now, it has moved on to install... I'd say 20min left Oct 27 19:39:39 :D Oct 27 19:39:50 I'll be PR-ing my luna-sysmgr config changes shortly Oct 27 19:39:56 Should be OK to merge Oct 27 19:40:24 Andolamin: I guess you can add the 4 values to your .conf and PR that already too against luna-sysmgr in our branch ;) Oct 27 19:41:30 Tofe: https://github.com/webOS-ports/luna-sysmgr/pull/21/files Oct 27 19:41:55 ShowNotificationsAtTop is used for showing notifications 3.x style at some point in future when we implement it in LNC Oct 27 19:42:22 Rest is merely cosmetics ;) Oct 27 19:43:00 I.e. using our versions of apps instead of com.palm ones which don't exist and unify the settings across devices so each device has the same settings included in the conf at least Oct 27 19:55:46 Tofe: I'll leave camera in there for now so we don't forget about it. we don't have a replacement yet. Oct 27 19:56:10 ok Oct 27 19:56:19 Tofe: OK PR updated Oct 27 19:58:58 Well, background isn't transparent, but I think it's just because there's a little signal missing somewhere Oct 27 20:02:00 Andolamin: See this PR for the changes you need to add to your .conf: https://github.com/webOS-ports/luna-sysmgr/pull/21/files Oct 27 20:03:35 Herrie|Laptop: Awesome, thanks Oct 27 20:04:03 If you add them you can PR your conf against our branch, so we already have that for integration in future ;) Oct 27 20:04:22 Herrie|Laptop: I think we're good to go for merging qtwebengine Oct 27 20:04:54 Same with luna-next-cardshell changes. I'll take care of the implementation further then with reading the values from .conf and Tweaks options Oct 27 20:04:55 I Oct 27 20:05:02 've done that before, so know how to do that Oct 27 20:06:13 Herrie|Laptop: tadaa https://github.com/qtproject/qtwebengine/commits/5.5 Oct 27 20:06:43 TofE: LOL Oct 27 20:06:54 Needed change but merged 1:1 :P ? Oct 27 20:07:23 Tofe: Ok got PR for qtwebengine, luna-webappmanager, luna-service2 Oct 27 20:07:29 Nothing for luna-qml-launcher? Oct 27 20:07:48 Herrie|Laptop: yeah it's exactly my commit on our fork. We'll rebase sometime later, when we'll be through with the merge Oct 27 20:08:17 Herrie|Laptop: no, that one is already migrated Oct 27 20:08:36 I don't think I have other modifications, let me double-check Oct 27 20:09:40 no, seems good Oct 27 20:11:08 Tofe: OK all merged, let me update recipes and kick off some builds :D Oct 27 20:11:16 Let's live on the edge :P Oct 27 20:11:47 for luna-webappmanager, you'll need to replace qtwebkit with qtwebengine, same for -qmlplugins Oct 27 20:14:45 I've also PR'ed a change I've wanted for a long time :) Oct 27 20:17:44 Herrie|Laptop: one thing we could fix also before triggering the build, in the qtwebengine recipe, is the two qa warnings about missing depends on pmloglib and luna-service2 Oct 27 20:18:01 Tofe: hell why not ;0 Oct 27 20:18:04 ;) Oct 27 20:18:57 And that'll be all from my side :) Oct 27 20:18:58 Big list of changes going in today Oct 27 20:19:24 Yeah, today is byebye webkit Oct 27 20:19:26 Andolamin: Not that big, just critical stuff... I closed a handful of old Maguro bugs that seems to have solved themselves Oct 27 20:20:38 What does QtWebEngine do layout with? Oct 27 20:20:53 Andolamin: What do you mean? Oct 27 20:20:59 Blink, I presume? Oct 27 20:21:07 QtWebEngine uses chromium code base Oct 27 20:21:12 so yes, blink Oct 27 20:21:20 Ah, nice Oct 27 20:21:48 Andolamin: Our browser html5test.com score went from 390 to 492/550 when we switched :P Oct 27 20:22:10 I *think* I've got node 4.2.1 working in my builds. Build is just about done, then I'll see if anything broke. Oct 27 20:22:37 Andolamin: According to JaMa 3 modules needed fixing Oct 27 20:23:02 node-sqlite3, node-taglib and node-dbus Oct 27 20:23:44 node-sqlite is used in various places I think. node-taglib for our media-indexer I guess. Not sure where we use node-dbus but sure in quite some places too Oct 27 20:24:11 Ah seems keymanager uses node-sqlite3 Oct 27 20:24:19 Yup. I *think* they'll build fine now, but we'll see shortly Oct 27 20:24:40 What kind of benefit is there with such upgrade? Oct 27 20:24:44 Andolamin: That would be nice :D Oct 27 20:24:57 Fortunately work is doing a hackathon right now and Node 4.2.x is pretty critical for what I want to do, so I get ~48 hours paid LG time to work on LuneOS Oct 27 20:24:58 Tofe: ES6 support out of the box and latest greatest NodeJS;) Oct 27 20:25:14 Herrie|Laptop: ok, looks good :) Oct 27 20:25:15 Andolamin: NICE :D Oct 27 20:25:15 Tofe: SIGNIFICANTLY improved V8 performance Oct 27 20:25:43 Herrie|Laptop: Of course, I intend to use some of that for sleep ;) Oct 27 20:26:04 Ah, V8 improvement is great, now more than ever ;p Oct 27 20:26:27 I remember DougReeder was complaining about NodeJS performance Oct 27 20:26:29 I've seen 90-95% performance improvement in places with newer node versions Oct 27 20:27:12 Tofe: What you feel like some QML or some C++ :P ? Got a few small ones of both :P Oct 27 20:27:46 Herrie|Laptop: I'm more in a QML mood right now Oct 27 20:28:04 Tofe: OK... Can you get phone app to work better :P Oct 27 20:28:09 hehe Oct 27 20:28:11 I'll tell you the problems ;) Oct 27 20:28:32 Andolamin: will you migrate also our internal JSON optimalization to newer nodejs? Oct 27 20:28:44 Tofe: Let me push to a branch :P Oct 27 20:29:29 JaMa: libpbnjson? Oct 27 20:32:02 Tofe: build running Oct 27 20:32:09 *\o/* Oct 27 20:32:12 We can fix QA issues if this is OK Oct 27 20:32:29 It's not that critical for build Oct 27 20:32:34 Lets first see how this works out Oct 27 20:32:40 yeah Oct 27 20:32:52 Tofe: https://github.com/herrie82/org.webosports.app.phone/ Oct 27 20:33:44 I did initial migration to Units.gu. I need to have a look at UI in general, not happy with it, but all pages are there. I'll work on layout later Oct 27 20:34:47 little numbers :p Oct 27 20:35:37 Biggest problem I have now is the following: 1. When I answer an incoming call, it doesn't open the phone app at all. The IncomingCallAlert (or Page) don't remember, pops up, answers the call and the phone app disappears. Oct 27 20:35:45 It's there somewhere, just not visible Oct 27 20:36:38 mmh Oct 27 20:38:01 Also when in DialerPage.qml and I press the dial button, it does call, however it doesn't show ActiveCallPage.qml Oct 27 20:38:30 Actually when accepting incoming call it should open the phone app at the same ActiveCallPage.qml Oct 27 20:39:01 I know this used to work OK a while back, but then morphis started to tamper with things halfway in the voicecall migration I think and left it there broken :P Oct 27 20:39:36 Andolamin: http://issues.webos-ports.org/issues/699 Oct 27 20:39:41 That's the issue we had Oct 27 20:40:51 Andolamin: no patches we have for nodejs Oct 27 20:40:56 so... where did I put this phone number again... Oct 27 20:41:47 Tofe I made a contact on my Veer called HerrieTest with all my test sim numbers :P Oct 27 20:41:57 :) Oct 27 20:42:44 Sorted my sims in the weekend because I had like half a dozen :p Oct 27 20:42:51 Now have 3 that work and have some balance Oct 27 20:45:24 JaMa: I don't see those patches anywhere, but if there's reason to believe they're still necessary in nodejs 4.2.x I'll definitely look at migrating them Oct 27 20:45:25 I have no idea what's the status of mine Oct 27 20:48:55 Tofe: outgoing calls work on N4 ;) Oct 27 20:49:06 So when you hvae a sim in it, you can just call your other phone :P Oct 27 20:49:16 And you'll have the number :P Oct 27 20:50:49 mmh I don't seem to be able to do any call, I think my number has been revoked Oct 27 20:51:51 Anyway, I wanted first to do a clean build from latest testing Oct 27 20:53:28 Tofe: We have free sims here with Lebara, Lycamobile etc Oct 27 20:53:33 Sure you have similar in France ;) Oct 27 20:53:45 Add EUR 5 and you get EUR 10 credit etc :P Oct 27 20:53:57 yeah, I had a lycamobile one lately Oct 27 21:03:10 JaMa: You sure this is correct for testing: meta-qt5 = "jethro:89038bffd224a0d43aa8627472374503b3023f61" Oct 27 21:03:25 Andolamin: there are 16 patches in ./meta-webos/recipes-upstreamable/nodejs/nodejs Oct 27 21:03:35 Herrie|Laptop: why not? Oct 27 21:03:51 Dunno? Just asking Oct 27 21:04:00 yes, I'm sure :) Oct 27 21:04:19 I thought you said earlier today you were working on jethro, so surprised to see that in testing already? Oct 27 21:04:26 I thought you were doing that in unstable? Oct 27 21:04:28 it's latest in jethro branch Oct 27 21:04:37 we were already using master branch for meta-qt5 Oct 27 21:04:42 instead of fido, to get 5.5* Oct 27 21:04:59 Ah ok Oct 27 21:05:02 now jethro will keep 5.5 and master will switch to 5.6 when I finish the recipes Oct 27 21:05:06 fido didn't have 5.5 right? Oct 27 21:05:15 yes, fido had 5.4* Oct 27 21:05:33 Ah OK then it makes sense :D Oct 27 21:05:37 and we were using meta-qt5/fido from meta-webos-ports/dizzy builds :) Oct 27 21:05:47 so meta-qt5 is often shifted by one release Oct 27 21:06:05 I think we're happy with 5.6 in general, just Tofe needs to do a little work I guess to migrate some stuff Oct 27 21:06:11 We now backported a few things Oct 27 21:06:29 you mean 5.5, right? Oct 27 21:06:49 5.6 recipes are only WIP for alpha release which don't build yet (I'm fixing qtbase atm) Oct 27 21:07:10 current testing/fido builds are using 5.5.1+ Oct 27 21:09:00 JaMa: I mean when you're ready with 5.6 I think we're OK to migrate, just need to see what of our custom code can be 1:1 and what needs mods Oct 27 21:09:16 Tofe currently backported a few features from 5.6 to 5.5.1 for our webappmanager Oct 27 21:09:34 Herrie|Laptop: no rush, no rush :) 5.6 will break everything again :) Oct 27 21:11:00 Tofe: Well I'm sure 5.5.1-> 5.6 will be a walk in the park compared to qtwebkit->qtwebengine ;) Oct 27 21:12:23 probably Oct 27 21:12:48 Let's say a walk in a Tivoli park then Oct 27 21:18:08 Tofe :D Oct 27 21:33:23 Tofe: https://github.com/webOS-ports/luna-sysmgr-common/pull/8 Oct 27 21:34:11 Ah wait I forgot something :P Oct 27 21:35:16 Tofe: No it was already there for ShowNotificationsAtTop Oct 27 21:35:20 So PR is OK Oct 27 21:45:00 Tofe and: https://github.com/webOS-ports/luna-next/pull/112 Oct 27 21:45:10 That should allow us now to play in LNC with it I guess? Oct 28 00:29:26 OK - nodejs 4.2.1 will take more work than I was hoping for. Got node-sqlite3, node-dbus, node-taglib and node-gyp-native building fine, but now I'm running into V8 incompatibilities with nodejs-module-webos-sysbus and nodejs-module-webos-dynaload. Those appear to need source updates. Oct 28 02:52:27 jama, sorry, didn’t see your message until now. I haven’t build any of those, sorry. **** ENDING LOGGING AT Wed Oct 28 02:59:58 2015