**** BEGIN LOGGING AT Thu May 14 02:59:58 2015 May 14 03:08:50 Huh, tweaked the Dashboard test to work on the Pre3, and it works better on the N4. Both have high-DPI screens. May 14 03:10:32 Still only displays half the dashboard on the N4, though. May 14 05:31:17 DougReeder: ping May 14 05:34:45 For the dashboard you need the specify the height in GridUnits, see: https://bpaste.net/show/07c2901338bc May 14 05:35:16 {metrics: "units"}, 6) May 14 05:37:37 See also https://github.com/webOS-ports/luna-webappmanager/blob/a662439d5f157fb953bee6f0911a268e4d3e573c/src/webapplication.cpp#L211 and further for it's implementation May 14 05:48:45 The idea is that this will give a resolution independant way to sort this May 14 05:49:24 So with the same amount of units, it should take more or less the same screen space on different devices May 14 05:49:50 For me it didn't work 100% with my luna-systemui tests so it could be it needs some tweaks here or there still May 14 05:50:41 GridUnit is set to 18 for N4 and 10 for TP May 14 05:50:55 See: https://github.com/webOS-ports/luna-sysmgr/blob/webOS-ports/master/conf/luna-mako.conf#L35 May 14 05:58:17 So instead of 320px height on TP you would use 320/10 = 32 GridUnits May 14 10:46:13 Tofe: if TabletUI=false is set on TP that is wrong May 14 10:46:15 needs to be fixed May 14 11:27:49 morphis: ok, I'll try to make a PR when I have some time May 14 11:28:24 morphis: https://github.com/webOS-ports/luna-sysmgr/blob/webOS-ports/master/conf/luna-tenderloin.conf#L25 May 14 13:16:36 Tofe: https://github.com/webOS-ports/luna-sysmgr/pull/18 May 14 13:43:36 Herrie, enyo.windows is not defined. May 14 13:49:22 Is that an Enyo 1 call? May 14 14:52:09 If I’m reading https://github.com/webOS-ports/luna-webappmanager/blob/a662439d5f157fb953bee6f0911a268e4d3e573c/src/webapplication.cpp#L211 correctly, the third argument to window.open should be something like this: 'height=6,attributes={"window":"dashboard","metrics":"units"}' May 14 15:02:59 If I undersand correctly, apps putting up a dashboard will call window.open() [perhaps via a convenience function like openPopup]. The third argument would normally be ‘attributes={"window":"dashboard”}’. And that should produce a standard height dashboard. IIRC, that’s 52px on 1x screens. May 14 15:12:13 Actually, for Enyo 1 the convenience function would be openDashboard(). May 14 15:14:05 …which calls openWindow, which calls this.agent.open(), which I can’t find the source for, but has an argument list suspiciously similar to window.open. May 14 15:20:15 Is there an enyo 1 app that just opens a dashboard, that I could trace? May 14 15:21:27 PopupCalc opens a system popup at the same time, the dashboard doesn’t open, and the log just shows the warning “WARNING: Executing pending window params, but no params list found. “ May 14 15:22:56 I could probably assemble http://webos101.com/Enyo_Dashboard_App later. May 14 15:47:46 DougReeder: It's Enyo 1 indeed. It's used for the battery alerts in luna-systemui for example. May 14 15:48:31 Clearly, it’s possible for functional dashboards to be be created. May 14 15:49:15 DougReeder: Yeah could be you need to tweak your syntax a bit. Also able to get dashboards from messaging app by the way May 14 15:49:48 I saw a few sometimes :) May 14 15:50:06 Yeah, we’ll want a dashboard when new messages arrive. Not sure how to simpulate incoming messages. May 14 15:50:37 Maybe a luna-send command to the chatthreader, with the correct parameters. May 14 15:50:39 Anyway on the way now to some friends for a bbq. The systemui code is in our GitHub too might give you some clues. May 14 15:50:59 DougReeder: db8 watch should be enough? May 14 15:52:06 Hmm, dashboard would be mainly for when messaging app isn’t open. May 14 15:52:35 So, chatthreader would launch app, with params to just put up the dashboard. May 14 15:56:16 Ah in legacy we had nowindow for this... May 14 15:59:06 Don’t we allow nowindow again? May 14 16:00:07 The rule under webOS is that when the last card, dashboard, or system popup is closed, the app is killed. May 14 16:09:23 I think we do for (some?) Enyo 1 apps but not sure how that would work for Enyo 2? May 14 16:10:07 I know policy changed, we disabled it in the past due to memory usage but it was enabled again some time ago, not sure if it's for all though... May 14 16:10:14 morphis can confirm I'm sure May 14 17:41:18 Okay, calling the Enyo 1 openDashboard() uses some other convenience functions that eventually call window.open() with a third argument of ‘attributes={"window":"dashboard”}’ **** ENDING LOGGING AT Fri May 15 02:59:58 2015