[00:00] <spymastermatt> oh ok. I must have missed that in the API docs
[00:00] <spymastermatt> yeah it seems like layouting within layouting would be useful
[00:01] <nik90> spymastermatt: You might want to report a bug at https://launchpad.net/ubuntu-ui-toolkit
[00:01] <spymastermatt> for example, in this case I was hoping to have a list of folders and a list of emails where they occupy the available space side by side if there is space, or overlapping and collapsing if not
[00:01] <nik90> spymastermatt: I will also talk to the SDK dev as to why this limitation is present.
[00:01] <spymastermatt> cheers thank you
[00:02] <spymastermatt> i will report this bug tomorrow evening as it's getting late here.
[00:02] <spymastermatt> thank you for your help
[00:02] <nik90> spymastermatt: np..yw
[04:33] <mayank> disconnect
[04:33] <mayank> hello
[07:01] <dholbach> good morning
[08:49] <nik90> good morning
[08:49] <nik90> zsombi: ping (alarms)
[09:23] <zsombi> nik90: pong
[09:26] <JamesTait> Good morning all; happy World Bartender Day! :-D
[09:26] <ara> Kaleo, ping
[09:30] <nik90> zsombi: I was testing the alarms on image 205 and it seems there is a timezone issue.
[09:30] <nik90> zsombi: when I create an alarm in UTC+1, the alarm is saved and triggered in UTC.
[09:31] <nik90> zsombi: I am collecting alarms dogfooding blocker bugs at https://bugs.launchpad.net/ubuntu-clock-app/+bugs?field.tag=dogfooding-blocker
[09:31] <nik90> zsombi: the one that I referred to above was https://bugs.launchpad.net/ubuntu-clock-app/+bug/1283236
[09:31] <ubot2`> Launchpad bug 1283236 in Ubuntu Clock App "Alarms are triggered in UTC tz despite saving in local tz" [High,Confirmed]
[09:32] <zsombi> nik90: SDK Alarms API timezone support was not scheduled for 0.1 release. On the other hand Alarms API passes the date object as it comes from the UI, not doing any conversion. I could check whether the Qt QDate API does conversions there, but I doubth
[09:33] <nik90> zsombi: yeah I remember reading the blueprint where timezone support lands in future releases of alarms API
[09:33] <nik90> zsombi: I need to know what timezone does EDS expects the alarm time to be in?
[09:34] <nik90> zsombi: since something is converting all the alarms times in UTC.
[09:36] <zsombi> nik90: as said, I pass the date objects in the format it comes, as objects. So EDS backend perhaps fetches the date with other format... or I have no idea...
[09:37] <nik90> zsombi: then I have to assume EDS is the culprit here...I will talk to renato to confirm this
[09:37] <nik90> zsombi: what is the expected timeline for the v0.1.1 and 0.2 releases of the alarms API?
[09:37] <nik90> zsombi: Is it for this cycle or the next?
[09:38] <zsombi> nik90: I can also verify that Alarms API passes the data properly and even check if the QOrganizerEvent has the proper dates
[09:38] <zsombi> nik90: as soon as we get all the bits'n'pieces ready for 14.04
[09:39] <nik90> zsombi: Are you referring to the !t 5.2 bits for 14.04?
[09:39] <nik90> s/!t/Qt
[09:39] <zsombi> nik90: there will be tiny fixes, like APP_ID is gonna come mid march
[09:40] <zsombi> nik90: nopez, there are lopts of issues we need to fix by 14.04
[09:40] <nik90> ok
[09:41] <zsombi> nik90: like text input was left soooooooo much behind that we need to refresh it heavily, few new components still must land, then import versioning must be updated, new UI designs, etc
[09:42] <zsombi> nik90: but any time we have a critical issue (bug or new component) to fix, that makes us slip with all the planned stuff :(
[09:42] <nik90> zsombi: can you confirm if the Alarms API is passing the correct time to EDS and check if the QOrganizerEvent has the proper dates?
[09:42] <nik90> zsombi: this way I can approach the concerned people and discuss it with them
[09:43] <zsombi> nik90: it will take some time while I can do that... but yes, I can check it
[09:43] <nik90> zsombi: ok
[11:05] <m-b-o> popey moin
[11:14] <m-b-o> popey MWC build for weather is done, right?
[11:25] <ara> kalikiana, ping
[11:25] <kalikiana> ara: pong
[11:29] <WebbyIT> mzanetti, o/ hope you had a nice weekend :-) When you have some time, could you review the camera improvement, please? :-)
[11:29] <WebbyIT> https://code.launchpad.net/~rpadovani/reminders-app/cameraImprovement/+merge/206559
[11:29] <mzanetti> WebbyIT: ok
[16:37] <zyga> hey
[16:37] <spineau1> hello
[16:37] <zyga> so what is this about? (which issue?)
[16:37] <ara> zyga, spineau1: bzoltan1 cannot reproduce the build issue in his precise chroot
[16:37] <zyga> ara: ah, I see
[16:37] <zyga> bzoltan1: have you seen the failure logs from our PPA?
[16:37] <spineau1> let me find a buildlog
[16:38] <bzoltan1> spineau1: zyga: if you depend on qt4.8 stuff and use qt5 then funny things are expected to happen
[16:38] <bzoltan1> spineau1: zyga: could you remove the qt4-linguist-tools from your build?
[16:39] <spineau1> here it is: https://launchpadlibrarian.net/167379225/buildlog.txt.gz
[16:39] <spineau1> taken from here, our dev ppa: https://code.launchpad.net/~checkbox-dev/+archive/ppa/+recipebuild/658552
[16:39] <zyga> bzoltan1: we depend on both
[16:39] <zyga> bzoltan1: is that impossible with qt?
[16:39] <zyga> bzoltan1: (we need qt4 for old UI and qt5 for the new UI)
[16:40] <spineau1> the relevant part: http://pastebin.ubuntu.com/6987854/
[16:40] <zyga> as for the linguist, I'm currently fire-fighting python + virtualenv but I could setup a builder in a moment
[16:42] <roadmr> bzoltan1, spineau1 : remember the problem is detailed here: https://bugs.launchpad.net/checkbox/+bug/1282257
[16:42] <ubot2> Launchpad bug 1282257 in checkbox "qt4 and qt5 dev tools can't be installed together on 12.04 from the ubuntu-sdk-team PPA" [High,Confirmed]
[16:42] <roadmr> bzoltan1: I see no way to remove qt4-linguist-tools and qt4-qmake since libqt4-dev depends on them :(
[16:46] <spineau1> bzoltan1: roadmr: basically we would need a qtchooser for precise with a version >= 4:4.8.4, is it possible?
[17:11] <iBelieve> mhall119: ping
[17:21] <bzoltan1> zyga: roadmr_: It is a bit strange setup to build both qt4 and qt5 UI at the same time. I would set up two separate projects and provide two separate package for the different UIs ... The qt4 is going to be dead meat very soon. But I will look around to see if there is a fix to your problem. But i will be frank with you ... suporting Qt4 on 12.04 is not a top priority for me right now.
[17:23] <roadmr> ok, understood
[17:23] <zyga> bzoltan1: the old package is a rather old ui, we want to get rid of it but it's not up to us
[17:24] <zyga> bzoltan1: would it work if it were being distributed into one ppa from two recipes?
[17:24] <bzoltan1> zyga: who's decision would that be?
[17:24] <zyga> bzoltan1: or is that basically a no-go because of qt5
[17:24] <roadmr> bzoltan1: about the bug, I filed it in checkbox but I wonder if it may be appropriate to add a task in another project (which project would that be?) so it's properly tracked
[17:24] <zyga> bzoltan1: our downstream users
[17:41] <mhall119> iBelieve: pong
[17:42] <iBelieve> hi mhall119, did you want to set up a time to discuss the snippets app?
[17:43] <mhall119> iBelieve: yes, when is good for you?
[17:45] <iBelieve> mhall119, Anytime other than Tuesday at 21 UTC and Thursday
[17:46] <iBelieve> mhall119: between 16 UTC and 23 UTC
[17:47] <iBelieve> mhall119: today works as well
[17:49] <mhall119> iBelieve: tomorrow at 1800 work for you? unfortunately I'm busy today trying to finish things on the developer portal
[17:55] <bzoltan1> zyga:  roadmr: Please give me half a day to sort out if there is something i can do with this problem. My team is in GMT+1 an GMT+2 :)
[17:55] <iBelieve> mhall119: sure, that will work fine. Google Hangouts?
[17:56] <zyga> bzoltan1: thanks
[17:56] <roadmr> bzoltan1: thanks! apologies for troubling you with this :(
[17:57] <mhall119> iBelieve: yes, PM me your address and I'll add you to the calendar invite
[17:57] <bzoltan1> roadmr: zyga: no worries ... I was heavily involved with the initial Qt5 packaging and the co-install-ability of Qt4 and Qt5 were a clear target ... but we knew that more people will use both beasts together more issues will pop up. It is just one of those issues :)
[17:58] <iBelieve> mhall119: Do you want to invite Daniel Holm as well? He was interested in contributing
[18:47] <nik90> renato: Were you able to get a landing slot for the EDS event fetch limit?
[18:48] <renato> nik90, not yet we are testing on device
[19:07] <love2xlr8> can anyone help me out with kde headers? I'm trying to compile an app on ubuntu and I think it needs kdelibs3-dev since this isn't available I installed kdelibs5-dev. But the configure keeps saying that I need to use an other prefix because it can't find the libs
[23:08] <jdstrand> popey: hey-- just read the beginning of your email to ubuntu-phone. I've been wanting to dtrt wrt working on different form factors with my apps, but not sure how to start. Are there tutorials, examples, etc? Are we supposed to check the resolution? does the sdk give us help here?
[23:08] <popey> jdstrand: heh, good question!
[23:09] <popey> a good example is KarmaMachine https://github.com/brianrobles204/Karma-Machine
[23:09] <jdstrand> currently I think I just do units.gu(50) x units.gu(75) and hope for the best :)
[23:10] <aquarius> jdstrand, see https://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Layouts/
[23:10] <popey> yeah, we tried that, and on the nexus 7 discovered some pain
[23:11] <jdstrand> popey: yeah, I'm guessing my apps aren't working right on it
[23:11] <aquarius> I ain't saying it *works*, I'm just saying that that's what you're supposed to use -- that's the SDK giving some help. :)
[23:11] <jdstrand> aquarius: oh, interesting
[23:11] <jdstrand> thanks. I'll play with that the next time I have some play time :)
[23:13] <aquarius> it's on my list to play with too :)
[23:14] <rpadovani> If I create a webapp following this, does it work also on Unity8?
[23:14] <rpadovani> http://developer.ubuntu.com/web/tutorial/