**** BEGIN LOGGING AT Wed Dec 30 02:59:59 2015 Dec 30 07:34:40 morning Dec 30 07:34:42 Tofe: ping Dec 30 07:56:39 morning Dec 30 08:03:42 nizovn: morning Dec 30 08:03:50 I got a reticle on N4 now :P Dec 30 08:05:18 Just 2 minor issues while trying to use the 4* resolution image. I would expect I'd need to do Units.gu(0.1) / 4 = Units.gu(0.025) but that doesn't work. Units.gu(0.1) / 4 works though. Another thing is that C++ seems to expect an absolute path for imagePath so /usr/palm etc Dec 30 08:05:32 However when I use Qt.resolvedUrl("../images/penindicator-ripple.png") it gets a file:// prefix Dec 30 08:05:32 morning Dec 30 08:06:06 Herrie: pong Dec 30 08:06:07 Which C++ doesn't like. I can simply replace that in JS with .replace("file://","") but not sure that's proper way to do it? Dec 30 08:06:44 Tofe: Another thing is that C++ seems to expect an absolute path for imagePath so /usr/palm/.. etc, however when I use Qt.resolvedUrl("../images/penindicator-ripple.png") in QML it gets a file:// prefix Dec 30 08:07:06 Tofe: Which C++ doesn't like. I can simply replace that in JS with .replace("file://","") but not sure that's proper way to do it? Dec 30 08:09:03 mmh Dec 30 08:10:34 Herrie: that's what i was talking about :P Units.gu(x/10)<>Units.gu(x)/10 because of rounding, and can return 0 Dec 30 08:10:57 nizovn: Ah, strange it does rounding :P It shouldn't IMHO :P Dec 30 08:11:12 Herrie: Qt.resolveUrl gives you a "url" type; therefore it should be handled with QUrl on C++ side Dec 30 08:11:25 it makes sense when use it for pixel size Dec 30 08:12:30 Herrie: then, you have QUrl::toLocalFile to get the "C++" usual path Dec 30 08:12:39 Tofe: OK Dec 30 08:12:45 nizovn: ^ can you do that on C++ side? Dec 30 08:13:22 nizovn: Since this is an exceptional case I guess we can just suffice with the Units.gu(0.1) / 4 ;) Dec 30 08:13:48 I have seen maybe 1 other case so far where we ran into issues. So it doesn't warrant to write something for it imho Dec 30 08:14:20 I.e. optional noRounding or something might be an idea but seeing it's rare I'm OK with the / 4 for now ;) Dec 30 08:14:23 Tofe: ^ Dec 30 08:21:03 Well, if we want a ratio (i.e. a real number, not an integer as for a pixel), it would indeed make sense to use Units.gridUnit Dec 30 08:22:19 (I sense nizovn wanting to say "hey, that's what I wrote back then!") Dec 30 08:22:19 Tofe: Yeah problem is that when the Units.gu value gets too small it doesn't work ;) Dec 30 08:22:36 Because it rounds it down to 0 ;) Dec 30 08:23:17 Tofe: btw i noticed on emulator that webappmanager stops eating cpu after first opening of justtype Dec 30 08:23:22 Herrie: if what you want is a length in pixel, what is the issue? Should it be 1 ? Dec 30 08:23:51 nizovn: oh, that's a great remark, that'll help thanks Dec 30 08:25:06 What we do now is we have the original image at 66*67 px which should scale to 66*67 * 1.8 (GridUnits of N4 vs TP (18 vs 10) so we say the minimumScale is Units.gu(0.1), so basically 1. However is we use the 4* resolution image we should put Units.gu(0.025) which doesn't work due to the rounding down ;) Dec 30 08:25:14 But Units.gu(0.1) / 4 does work Dec 30 08:25:27 Because the GridUnits doesn't get rounded down Dec 30 08:25:52 1 for TP that is and 1.8 for N4 of course ;) Dec 30 08:42:05 Herrie: so you want new reticle, seems it's a little different Dec 30 08:42:20 ? Dec 30 08:43:00 Herrie: so, what you want indeed is a scale Dec 30 08:43:08 not a pixel length Dec 30 08:43:29 so using Units.gridUnits directly makes sense in this case Dec 30 09:10:53 Tofe: Yeah I guess so Dec 30 09:11:11 nizovn: Yeah it would scale better on higher resolution screens Dec 30 09:11:18 That's why the 4* ones were made Dec 30 09:11:32 If you're not happy with the current one I can ask Benjamin to see if he can create a nicer one Dec 30 09:14:49 Herrie: try to scale old ripple to ~Units.gridUnit*5, it scales good. we will spend a little more cpu cycles with 4x Dec 30 09:15:02 anyway i'm going to pr imagePath Dec 30 09:23:21 nizovn: That's because this one is scaled in C++ Dec 30 09:23:31 Others we do in pure QML normally where the quality is worse ;) Dec 30 09:36:39 nizovn: https://github.com/webOS-ports/luna-next-cardshell/pull/250/files Dec 30 09:40:13 ok, it should work Dec 30 14:23:30 nizovn: Yeah it will ;) Dec 30 14:26:27 New build will be started soon, seems I messed up a SRCREV update :P Dec 30 14:26:50 nizovn: You have a LuneOS capable device with a SIM? Dec 30 14:27:20 Seems com.palm.wan is acting up somehow... At least that's what I get on my devices... Dec 30 14:27:27 I suspect it's a bug in C++ code of webos-telephonyd but not sure. Dec 30 14:29:17 Herrie|Laptop: no, only touchpad Dec 30 15:41:47 nizovn: OK Dec 30 18:58:24 Herrie: I haven't found yet what causes the cpu hog, but I may have found the cause of the webengine crash; so, well, not so bad a day :) Dec 30 19:01:17 Tofe: Nice :D Dec 30 19:01:30 Tofe: So you're back? Dec 30 19:02:28 Herrie: yep :) Dec 30 19:04:20 I was never very far anyway Dec 30 19:08:07 Tofe: LOL ;) Dec 30 19:08:25 Seems we now are able to get soundClass, soundFile, duration and doNotSuppress in LNC ;) Dec 30 19:08:47 So can work on getting that to play sounds ;) Dec 30 19:08:53 Should be straight forward Dec 30 19:10:53 Yes, we already play some sounds here and there iirc Dec 30 19:11:28 BootLoader.qml, for instance. Dec 30 19:12:10 Tofe: Yes ;) Dec 30 19:12:34 Just need to see how to deal with soundClass... Seems we need to port something from luna-sysmgr I guess Dec 30 19:12:56 what does soundClass mean, btw? Dec 30 19:13:53 Tofe: https://github.com/woce/LunaSysMgr/blob/a8f94c9171da2af9cdf25a820af6f2a2d68123fc/Src/lunaui/notifications/AlertWindow.cpp#L166 Dec 30 19:13:59 It seems some kind of sound type Dec 30 19:14:03 Like a CSS class :P Dec 30 19:14:56 Basically a stable reference to a file that might change... Dec 30 19:15:07 Ie always call it Ringtone but we'll take the actual ringtone Dec 30 19:15:20 That could be achieved with a simple LS2 call too anyway :S Dec 30 19:15:31 It's a bit of an odd way of dealing with it in the C++ code imho? Dec 30 19:15:37 Ah ok, yes it's only really useful when filepath is empty Dec 30 19:16:13 Also because webOS allowed changing the volume for different sound types? Dec 30 19:16:27 Andolamin: That's dealt with at a differnt place ;) Dec 30 19:17:31 I don't see much reason to do it the way it's done in C++ in QML. Probably doing it will some LS2 call to get the prefs value should do pretty much the same or I read the code wrong. Dec 30 19:17:49 Well, they took advantage of the fact that they are in LunaSysMgr, so they have direct access to preferences and so on Dec 30 19:18:21 Tofe: Yeah I guess so Dec 30 19:18:31 But they're all stored in a single LS2 call if I'm correct Dec 30 19:18:42 luna-send -n 1 palm://com.palm.systemservice/getPreferences '{"keys":["ringtone","systemSounds","uiNotifications", "uiSoundsWhenCharging", "vibrateWhenCharging", "playSoundWhenCharging", "lockmode", "VibrateWhenRingerOn","VibrateWhenRingerOff", "BeatsOnForHeadphones", "ringtone","systemSounds"]}' Dec 30 19:18:45 The main difference I see is the sync/async of the code Dec 30 19:19:07 but QML is async anyway Dec 30 19:19:51 Herrie: yes, let's do it through a LS2 call; anyway I don't think we have much choice here :p Dec 30 19:21:12 Tofe: OK Dec 30 19:21:29 The rest should be easy enough in JS Dec 30 19:22:22 elvispre: You around? Dec 30 19:22:42 Dinner time ;) Dec 30 19:23:14 Herrie: About to watch TV for half an hour, but yes I am. Dec 30 19:54:00 Back from dinner ;) Dec 30 19:54:17 elvispre: You're currently working on something or you have time for some small Enyo stuff? Dec 30 19:54:52 Herrie: I have some time for Enyo stuff, if elvispre is busy Dec 30 19:55:36 Herrie: Also, is there an SVG version of the LuneOS moon logo? Dec 30 19:58:30 Andolamin: I have a PSD version Dec 30 19:59:00 Good enough. Can you send it to me? Dec 30 19:59:06 Yeah let me look it up Dec 30 20:00:12 What we'd need is to add relaunch support to messaging, so when you tap on a notification it will open the correct thread ;) Dec 30 20:03:26 We have a similar implementation in Settings for going to the WiFi panel: https://github.com/webOS-ports/org.webosports.app.settings/blob/master/source/views/Settings.js#L244 Dec 30 20:04:02 So that https://github.com/webOS-ports/org.webosports.messaging/blob/master/service/javascript/utils/MessageAssigner.js#L13 will actually work ;) Dec 30 20:04:32 Sure, I'll take a look Dec 30 20:17:02 Herrie: I am not working on anything in particular. Dec 30 20:20:11 elvispre: OK, seems Andolamin already covered this one ;) Dec 30 20:22:38 OK. Did I see you all talking about sound earlier? Dec 30 20:23:17 elvispre: Yeah ;) Dec 30 20:23:29 I've been playing around a bit with the missing banner params Dec 30 20:23:59 I was thinking of trying to get the clock alarm to actually play something. Is that likely to work? Dec 30 20:24:02 We can now get soundClass, soundFile, duration and doNotSuppress params from the banners via luna-next into luna-next-cardshell ;) Dec 30 20:24:14 Elvispre: If the sound files are there it should Dec 30 20:24:24 Volume UP and Down works for me on N4 Dec 30 20:24:30 ...Shouldn't be too hard then :-) Dec 30 20:24:39 YouTube used to work as well, but doesn't anymore. Dec 30 20:24:44 Not really sure what broke that Dec 30 20:24:51 Could be browser upgrade or pulseaudio Dec 30 20:24:57 Need to dig further a bit Dec 30 20:25:05 LuneTube would not install for me earlier (in Preware 2). Dec 30 20:25:49 Although my simple app that I mentioned was white-screening has started working properly again. Dec 30 20:26:48 Volume up/down is all I ever hear lately. I seem to remember HTML5 audio working some time ago. Dec 30 20:27:00 elvispre: Yeah it did Dec 30 20:27:09 Probably before the qtwebengine upgrade. Dec 30 20:27:16 We upgraded QT (Browser) and also PulseAudio Dec 30 20:27:43 So it's probably somewhere where it connects where things broke... For this we could use morphis ;) Dec 30 20:28:01 morphis: ^ Any chance you'll have some time soon to pick up some things? Dec 30 20:43:15 hi Dec 30 20:43:34 ka6sox: Hi Dec 30 20:43:37 How are things? Dec 30 20:44:05 quieting down Dec 30 20:45:18 Feeling better? Dec 30 20:47:53 Tofe: This fixed application launch from notifications ;)https://github.com/webOS-ports/luna-next-cardshell/commit/88d506898b0679dfad9de8d7e1e88aaa352dfc35 Dec 30 20:48:18 Tofe: This is the corresponding PR: https://github.com/webOS-ports/luna-next-cardshell/pull/251 Dec 30 21:06:29 Tofe: Is 1122 still accurate for web inspector port? If so, any ideas why it won't load from emulator for me? Dec 30 21:10:19 Andolamin: yes, should ve Dec 30 21:10:20 be Dec 30 21:10:52 Hmm. Emulator is set to forward 1122, but that doesn't seem to work for me Dec 30 21:10:59 Tofe: Any way we can check in emulator if it's running? Dec 30 21:13:20 Herrie, not yet. Dec 30 21:22:06 Tofe: Do you remember whihc relaunch we should use again? Dec 30 21:28:08 Tofe: NM sorted Dec 30 21:28:12 tyrok_laptop1: Hi ;) Dec 30 21:33:45 Is there a bug or two that would be easy for a newbie to tackle? A little lost with where to start. Dec 30 21:34:17 On a related note, this would be a very helpful thing to fix to help those of us who are not terribly familiar with how things are set up and improved yet: http://issues.webos-ports.org/issues/987 Dec 30 21:36:43 KyleMaas_Laptop: Long time no see! How are things? Dec 30 21:36:49 Yeah documentation really needs some work ;) Dec 30 21:37:14 KyleMaas_Laptop: What's your area of expertise? C++, JS, QML... ? Dec 30 21:38:02 Herrie: Good. Been out of things for quite a while, so I consider most of what I learned a long time ago to be mostly obsolete at this point. Would still really love to help. Dec 30 21:38:23 KyleMaas_Laptop: Well a lot of things are still similar-ish ;) Dec 30 21:39:03 Herrie: Decent at C/C++ and JS. Could probably start up doing Doxygen docs again, if there's a particular area where that'd be helpful. Dec 30 21:39:45 Biggest changes we've made is: 1. A completely new UI in QML to replace LunaSysMgr. It's not feature complete compared to LunaCE but we're getting there step by step ;) 2. Moved away from the whole webkit 1 BrowserServer/BrowserAdapter model to WebKit 2 and now QtWebEngine ;) Dec 30 21:39:59 Only device I could test things on would be a Galaxy Note II, and porting to it is way beyond my current level of expertise. :) Dec 30 21:40:22 KyleMaas_Laptop: We have a VirtualBox image ;) Dec 30 21:40:28 Glad to hear it. That old code was a mess and convoluted as all get-out. Dec 30 21:40:41 And good old Touchpad still works if you have one ;) Dec 30 21:41:16 So browser wise we're pretty good wrt compatibility. We still need to work on features but well ;) It does the job most of the times at least Dec 30 21:41:32 It beats any legacy browser hands down :P Dec 30 21:41:35 Yeah, I tried the VirtualBox image. Immediately found a number of bugs, but it turned out I didn't download the current development version, so I figured I'd better not file them until I got a chance to re-test with current. Dec 30 21:41:41 Scores 490/550 on html5test.com Dec 30 21:42:06 I saw in the To-Do for the repo that it doesn't support cookies. Is that true? Seems like that'd be kind of a major issue. Dec 30 21:42:06 KyleMaas_Laptop: The non working keyboard was recently fixed by nizovn ;) Dec 30 21:43:08 KyleMaas_Laptop: Well it does cookies I think, just not the management Dec 30 21:43:15 Got a project at work where we'll be using a Raspberry Pi 2 Model B. I saw that's one of the porting target goals. If it works well at work, I might buy one for home use, but I don't have that available yet. Dec 30 21:43:16 I.e. delete them Dec 30 21:43:21 Ah Dec 30 21:43:49 Andolamin is the one who ported to the Pi 2 ;) Dec 30 21:43:59 Is that already working, then? Dec 30 21:44:27 It's working, just there are some issues in the way it's being build that prevents it from including it in our build environment. Dec 30 21:45:05 I.e. It would retrigger a rebuild of QtWebEngine for each target and that's the biggest component we build, so we don't want to do that ;) Dec 30 21:45:18 Hoping to have that resolved soon. Dec 30 21:45:28 Awesome. Well, if it's that close, I might need to buy one anyway. :) Dec 30 21:45:32 Andolamin: Yeah it shouldn't be too long Dec 30 21:46:04 KyleMaas_Laptop: I think Andolamin could hook you up with something though if needed ;) He might have something laying around that you can " plug and play" more or less Dec 30 21:46:14 He uses the offical display with it I think Dec 30 21:47:10 I can put an image up on Dropbox that you can download and flash Dec 30 21:47:26 Andolamin: Awesome. Don't have one yet, but I know who to ping when I get one. Dec 30 21:48:04 Biggest thing I'm concerned about right now is setting up a proper development environment. Code docs that get compiled out are all well and good, but at some point, it would be nice to be able to actually help fix bugs. :) Dec 30 21:48:33 Totally Dec 30 21:48:53 KyleMaas_Laptop: We could use some help on some C++ things in case you want to get your hands dirty :P Dec 30 21:49:29 Herrie: Love to, as long as I can get a good development environment set up to test it. Which kind of comes back to bug #987. :) Dec 30 21:50:00 re: display, I do use the official display with it, but I've also tested with HDMI and it works fine. Scaling might be off if the HDMI display isn't 800x480 like the official display. Touch might be another issue with an HDMI display, as those generally use USB for the touch and the drivers might not be in the build. Dec 30 21:50:12 I use Gentoo on my desktop, Arch on my laptop, and no supported hardware to run things on, so I have a feeling this will be a bit of a complicated thing to get started with. :) Dec 30 21:50:52 Andolamin: Does it work with a Bluetooth keyboard/mouse (provided you plug in a BT dongle, of course)? Dec 30 21:52:07 Bluetooth works with an adapter, but LuneOS isn't fully set up to deal with bluetooth yet, so would be a bit of a hassle for a bit. Keyboard should definitely work, not sure about mouse, though. Would probably need a conf change to show the cursor like emulator. Dec 30 21:52:48 I can try tonight with USB keyboard/mouse and see what happens, bluetooth keyboard/mouse should be the same. Dec 30 21:53:06 KyleMaas_Laptop: For environment: In general anything Ubuntu 12.04+ x64 should work, see http://webos-ports.org/wiki/Build_for_qemux86 Dec 30 21:53:32 Anything similar to this for LuneOS yet? https://github.com/openwebos/build-desktop Dec 30 21:53:43 KyleMaas_Laptop: I followed it to the letter and it was OK Dec 30 21:53:46 It was incredibly handy for both development and showing it off to other people. Dec 30 21:54:15 KyleMaas_Laptop: http://webos-ports.org/wiki/Build_for_qemux86 this one you need Dec 30 21:55:07 I read through that and didn't quite understand how that would mesh with multiple separate repos to be able to change things, commit, and push. Dec 30 21:55:27 KyleMaas_Laptop: We have BT in the backend and also something in Settings just needs hooking up ;) Dec 30 21:55:36 I assume I'd need to clone to my GitHub account and do a pull request once changes are committed, but I didn't see any provisions in there for using a separate repo. Dec 30 21:56:01 KyleMaas_Laptop: Yeah clone repo, make changes and PR ;) Dec 30 21:56:42 Feel free to write things up along the way ;) Dec 30 21:56:50 I can give you Wiki access if that helps ;) Dec 30 21:57:37 Does it honestly need 70GB of free hard drive space to compile? I'd be doing my primary development from this laptop, which has an SSD so space is a little scarce. Dec 30 21:58:57 I'm not sure how much exactly ;) Dec 30 21:59:05 I think 40-50 would do Dec 30 21:59:23 It's the QtWebEngine and dependancies that are HUGE Dec 30 22:00:38 Anyway I'm off to bed for now Dec 30 22:02:56 Ciao! **** ENDING LOGGING AT Thu Dec 31 02:59:58 2015