**** BEGIN LOGGING AT Mon Sep 08 02:59:58 2014 Sep 08 05:58:11 morning Sep 08 06:30:54 morning Sep 08 06:31:31 browser PR is taking shape, expect it to be completed later today, just some code cleanup + layout tweaking to do for N4 ;) Sep 08 08:28:56 morphis: is it possible to check hardware type here: https://github.com/webOS-ports/sleepd/blob/webOS-ports/master/src/pwrevents/machine.c#l121 ? This will reduce flood rate(577) from every 0.5s to 300s. The problem is sleepd written in C, while LunaSettings in C++. Do you think it's good to rewrite MachineGetName to get network name and use it? Sep 08 08:34:19 nizovn: that exactly do you want to change with checking for the hardware type in there? Sep 08 08:34:56 s/that/what/ Sep 08 08:35:17 morphis: MachineCanSleep can return false for emulator or desktop Sep 08 08:36:10 nizovn: but imho we should never come into that case as https://github.com/openwebos/sleepd/blob/master/src/pwrevents/suspend.c#L290 Sep 08 08:36:19 on the emulator the display should be always on Sep 08 08:45:24 ok, but for some reason emulator reaches SuspendRequest. will see why. Sep 08 08:50:22 seems the problem is that IsDisplayOn is different in openwebos and webos-ports. Sep 08 08:56:48 yeah Sep 08 09:03:22 nizovn: if we disable display timeouts for the emulator (like you did with your PR) it should just work and sleepd should never try to suspend the system Sep 08 09:04:30 morphis: it goes into SuspendRequest state and floods ls-monitor. Sep 08 09:34:29 maybe problem somewhere in init, because after turn off, turn on screen, it stops flooding. Sep 08 09:45:18 morning Sep 08 10:14:55 nizovn: on emulator? Sep 08 10:15:04 yes Sep 08 10:15:22 as I said, the screen should not go off on the emulator Sep 08 10:16:13 nizovn: so I think doing the check you added in your PR should be enough to get this fixed Sep 08 10:17:26 seems screen not goes to off, but sleepd goes into suspendrequest state once after boot.(i've tested with PR changes) Sep 08 10:17:49 ok Sep 08 11:03:02 ok, it gets displayInactive event and decide that screen is off. be back after 2.5 hours. Sep 08 17:15:04 not sure what you are talking about, but currently emulator is still unusable for me. Right after boot luna-next seems to crash, or at least does not react to mouse input at all. After a luna-next restart (which solves the issue on "stable" emulator), the lock screen is displayed, reacts to mouse input but can not be unlocked. Sep 08 17:16:33 ls-monitor shows call to control/setLockStatus {"status":"unlock"} goes through, but lockscreen stays. Hm. strange. Sep 08 17:16:57 and now it's in "suspend flood" again. ;) Sep 08 17:20:19 Tofe: ping Sep 08 17:32:12 Garfonso: you are right, this is not luna-next crash, but screen turns off(it reacts on mouse however). You can temporary solve this by turning it on by luna-send. Fix is almost ready. Sep 08 17:43:53 what is the luna-send cmd to turn it on? Sep 08 17:57:49 Garfonso: luna-send -n 1 luna://com.palm.display/control/setState "{\"state\":\"on\"}" If not works, then turn off it before. Sep 08 18:19:34 nizovn: I have two other changes regarding display management Sep 08 18:20:46 ? Sep 08 18:22:13 nizovn: https://github.com/webOS-ports/luna-appmanager/pull/3 Sep 08 18:23:30 morphis: for now i think to enable DNAST mode for emulator. What does it mean? Sep 08 18:23:35 :) Sep 08 18:24:19 nizovn: it's a blocker for the display Sep 08 18:24:33 not sure if it was used in legacy for the same problem we try to fix here Sep 08 18:25:35 nizovn: and https://github.com/webOS-ports/luna-sysmgr/pull/9 Sep 08 18:25:40 morphis: seems it was used, but emulator was called "desktop" in those times Sep 08 18:26:06 really? Sep 08 18:26:24 nizovn: emulator and desktop should be different even on legacy Sep 08 18:26:50 nizovn: https://github.com/openwebos/luna-sysmgr/blob/master/Src/base/DisplayManager.cpp#L705 Sep 08 18:28:53 nizovn: putting that back in might fix the problem we have Sep 08 18:28:59 if you use the settings approach Sep 08 18:29:10 we're using the same when the first use app is running Sep 08 18:29:14 works quite fine Sep 08 18:29:17 display never goes off Sep 08 18:29:58 morphis: there is a problem while i tested it. lunasettings returns Device there for some reason. Sep 08 18:30:11 that can be fixed Sep 08 18:30:53 nizovn: https://github.com/webOS-ports/luna-sysmgr-common/blob/webOS-ports/master/Src/base/settings/Settings.cpp#L608 Sep 08 18:30:56 is where it is read Sep 08 18:31:39 nizovn: that installs the config https://github.com/webOS-ports/meta-webos-ports/blob/daisy/recipes-webos/luna-sysmgr-conf/luna-sysmgr-conf.bb Sep 08 18:32:02 nizovn: which is here for emulator: https://github.com/webOS-ports/luna-sysmgr/blob/webOS-ports/master/conf/luna-qemux86.conf Sep 08 18:32:15 there might be something wrong with this if it doesn't work Sep 08 18:32:39 nizovn: you can add -t -c to the cmdline for LunaSysMgr in /lib/systemd/system/LunaSysMgr.service Sep 08 18:32:44 that should give you more verbose output Sep 08 18:32:52 and should also mention the hardware type it reads Sep 08 18:33:09 btw there is emulator line in luna-platform.conf Sep 08 18:34:18 nizovn: on the emulator rootfs? Sep 08 18:34:23 yes Sep 08 18:34:49 hm Sep 08 18:34:59 then something with the parsing is wrong when it returns device for you at the other end Sep 08 18:36:16 nizovn: have to drop off, can you also look at my two PRs? Sep 08 18:36:40 nizovn: should fix #575 Sep 08 18:39:30 morphis: i'll test them too. not sure they fixing 575, seems more 577 Sep 08 18:43:49 hm.. hope #9 will solve 575 on mako and tenderloin Sep 08 18:47:58 hey morphis, are LuneOS install instructions up on the wiki? Sep 08 18:49:29 nevermind. i found it. Sep 08 18:49:30 :) Sep 08 19:41:15 Herrie: pong Sep 08 19:47:20 uhm.. regression: Parameters are not handed to Custom UI anymore. :( Sep 08 19:47:54 like, Launch Parameters? Sep 08 19:48:16 Tofe: here from laptop Sep 08 19:48:59 GodGinrai: right Sep 08 19:49:46 Herrie|Laptop: well, pong|laptop then :) Sep 08 19:49:57 k Sep 08 19:50:07 LOL Sep 08 19:50:18 Just wondering how I could run some queries in QML while loading the UI Sep 08 19:50:47 I need to pull some data right at the beginning. Now have some onClick when I actually need it but would like to load it when UI is build Sep 08 19:51:08 Herrie: Component.onCompleted is what you need Sep 08 19:52:07 OK will try that :) Sep 08 19:52:09 it's available on all types of QML components; just be careful: if you have A that contains B, B will be completed before A is fully completed. Sep 08 19:52:29 Usually it's used on the root component of the module you want to handle Sep 08 19:53:07 There are plenty of examples in the cardshell, if you need some. Sep 08 19:53:49 OK Sep 08 19:54:08 Also, be careful with async requests; but that's nothing new compared to Enyo Sep 08 19:54:27 I guess I might have some of those ;) Sep 08 19:54:36 * Herrie|Laptop doesn't know Enyo that well :P Sep 08 19:55:02 * Tofe doesn't know Enyo Sep 08 19:55:14 (boooo) Sep 08 19:55:59 So what should I take care of with the async ones? Sep 08 19:56:09 I need to have a success and failure call in there? Sep 08 19:56:24 just that when the UI is ready, you may not yet have your underlying data ready Sep 08 19:59:14 OK yeah have that here it seems ;) Sep 08 19:59:21 But well that's a bug to fix for later :P Sep 08 20:01:31 I guess that causes my "Unable to assign [undefined] to QString"? Any quick way around this? Sep 08 20:03:19 "undefined" looks like a name resolution error to me Sep 08 20:03:27 I'm calling a function that does a luna-call to DB8 and then populates the values Sep 08 20:03:38 Since it's async it's probably not done yet ;) Sep 08 20:03:47 mmh Sep 08 20:03:55 do you have already the code on gh ? Sep 08 20:04:22 Let me push that now :P Sep 08 20:09:50 https://github.com/Herrie82/org.webosports.app.browser/commit/cc6ad910f3f3653804eb83d52418d20478acc0d4 Sep 08 20:10:06 Need to add some stub stuff sometime ;) Sep 08 20:10:23 Not very useful to test in QT Creator like this without mock backend DB8 stuff Sep 08 20:11:50 I'm sure a lot of things could be done more optimal but well :p Sep 08 20:12:14 It works more or less for most things :P Sep 08 20:20:08 Tofe: Implemented some of your suggestions (URL suggestions rows lower, full screen on N4, made panel for downloads, history + bookmarks fullscreen on N4 too). It could use some nice transformation effect as well I guess but well :p Sep 08 20:20:32 Herrie|Laptop: where would that error be, btw ? Sep 08 20:23:37 main.qml line 440: json: getJSONData() Sep 08 20:24:09 and NavigationBar.qml line 769: json: getURLHistory() Sep 08 20:29:03 well, there's an easy way Sep 08 20:29:44 First, declare my*Data as string, not variant, because you know it will be a string Sep 08 20:29:53 (isn't it ?) Sep 08 20:30:29 Well it's a JSON ;) Sep 08 20:30:31 assign a default value, i.e. property string myBookMarkData: '{}' Sep 08 20:30:33 So i thought variant? Sep 08 20:30:39 Or can do string there? Sep 08 20:31:13 it looks like you assign the payload to it, but without doing a JSON.parse, so you'll get a string, not an object Sep 08 20:32:12 I do a parse ;) Sep 08 20:32:23 var defbrows = JSON.parse(message.payload) Sep 08 20:32:46 Ah that's for the other ;) Sep 08 20:32:51 yes Sep 08 20:34:23 for urlHistory*Data, same remarks Sep 08 20:35:43 I should JSON.parse them I guess? Sep 08 20:36:05 depends on the "json" property of the JSONListModel, let me see Sep 08 20:36:44 string it is Sep 08 20:37:03 so no parse Sep 08 20:38:07 variant properties should be avoided when possible, because it can't be optimized and slows down a bit the app Sep 08 20:39:45 ok Sep 08 20:39:56 so all strings and initialize with '{}' Sep 08 20:40:03 yes Sep 08 20:41:22 That works Sep 08 20:41:27 :) Sep 08 20:42:39 also, your two qml files begin to be pretty big; maybe at some point in time you'll want to refactor them a bit -- but that can wait, as long as you don't feel the need for that Sep 08 20:43:15 Yeah saw that as well Sep 08 20:44:30 Need to see how :P QML n00b Sep 08 20:45:57 oh, that's pretty easy: you take a set of consistent lines (for example, a delegate definition), cut&paste in another file; then, you see what data you are missing in the standalone delegate, and put that as properties of the delegate, which you feed in from you previous big file. Sep 08 20:57:10 Ah ok Sep 08 21:09:09 morphis: PR is in for the browser Sep 08 21:10:03 P.s. Should the messaging app be called org.webosports.app.messaging instead of org.webosports.messaging in order to be compliant with our naming convention for the other apps? Sep 08 21:42:06 Herrie: merged! Sep 08 21:43:29 Tofe: thnx fixed the few things you mentioned Sep 08 21:43:39 Will update the readme with what's done and what needs doing still Sep 08 21:43:49 But it's an improvement so far for sure Sep 08 21:43:56 Need some help with that FocusScope I guess :P Sep 08 21:44:02 Tried but failed :P **** ENDING LOGGING AT Tue Sep 09 02:59:59 2014