[12:06] <dpm> ah, davidcalle, I did some more edits to the community ports page yesterday and I created an anchor to it: https://developer.ubuntu.com/en/start/ubuntu-for-devices/devices/#community-ports
[12:06] <davidcalle> dpm: oh nice edits!
[12:07] <dpm> well, you did all the work revamping the page :)
[12:11] <davidcalle> popey: dpm: mhall119: balloons: dholbach: do we have a good way of recording the phone screen at "at least" ~20fps and no lag? I've tried many things without success. Maybe there is a brand new method I'm not aware of?
[12:15] <popey> no
[12:15] <popey> the way I do it, I get ~4fps
[12:16] <popey> http://paste.ubuntu.com/15130508/ that's the script I use
[12:16] <popey> plug phone in over usb cable and run that script
[12:41] <davidcalle> popey: excellent! I've tweaked it a little and I get the perf I need
[12:41] <popey> patches welcome davidcalle :)
[12:42] <davidcalle> ssh $SSH_OPTS -C -c aes128-ctr phablet@localhost mirscreencast -m /var/run/mir_socket --stdout --cap-interval 1 -s 360 640 |  mplayer -framedrop -demuxer rawvideo -rawvideo w=360:h=640:format=rgba -
[12:42] <davidcalle> l135
[12:43] <davidcalle> popey: ^
[15:36] <sverzegnassi> balloons: ping
[16:14] <dpm> balloons, can you remind me... core app click packages are built on every commit of a MP, or only when it's been approved and merged into trunk?
[16:14] <balloons> we build on every commit
[16:14] <dpm> ok, cool thanks
[16:14] <balloons> so we get a click everytime. However, what goes into the store / gets reviewed is built seperately
[16:15] <balloons> sverzegnassi, pong
[16:15] <dpm> and what does it mean that it's built separately?
[16:15] <balloons> I mean, popey builds them however he wishes :-) I don't believe he takes the click from the a jenkins MP, but maybe he does :-)
[16:16] <popey> sometimes
[16:17] <popey> I was building locally for a while for numerous reasons. 1) When jenkins failed, 2) When I wanted a fat package, 3) When jenkins builds a click without the right version number in the filename
[16:17] <popey> (3) is the only one that still applies now
[16:17] <popey> due to the rather ropey chroot we have, which doesn't have bzr installed due to dependency hell
[16:18] <balloons> ahh, well presumably you just kick off a build of trunk to get your click then?
[16:19] <popey> yes
[16:19] <popey> I build every core app every day anyway
[16:19] <popey> but if I am about to upload and one of the above issues arises, I'll build on demand
[16:22] <balloons> so dpm, the workflow is covering the upload to the store. The first bit happens on every commit, the second is the store upload. I had them broken up better, but left them as bullet points since I wanted to make a visual anyway
[16:24] <dpm> popey, but I guess that (3) is simply a bug? Is it still present and affects all apps?
[16:28] <balloons> dpm, afaik it's an issue with how cmake is built. I'd call it simply a bug that could be fixed
[16:30] <popey> yes, it's a bug
[16:30] <popey> its a bug in the samba packaging which means we have to do a bit of a packaging dance
[18:33] <lets_go_surfing> appdevs: Hi there, I'm quite new to QML development and I hope I can find some help here. Imagine I'm writing a client to some rest API, so the question is: how much should I implement in C++ and how much in QML?
[18:34] <lets_go_surfing> At the moment I have a rest client implemented using JS via XMLHttpRequest and it works fine, but the question is how to implement for example loading of images, how to persist them, is it possible from QML?
[18:35] <lets_go_surfing> Since Ubuntu apps are being written using QML, I hope some of you guys can help me a bit here, thanks in advance!