**** BEGIN LOGGING AT Tue Mar 08 02:59:57 2022 Mar 08 08:11:24 Tofe: Could it be CORS is somehow causing issues in the initialization? I.e. it doesn't want to load certain things? Mar 08 08:21:56 Herrie: I don't know at all for the moment Mar 08 08:22:43 or maybe Enyo doesn't detect PalmSystem (or the webOS context) and skips a big part of the init Mar 08 08:54:44 Tofe: wam_demo doesn't ring a bell Mar 08 08:56:52 Tofe: https://github.com/webOS-ports/meta-webos-ports/pull/500 should probably target honister branch now instead of herrie/honister-wam-extended which was merged to honister yesterday Mar 08 09:00:14 I've rebased it now, please double check and LGTM from me Mar 08 09:01:12 Oh, I didn't realize it was merged to honister Mar 08 09:02:28 that's what I was rebasing and force-pushing yesterday :) Mar 08 09:21:08 JaMa: So honister now has all from the wam-extended branch? Mar 08 09:21:33 Not really sure that is what was intended yet, but well at some point we'd merge it anyway I guess Mar 08 09:22:03 HerrieTP: I didn't merge it, it was already there I assumed it was merged by you Mar 08 09:23:24 JaMa: Well I probably messed something up while rebasing the wam-extended then Mar 08 09:23:41 Anyway we're in decent shape, we just need to fine tune quite a few bits still Mar 08 09:24:45 then we should merge Tofee's PR and I'll remove meta-python2 layer as well Mar 08 09:30:36 done and fixes for qt 5.15.3 merged as well (should be backwards compatible with 5.15.2) Mar 08 09:34:27 Tofe: Your thoughts? Do you expect issues with the migration to WAM/LSM that are not fixable? Mar 08 18:23:39 HerrieTP: well, my biggest concern is about the QML apps that are blurry Mar 08 18:24:39 but it's well identified, and fixable; at worst we can inherit WebOSCoreCompositor and do the client surface resize there, like we did for luna-next Mar 08 19:12:27 Tofe: Well there's app menu, system menu and other things, but they don't need to be huge Mar 08 19:58:27 HerrieTP: this might come almost for free if Enyo is working again Mar 08 20:02:22 Herrie: about enyo, the error I see for calendar is: "Uncaught TypeError: enyoApp.watch is not a function" at initializeCalendarView (calendar.js:63) Mar 08 20:03:03 enyoApp being "enyo.application" in this context Mar 08 20:04:03 this is an empty object, when looking with the console Mar 08 20:04:45 but for "enyo Mail Launcher" app, it's all fine, and enyo.application looks ok Mar 08 21:11:24 when you inspect it in Chrome, are there any 404s or CORS errors when that app launches? Mar 08 21:14:10 nope, not this time Mar 08 21:14:28 also, I'm currently just trying with clock app which is easier to debug Mar 08 21:14:44 and we don't seem to go into the "startup" callback Mar 08 21:15:31 https://github.com/webOS-ports/core-apps/blob/webOS-ports/master/com.palm.app.clock/launch/clockapp.js#L55 here Mar 08 21:22:26 oh, sorry, looks like that one is only called when playing the app on desktop or so Mar 08 21:31:50 mmmh actually not sure what happens between index.html and main.html Mar 08 21:37:09 main.html looks like what you'd expect to find in a webOS app -- renderInto kicks off the app Mar 08 21:38:20 but the appinfo.json says it should start index.html Mar 08 21:45:02 and the readme says: index.html - This is the main html file which creates the main JS object for the App. Mar 08 21:52:05 Well normally I'd expect index.html really Mar 08 21:52:29 I recall adding some index-desktop.html in the past for desktop debugging Mar 08 21:55:08 so if startup isn't getting hit, then its probably not getting loaded by the framework Mar 08 21:55:20 the scripts the framework loads are specified by the depends file: https://github.com/webOS-ports/core-apps/blob/webOS-ports/master/com.palm.app.clock/depends.js Mar 08 21:57:49 the scripts with the startup function is launch/clockapp.js Mar 08 21:58:36 can you put a console.log at the top of that file to see if the file is getting loaded at all? **** ENDING LOGGING AT Wed Mar 09 02:59:56 2022