**** BEGIN LOGGING AT Wed Mar 09 02:59:56 2022 Mar 09 07:20:06 codoepoet80: that js file is actually executed, I can put a breakpoint at the file line of the file Mar 09 07:20:48 currently, my guess is that there is a mechanism in Enyo 1.0 that makes it load main.html after index.html Mar 09 10:26:17 Morning! Mar 09 10:26:46 Tofe: I'm also not really sure how the clockApp works, it was broken in Open webOS, I fixed it a little bit so it would run on Desktop, but it might not be the most reliable app to test with somehow Mar 09 10:27:06 Morning! Mar 09 10:27:06 THere were others that were broken in Open webOS, I tried to do some minimal fixes to get them running on desktop for most Mar 09 10:27:29 Herrie: well, the error is currently quite similar between calendar and clock Mar 09 10:27:37 i.e. enyo.application.prefs is empty Mar 09 10:28:32 Tofe: Well I think we even had that on our luna-webappmanager Mar 09 10:28:38 It's the cookies that don't get loaded Mar 09 10:28:41 And saved Mar 09 10:28:58 That's what codepoet mentioned with App Museum 2 Mar 09 10:29:43 It every time shows the startup dialog where it should only show it once, save a cookie and next time don't show it Mar 09 10:29:49 Or at least it might be related somehow Mar 09 10:30:18 mmh interesting Mar 09 10:32:00 I suspect that's this line: https://github.com/codepoet80/webos-catalog-frontend/blob/main/app/museumApp.js#L263 Mar 09 10:32:10 So you might want to test the App Museum see what it does Mar 09 10:32:26 I remember with our luna-webappmanager it would show the popup every single time Mar 09 10:32:36 Might be a bit easier to debug vs all the framework stuff Mar 09 10:33:51 note that we mostly have no issue with Enyo2 apps Mar 09 10:36:15 oh, but app museum is Enyo 1, I didn't realize that... ok, then, yes, it's a good idea to test it Mar 09 11:10:53 Tofe: Not sure it will help, but it might load less frameworks etc, so might be easier to debug somehow (or not), but worth to try Mar 09 11:11:28 Tofe: This was the issue codepoet raised for it: https://github.com/webOS-ports/luneos-testing/issues/14 **** ENDING LOGGING AT Wed Mar 09 16:29:45 2022 **** BEGIN LOGGING AT Wed Mar 09 16:32:16 2022 Mar 09 18:02:27 Herrie: AppMuseum fails early on, because PalmSystem.deviceInfo returns "" which isn't a JSON string Mar 09 19:04:31 fixing deviceInfo made AppMuseum work Mar 09 19:05:09 but clock is still the same, unfortunately Mar 09 20:10:23 Tofe: Well it was worth a try Mar 09 20:13:35 HerrieTP_: and the fix was needed anyway Mar 09 20:15:02 JaMa, Herrie: I rebased my honister-wam-extended on top of honister, but I still get these commits: https://github.com/webOS-ports/meta-webos-ports/compare/honister...Tofee:tofe/honister-wam-rebased?expand=1 Mar 09 20:15:12 Tofe: Well that fixed the cookie issue? Mar 09 20:15:13 the deviceInfo one is normal, but the other ones ? Mar 09 20:15:47 HerrieTP_: ah, I don't know :) The error was completely at the startup of the app Mar 09 20:15:58 Ah OK Mar 09 20:16:23 Weird it worked OK with luna-webappmgr before Mar 09 20:17:01 I don't see any cookie for the app, though, so I guess it failed Mar 09 20:17:27 Cookie issue is solved when the popup window on app start doesn't appear on 2nd, 3rd etc launches of the app Mar 09 20:17:48 The cookies are in dom/dom.js it seems Mar 09 20:17:57 Yes, I now understand what it was about Mar 09 20:18:14 Could be the way Chrome handles the storage in the backend was changed so it no longer works Mar 09 20:18:23 for luna-webappmgr the deviceInfo thing was provided by our homemade Qt extension Mar 09 20:18:48 I don't think it changed it the last 15 years Mar 09 20:18:57 in* **** ENDING LOGGING AT Thu Mar 10 02:59:57 2022