[05:55] <mihir> Good morning :)
[06:11] <mihir> nik90: ping
[06:19] <zsombi> nik90: your'e most wanted seems :)
[06:19] <mihir> zsombi: hehehe :D
[06:38] <dholbach> good morning
[07:17] <nik90> mihir: just woke up. Give me few mins and we can talk
[07:17] <mihir> dholbach: Morning :)
[07:17] <dholbach> hi mihir
[07:17] <mihir> nik90: no issues, just wanted to confirm just Jenkis is not function or not?
[07:23] <zsombi> nik90: ok, so the alarm issue is the following: after you edit an enabled alarm and right after that you want to disable it, QOrganizer does not remove neither audio nor visual reminders. So we have a problem with either using QOrganizer or with it itself.
[07:23] <justCarakas> gooooooooood morning all :)
[07:23] <zsombi> :)
[07:24] <nik90> zsombi: oh seems like a serious issue
[07:24] <zsombi> nik90: yup, I'll try to remove the reminders in a loop, perhaps we have them in the occurrences somehow still
[07:24] <nik90> zsombi: we are thinking of replacing the old clock with new clock app this evening
[07:25] <zsombi> nik90: good thinking :)
[07:25] <zsombi> nik90: yet I have a MP with ~400 lines...
[07:25] <zsombi> nik90: but this is not solved yet in there...
[07:25] <nik90> Wow
[07:25] <zsombi> nik90: only the model update, but at least the flicking is not there anymore :)
[07:26] <zsombi> nik90: do U remember the bug still?
[07:26] <nik90> zsombi: the flicker issue or the status bug?
[07:26] <zsombi> nik90: both, seems this goes down both to Alarm services...
[07:27] <nik90> zsombi: I haven't created one for the alarm status issue yet
[07:28] <zsombi> nik90: ok, please do so, as it seems we have more problems with that...
[07:28] <nik90> OK. Will ping you with both the bug reports
[07:30] <zsombi> nik90: ok, the loop seems to fix it :)
[07:30] <zsombi> nik90: so we will have a fix for that as well :D
[07:31] <zsombi> nik90: nice way to close the week ;)
[07:32] <nik90> zsombi: :D
[07:32] <nik90> zsombi: but now I have to wait for the next promoted image :P
[07:33] <zsombi> nik90: yes, but at least you know that will come, right? ;)
[07:33] <nik90> yes indeed :)
[07:33] <nik90> zsombi: okay first bug is at https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1359112
[07:34] <zsombi> nik90: I marked the bug #1359112 for rtm14 as well
[07:36] <nik90> zsombi: bug number 2 https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1360101
[07:37] <zsombi> nik90: shouldn't this be also tagged as rtm14?
[07:37] <nik90> zsombi: yup, I just added it
[07:41] <nik90> zsombi: let me know when you want me to test it.
[07:41] <zsombi> nik90: uhh, damn it! of course it has twice the reminders! I'm adding those every time you modify anything on teh alarm, so if you update the alarm 3 times, you will not be able to disable only after the 3rd time! ASO... damn!
[07:42] <nik90> zsombi: yeah I sort of noticed that but figured I was imagining things
[07:42] <zsombi> nik90: so the fix is even easier :)
[07:43] <nik90> woohoo :D
[07:50] <nik90> zsombi: could this be why saving an alarm takes some time?
[07:53] <zsombi> nik90: yes, it could
[07:53] <zsombi> nik90: so, I have to break the MR in a chain of fixes, so it might take some time to land it
[07:54] <zsombi> nik90: but I'l focus on that so we get it done ASAP
[07:54] <nik90> zsombi: ok
[07:54] <nik90> zsombi: I will wait for that to land and the next promoted image before doing the replacement since I think this is a high priority issue.
[07:55] <zsombi> nik90: well, as you wish...
[07:56] <nik90> zsombi: I feel that updating a single alarm which causes the whole alarmmodel to be refreshed is rather detrimental to the user experience. Might as well wait since a fix is in sight.
[07:58] <nik90> popey: what do you think I should do? ^^
[08:06] <popey> zsombi: can you define "some time" ?
[08:07] <mzanetti> nik90: ping
[08:07] <nik90> mzanetti: pon
[08:07] <nik90> pong*
[08:07] <mzanetti> nik90: so there has been some activity on the timezone bug we reported
[08:07] <mzanetti> nik90: seems this is only an issue in the toString() method
[08:08] <popey> nik90: I'm inclined to say we should keep clock-reboot updated in the store and switch the apps when we know we won't regress the clock experience.
[08:08] <mzanetti> nik90: and happens because the JavaScript spec dictates that toString() must print the time in the local timezone
[08:08] <nik90> mzanetti: ah ok
[08:09] <nik90> mzanetti: so what does upstream recommend for our issue?
[08:09] <mzanetti> nik90: could you test if you get the correct time by not using toString(), e.g. by using time.hours() etc
[08:09] <mzanetti> nik90: upstream agrees that this isn't good, but not sure if violating the JavaScript spec is better
[08:09] <mzanetti> nik90: so discussion still ongoing
[08:10] <nik90> mzanetti: ok, I will try this out in another 30 mins and see if that resolves it
[08:10] <mzanetti> nik90: sure, no rush
[08:10] <nik90> popey: ack
[08:10] <mzanetti> nik90: if that's really the case, we could write our own toString() method for time
[08:11] <nik90> popey: it won't regress clock since the old clock app also has the issue. But I don't see any harm in waiting. May be next week we can push it out.
[08:11] <mzanetti> so we could do something like TimeUtils.toString(dataObject) which then takes TZ info into account
[08:11] <nik90> popey: since in the landing email, lucakz mentioned about 2 promoted images per week
[08:12] <popey> thats the target
[08:16] <dholbach> jdstrand, beuno: if you could take a look at https://code.launchpad.net/~dholbach/click-reviewers-tools/1355215/+merge/231569 later on, that'd be nice :)
[08:34] <wellsb> The accounts policy is still reserved?  Goodness, it's been eons.  Is it still reserved in 14.10?
[09:02] <mihir> nik90: https://code.launchpad.net/~akiva/ubuntu-calendar-app/no-upcoming-events-visible-fixed/+merge/231758
[09:02] <mihir> why jenkis is not triggiring ?
[09:02] <mihir> triggering*
[09:02] <mihir> any problem with it ?
[09:03] <nik90> mihir: not sure.. I checked it as well
[09:03] <nik90> mihir: did you try top approving?
[09:03] <mihir> i thought it might be because of empty commit message, i did seet that too
[09:03] <mihir> nik90: nope , i thought lets Jenkis run and i'll top approve then after.
[09:04] <nik90> Well when u top approve it usually runs the test before merging
[09:04] <mihir> nik90: let me try to do that
[09:04] <JamesTait> Good morning all; happy Friday, and happy Hug Your Boss Day! :-D
[09:05] <mihir> JamesTait: seriously, Hug your boss day , hehehe
[09:06] <popey> mihir: nik90 jenkins didn't do it because akiva isn't in the calendar dev team
[09:07] <nik90> popey: but mihir approved it though
[09:07] <mihir> popey: ohhh , is it.. i never noticed this..
[09:07] <nik90> (not top approve)
[09:07] <mihir> popey: i just did Top Approve.
[09:07] <JamesTait> nik90, to be fair, whenever I go to a sprint, as soon as I see my boss it's usually the first thing we do.
[09:08] <mihir> popey: i believe even when i push MR to some other app , it does run Jenkis , if I am not wrong..:|
[09:08] <nik90> JamesTait: erm wrong person :P
[09:08] <popey> dont think so
[09:08] <JamesTait> nik90, heh, sorry! I meant mihir.
[09:09] <mihir> JamesTait: I got it :)
[09:09] <JamesTait> mihir, didn't happen in Malta, though.  In Malta we were roomies, and he was already in bed when I arrived.  That would just have been weird.
[09:10] <mihir> popey: hmmm , so is it mandatory that , user has to be dev group ?
[09:10] <mihir> JamesTait: hehehe , that's nice :)
[09:11] <popey> mihir: for automatic jenkins yes
[09:11] <popey> mihir: but jenkins can be triggered manually too
[09:12] <mihir> popey: how can we do that ?
[09:12] <popey> i dont think you guys can do that, needs auth in jenkins
[09:12] <popey> if you expect more contributions from akiva then I can add him to the team.
[09:13] <zsombi> nik90: popey: "some time"means around a week
[09:13] <popey> zsombi: thanks
[09:13] <popey> JamesTait: you changed the format of https://search.apps.ubuntu.com/api/v1/search?q=architecture:armhf&size=1000&page=1 overnight?
[09:13] <popey> broke my script ☹
[09:14] <nik90> zsombi: ack. Let me know when you have individual MPs to test. I can test on utopic desktop and comment in the MR.
[09:14] <JamesTait> popey, we sent out the warning mails over a month ago. ;)
[09:14]  * popey looks for the mail
[09:15]  * JamesTait does too.
[09:15] <popey> found it, thanks.
[09:15] <popey> ☹
[09:16]  * popey disables the cron job till he can fix it
[09:16] <JamesTait> popey, you have it in a bzr branch somewhere, don't you?  I remember you sharing it a while back.
[09:17] <popey> http://paste.ubuntu.com/8112777/
[09:18] <justCarakas> JamesTait: not sure if my boss would like a hug :p
[09:40] <JamesTait> popey, http://paste.ubuntu.com/8112919/
[09:40]  * JamesTait takes a note to do something with lp:~jamestait/+junk/click-support-tools
[09:50] <davmor2> nik90: 201 had the popup's that trigger location service some people get fixes easily others don't but we don't have a full location stack currently so that is why it might not look to be working, however in 203 the location trusted service isn't even running so it will never get a location fullstop.
[09:51] <nik90> davmor2: ok, I was trying to use location services in the clock app and test an MP. I will root to 201 and do that
[09:52] <davmor2> nik90: I'm pretty sure that tvoss will not be happy about it being broken so it will likely be up and running pretty quickly :)
[09:53] <nik90> davmor2: I am keeping an eye on the bug report as well
[09:54] <brendand> davmor2, did the convo with tvoss continue yesterday?
[09:54] <brendand> davmor2, or did it stop where i left?
[09:55] <davmor2> brendand: stopped but I know how tvoss feels about it :)
[09:56] <brendand> davmor2, right. he didn't comment on why the service didn't start?
[09:56] <davmor2> brendand: no just thanked me for the bug
[10:00] <wellsb> I'm seeing "tcsetattr: Invalid argument" when I try to run application on device.  Then deployment fails with code 134.  Thoughts?
[10:02] <wellsb> Before that, I get: cannot set terminal process group (-1): Invalid argument
[10:03] <ogra_> wellsb, grep DEN /var/log/syslog ...
[10:03] <ogra_> looks like you miss the right apparmor profiles for your app
[10:04] <wellsb> No results for DEN
[10:05] <wellsb> Sorry, the failure code is 139
[10:07] <wellsb> Nope, 134 was right.  139 when I tried the 14.10 framework, but I can't do that because I'm on 14.04
[10:07] <wellsb> The apparmor profiles is a possibility, because I've excluded Accounts because it's reserved, but it really should be there
[10:21] <wellsb> It's been a while since I've touched this app.  It's happening with several other older apps.  Perhaps something has changed in QT.  This should be fun.
[10:21] <nik90> wellsb: are you using kits to run them on device?
[10:21] <wellsb> I am not
[10:21] <wellsb> I saw your video earlier, though.  Could you shoot me that link again?
[10:21] <nik90> wellsb: http://developer.ubuntu.com/start/ubuntu-sdk/using-device-kits/
[10:22] <wellsb> Thanks
[10:22] <nik90> yw
[10:22] <nik90> mihir: if I fix https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1357315, can you help me fix the AP tests?
[10:23] <nik90> mihir: I can create a common calendar branch that we both can hack on
[10:23] <mihir> nik90: sure, we can do that , but we need to fix AP wherever it is being used.
[10:23] <nik90> mihir: shouldn't fixing the function which clicks the button in the emulators.py file fix it everywhere?
[10:24] <mihir> nik90: usually it should be , just push that MR, i'll fix that
[10:24] <nik90> mihir: either way let me fix it first, and then do some manual testing before worrying about the AP.
[10:24] <nik90> mihir: thnx
[10:24] <nik90> mihir: will ping you with the MR when finished
[10:24] <mihir> nik90: sure , thanks.
[10:40] <t1mp> zsombi: does https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/10-alarm-data/+merge/231847 need review from clock-app devs too?
[10:41] <zsombi> t1mp: no, that not
[10:41] <t1mp> zsombi: could it break clock-app if the alarms are not stored/loaded correctly?
[10:41] <zsombi> t1mp: read the commit message :)
[10:42] <t1mp> ahh
[10:42] <zsombi> t1mp: it states it only affects memory manager, and that is a fallback only
[10:42] <zsombi> t1mp: it easesmanual testing, to see the saved data
[10:42] <nik90> mihir: https://code.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/move-save-cancel-buttons
[10:43] <nik90> mihir: I tests creating/editing new events
[10:43] <nik90> mihir: worked as expected. No regressions afaik. Let's fix the AP tests now
[10:43] <mihir> nik90: thanks, i'll start working on this once i reach home :)
[10:43] <nik90> mihir: ok
[10:45] <t1mp> zsombi: ok, happroving
[10:46] <zsombi> t1mp: thx!!
[10:46] <t1mp> bzoltan: are we doing a landing?
[10:46] <zsombi> t1mp: the next two must be tested by the clock app
[10:46] <t1mp> bzoltan: or we wait till monday?
[10:46] <DanChapman> Does anyone know how I could detect the host arch inside a click chroot. Previously I could run dpkg-architecture -qDEB_HOST_ARCH but that doesn't seem to work anymore
[10:47] <bzoltan> t1mp: I just requested a silo
[10:47] <t1mp> bzoltan: cool
[10:47] <bzoltan> t1mp: I wish to land as soon as possoble, but we still have like 5 MRs waiting to be merged
[10:48] <bzoltan> t1mp: I will keep updating the landing MR as the new staging versions happen
[10:49] <t1mp> bzoltan: with the new versioning of the packages it is so much easier to see what will be part of the new landing :)
[10:49] <t1mp> bzoltan: why land as much as possible? we can do another landing next week
[10:49] <t1mp> bzoltan: the landing will already include 15 MRs
[10:50]  * t1mp gets a bit nervous from huge landings. Smaller ones are easier to find issues in case something is broken
[10:50] <nik90> popey: how do you test calendar app on a device?
[10:51] <nik90> popey: do you install the click manually on a device? I cannot run calendar app on phone using QtC since desktop file is missing apparently.
[10:51] <popey> adb push foo.click /tmp
[10:51] <popey> phablet-shell
[10:51] <popey> pkcon install-local /tmp/foo.click
[10:52] <nik90> ah kk
[10:52] <t1mp> nik90: then add a desktop file?
[10:52] <nik90> t1mp: it has 2 .desktop files strangely
[10:53] <t1mp> actually it is weird that we require *desktop* files to run something on a *phone* :)
[10:53] <t1mp> maybe .desktop is not the best name
[10:53] <nik90> hehe
[10:54] <popey> ☻
[10:56] <nik90> popey: http://imgur.com/lCbDpYK
[10:57] <popey> nik90: OOOH!
[10:57]  * popey hugs nik90 
[10:59]  * nik90 hugs back
[11:05] <bzoltan> t1mp:  there was no small landing because nothing went to the staging for 8 days.. all the queued MRs started to land just in the last 2-3 days
[11:08] <t1mp> bzoltan: I know. I tried to say that what we don't get in this landing, we'll get in the next one :)
[11:09] <bzoltan> t1mp: that is why I gave up and started the landing...I still do not have the silo, that is why I said that I will update the landing branch from the staging if it gets new revisions. as it just got the 2006
[11:09] <bzoltan> 1206
[11:13] <bzoltan> t1mp: and you should not be nervous :) I have run the UITK test suite like 6 times in the last 3 days ...no sign of regression
[11:14] <mihir> nik90: t1mp this file is not required , com.ubuntu.calendar_calendar.desktop.in.in ?
[11:15] <nik90> mihir: no we need it
[11:15] <nik90> mihir: the other .desktop is what we added to temporarily fix the qtc issue.
[11:15] <mihir> nik90: then i can see only one desktop file ,
[11:15] <t1mp> bzoltan: ok :)
[11:16] <nik90> mihir: there is another com.ubuntu.calendar.desktop
[11:16] <mihir> nik90: okay , i thought that required for the running into desktio
[11:16] <nik90> mihir: Are there any special packages that need to be installed to run calendar app tests?
[11:16] <mihir> desktop*
[11:16] <nik90> mihir: I get AttributeError: 'module' object has no attribute 'ModuleImportFailure'
[11:17] <nik90> ImportError: No module named dateutil
[11:18] <mihir> nik90: on your local machine ?
[11:18] <nik90> mihir: yes
[11:19] <daker> python-dateutil
[11:19] <mihir> daker: i believe it is by default in python , isn't it?
[11:19] <daker> no
[11:19] <nik90> apparently not, since it is installing it now
[11:20] <nik90> mihir: this should be added to the debian/control file then
[11:20] <daker> https://labix.org/python-dateutil
[11:21] <zsombi> t1mp: nik90: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/20-alarm-model-update/+merge/231863
[11:21]  * mihir makes note to add in control file 
[11:21] <nik90> mihir, daker: anything for File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 628, in useFixture
[11:21] <nik90>     fixture.setUp()
[11:22] <nik90> zsombi: quick question.
[11:22] <zsombi> nik90: t1mp: lemme resubmit
[11:22] <nik90> zsombi: what signal do I use to update "next alarm in ..hr and .. mins" ?
[11:22] <nik90> zsombi: previously I used onModelReset
[11:23] <mihir> nik90: probably , this https://pypi.python.org/pypi/fixtures
[11:23] <nik90> zsombi: but if that isn't fired after an alarm is modified, then is there any other signal i can track?
[11:24] <nik90> mihir: hmm apparently I already python-fixtures installed
[11:24] <daker> nik90: python-testtools & python-fixtures
[11:24] <nik90> daker: both installed already
[11:24] <zsombi> t1mp: nik90: ok, a bit cleaner MR
[11:25] <zsombi> nik90: depends from whom do you want to catch teh signal
[11:25] <nik90> zsombi: I tracked the onModelReset signal in the AlarmModel{} object
[11:25] <zsombi> nik90: from model, you get beginModelReset/endModelReset when the whole model is refreshed (item is added/deleted) or dataChanged() if an item data changes
[11:26] <zsombi> nik90: the dataChanged() will come after we land the MP above
[11:26] <nik90> zsombi: ok I track onModelReset and dataChanged() signal to track additions/editing to alarms
[11:26] <nik90> onDataChanged()
[11:26] <mihir> nik90: hmmm
[11:26] <zsombi> nik90: t1mp: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/20-alarm-model-update/+merge/231867
[11:27] <nik90> zsombi: testing
[11:27] <zsombi> nik90: we could eventually implement separate signals for additionand removal, as the QAbstractItemModel has such a func!
[11:28] <zsombi> nik90: it would be even faster to refresh a model... then to reload teh whole data
[11:28] <zsombi> nik90: but that's further optimizations we can do after RTM, not that critical yet, aint it?
[11:28] <nik90> zsombi: well I am just interested in known when the alarm count changes, an alarm is edited (enabled/disabled) so that I can accordingly update my "next active alarm in " string.
[11:29] <zsombi> nik90: yup
[11:29] <nik90> zsombi: we can leave the refresh model to after RTM yes
[11:29] <zsombi> nik90: now, the last MR for the alarm update ;)
[11:29] <mihir> nik90: you getting any specific error , or it just says what you have mentioned
[11:29] <zsombi> nik90: in ~30-40 mins
[11:30] <nik90> mihir: http://paste.ubuntu.com/8113542/
[11:30] <nik90> zsombi: sweet
[11:30] <mihir> nik90: you need to install dummy service for address book
[11:30] <zsombi> nik90: so this won't be needed anymore https://code.launchpad.net/~nik90/ubuntu-clock-app/fix-status-revert/+merge/231690
[11:31] <nik90> zsombi: yes. I will reject and remove it
[11:31] <mihir> nik90: sorry , it seems you have that too
[11:31] <nik90> mihir: how do you know?
[11:31] <nik90> mihir: I can check on my side if you tell me the package name for it
[11:31] <mihir> nik90: it runs or it never runs any AP ?
[11:32] <nik90> mihir: well it doesn't :)
[11:32] <mihir> ohhhkie
[11:33] <nik90> mihir: actually one sec
[11:33] <nik90> mihir: it seems to be running some of the tests
[11:33] <mihir> nik90: could you check this pacakge , address-book-service-dummy ?
[11:33] <nik90> mihir: like the month scrolling
[11:34] <nik90> mihir: it is testing switching between month view to year view and others..let it finish and see where the failures are
[11:34] <mihir> nik90: not sure it'll resolve issue, but this is must too.
[11:34] <mihir> for new event , it should break when you it tries to add guest.
[11:35] <nik90> mihir: ah ok
[11:36] <mihir> nik90: hmm, if that is the case this should resolve issue.
[11:36] <nik90> mihir: ok so it ran 24 tests, 4 of which failed. I am guessing those were the new event ones
[11:36] <nik90> mihir: yup I didnt have that package
[11:36] <nik90> mihir: ok so 2 packages to add to debian/control
[11:37]  * mihir mihir updates the list for debian/control 
[11:39] <nik90> mihir: hmm same error :/ no worries I will wait until the evening to work with you and balloons on it.
[11:40] <mihir> nik90: ohh
[11:44] <mihir> nik90: it gives same errors , http://paste.ubuntu.com/8113542/ ?
[11:44] <nik90> mihir: oh
[11:44] <nik90> mihir: trunk or my branch?
[11:45] <mihir> nik90: trunk, branch shouldn't work until we make changes to Ap
[11:45] <nik90> mihir: I made a blind change to fix the AP test...here is me hoping that worked :P
[11:45] <mihir> nik90: hahaha okay ,
[11:45] <nik90> mihir: I fixed the _save() function in the emulator.py. That should fix it. but let's see what jenkins says
[11:47] <mihir> nik90: yeah, that should.
[11:48] <nik90> zsombi: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/20-alarm-model-update/+merge/231867 causes clock app to crash when toggling the alarm status.
[11:48] <nik90> zsombi:The Alarm data has been updated with an unregistered item!
[11:48] <nik90> zsombi: The program has unexpectedly finished.
[11:48] <nik90> zsombi: I can get gdb log if you want
[11:48] <zsombi> nik90: no need
[11:48] <zsombi> nik90: that's a qFatal() causing it
[11:48] <zsombi> nik90: intentionally
[11:49] <nik90> zsombi: oh ok
[11:49] <zsombi> nik90: but that's bad
[11:49] <zsombi> nik90 that means the alarm you update is not registred or has different cookie!
[11:49] <nik90> zsombi: I also noticed that after creating a new alarm, the saved alarm switches reinitialized meaning the entire listview repainted
[11:50] <mihir> zsombi: any insights regarding these bugs , https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1357323
[11:50] <zsombi> nik90: well, alarm creation still resetd the whol elist... if we don;t want that, we have to inpmement that as well
[11:51] <zsombi> mihir: did not had time for that yet, sorry
[11:51] <nik90> zsombi: ah ok, this is just when updating an existing alarm?
[11:51] <zsombi> nik90: yep
[11:51] <nik90> zsombi: this would be enough for now.
[11:51] <zsombi> nik90: the rest must be done differently
[11:51] <mihir> zsombi: okay no issues :)
[11:52] <zsombi> nik90: but, the failure you get worries me...
[11:52] <zsombi> do you get that when you update the alarm?
[11:52] <nik90> zsombi: yup, regardless of what property I updated
[11:52] <zsombi> nik90: lemme se with mem manager...
[11:53] <zsombi> nik90: ok, we have a problem with EDS backend then!!!
[11:54] <zsombi> nik90: could you try it locally with memory backend?
[11:54] <nik90> already trying
[11:55] <nik90> zsombi: no happens with mem manager as well for me
[11:55] <zsombi> nik90: huhh? it passes safely 4 me... wth?
[11:55] <nik90> zsombi: I added ALARM_MANAGER=memory to the run environment in QtC project tab
[11:56] <zsombi> nik90: and you see the warning from alarm manager that memory will be used?
[11:57] <zsombi> nik90: ah, it does not display that if env var is used...
[11:57] <nik90> erm no
[11:57] <zsombi> nik90: well, you can see th ediff if you have different alarms in teh different DBs
[11:58] <zsombi> meeting...
[11:59] <zsombi> bbl
[11:59] <nik90> k
[12:03] <mihir> nik90: that works :D
[12:03] <nik90> mihir: woohoo...blind edits works!
[12:04] <mihir> nik90: hahaha  :) let me review that.
[12:04] <nik90> mihir: my fingers are itching to improve the new event design
[12:04] <nik90> mihir: its too cluttered in my opinion :/
[12:04] <mihir> nik90: we have already asked to designers
[12:05] <nik90> mihir: true, but did popey say you guys would get it before RTM?
[12:05] <mihir> nik90: i know it is too cumbersome
[12:05] <popey> what are we talking about specifically?
[12:06] <mihir> nik90: nope
[12:06] <nik90> popey: the New Event page design
[12:06] <popey> I think that'll come with a later calendar redesign, not in the short term
[12:15] <mihir> nik90: i was thinking to bifurcate the repetitions to some other page.
[12:16] <nik90> mihir: I have a revamp in mind. Small minor stuff but I think it will make it look better.
[12:16] <nik90> mihir: I will push it as a common branch again so we both can hack on it together
[12:16] <mihir> nik90: could you do mockup for me ?
[12:17] <nik90> mihir: I will try to create a sample app with just the UI code and show it to you
[12:19] <jdstrand> wellsb: if it's apparmor you would see denials in the logs (eg, 'grep DEN /var/log/syslog' and look for denials at the time of the failure)
[12:20] <jdstrand> wellsb: and fyi, the accounts policy group can now be freely used with 14.10 frameworks
[12:20] <popey> oh, really!?
[12:20] <jdstrand> yep, you can thank mardy
[12:20] <popey> time for wellsb to dust off Blackjack
[12:21] <jdstrand> it now has trust session prompting
[12:21] <jdstrand> (online accounts that is)
[12:21] <jdstrand> so I adjusted the click-reviewers-tools earlier in the week and when we came out of traincon-0, I updated the policy (1.2.21)
[12:25] <beuno> dholbach, sorry, will review today
[12:26] <popey> jdstrand: thanks.
[12:38] <Wellark> DanChapman: hey, let me know how it goes with the connectivity-api
[12:39] <Wellark> DanChapman: are you planning to use Qt or QML bindings?
[12:54]  * dholbach hugs beuno
[12:54] <justCarakas> :p
[12:59] <DanChapman> Wellark, hey :-) thanks for getting it in so quickly. I'm planning to use the Qt bindings so i'll let you know how I get on with it. I can test the QML bindings on it as well if that will help test it?
[13:02] <Akiva-Thinkpad> mordning all
[13:04] <justCarakas> o/
[13:04] <gerlowskija> Does anyone familiar with the calendar-app have some time to look at this MP: https://code.launchpad.net/~gerlowskija/ubuntu-calendar-app/fix-for-bug1350605  It's already been reviewed, but the reviewer (Kunal) couldn't test it because of environmental issues and requested someone else take a look.
[13:05] <zsombi> nik90: the other bug: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/30-alarm-update-fix/+merge/231882
[13:05] <zsombi> nik90: I'm still trying to repro the previous failure, unsuccessfully
[13:05] <nik90> zsombi: but you were able to reproduce it on EDS though?
[13:05] <zsombi> nik90: not on that, I had not tried it on that yet
[13:05] <nik90> zsombi: if I want to set the ALARM_MANAGER=EDS, would that work?
[13:06] <zsombi> nik90: eds, not EDS
[13:06] <nik90> ok.
[13:08] <nik90> zsombi: so whatever run environment options I provides, the alarms shown are the same. Maybe I am not changing the alarm backend properly. Let me try via console
[13:08] <zsombi> nik90: then most likelly you are not using teh right backend
[13:09] <zsombi> nik90: was the package name qtdeclarative-eds?
[13:10] <Wellark> DanChapman: I've tested the service, it works at least for networking status
[13:10] <nik90> zsombi: qtorganizer5-eds
[13:10] <Wellark> the bandwith limitation detection is still missing from the backend
[13:10] <Wellark> DanChapman: could you file a bug about that? it would help
[13:11] <Wellark> DanChapman: if you are going to use the Qt bindings then be aware that the libconnectivity-qt1.pc is broken
[13:11] <Wellark> the fix is on it's way
[13:11] <Wellark> but might be that we can't get it in today
[13:11] <Wellark> depending on how low we are on silos
[13:12] <zsombi> nik90: ok, with EDS I'm getting it as well, but not with memory manager
[13:12] <Wellark> DanChapman: https://code.launchpad.net/~jpakkane/connectivity-api/pkgconfig/+merge/231834
[13:13] <Wellark> DanChapman: you can work around it by not using the .pc file, but manually adding the necessary flags, if you want to try it out before the fix lands
[13:13] <nik90> zsombi: I did "set ALARM_MANAGER=memory" in the console but it doesn't seem to swtich the backend.
[13:13] <zsombi> nik90: btw, I've noticed that no matter what env var I'm setting, it's not gonna use it :/
[13:13] <wellsb> Can I target 14.10 framework if I'm running 14.04?
[13:13] <zsombi> nik90: set? not export?
[13:13] <nik90> zsombi: oh
[13:14] <zsombi> nik90: how you launch it from console?
[13:14] <zsombi> command line pls
[13:14] <Wellark> DanChapman: just set -I/usr/include/connectivity-api/qt1 -I/usr/include/<arch>/qt5/QtDBus -I/usr/include/<arch</qt5 -I/usr/include/<arch>/qt5/QtCore -I/usr/include/<arch>/qt5 /usr/lib/<arch>/libconnectivity-qt1.so.1 -lQt5DBus -lQt5Core -fPIC to your build scripts
[13:14] <nik90> zsombi: I create a builddir and then inside it run "cmake .. && make"
[13:15] <Wellark> you probably have that arch stuff already
[13:15] <nik90> zsombi: once done, I do "qmlscene ../app/ubuntu-clock-app.qml -I backend/"
[13:15] <Wellark> *qt5 stuff
[13:15] <zsombi> nik90: ok, then simply do ALARM_MANAGER=memory qmlscene ...... and the rest
[13:15] <Wellark> DanChapman: setting -I/usr/include/connectivity-api/qt1 -lconnectivity-qt1 should be enough
[13:15] <nik90> zsombi: ah ok
[13:16] <nik90> zsombi: "ALARM_MANAGER=memory qmlscene ../app/ubuntu-clock-app.qml -I backend/" didnt change it
[13:17] <zsombi> nik90: what the heck???!
[13:17] <nik90> zsombi: let me start fresh and see
[13:17] <zsombi> daaaaaaaaaaaaaaaaamn!!!!!
[13:17] <zsombi> nik90: ALARM_BACKEND=memory
[13:19] <nik90> zsombi: lol that worked
[13:19] <nik90> zsombi: u r right, issue is with EDS ;/
[13:19] <zsombi> nik90: I was affraid of that :(
[13:19] <zsombi> nik90: for some reason it changes the ID of the updated one :/
[13:20] <zsombi> nik90: and we don't have renato here ;(
[13:20] <nik90> zsombi: should we check with renato?
[13:20] <nik90> zsombi: ah
[13:21] <zsombi> nik90: he's comin'
[13:21] <nik90> zsombi: u guys in the same place?
[13:21] <zsombi> nik90: no, I see him on our channels :)
[13:21] <nik90> hehe
[13:21] <renatu> zsombi, hi
[13:22] <zsombi> renatu: dude, we have a problem
[13:22] <renatu> more problems :D
[13:22]  * nik90 grinns
[13:22] <zsombi> renatu: when an alarm is updated, I'm getting a different QOrganizerItemId than the one was saved with
[13:22] <renatu> humm this should not happen
[13:23] <renatu> only if the item was removed and created again
[13:23] <zsombi> renatu: in the itemsChanged() signal
[13:23] <renatu> zsombi, let me see I have unit tests for that
[13:23] <renatu> zsombi, do you have a example?
[13:23] <zsombi> renatu: I'm using the ID I'm getting from fetch, and set the fields I want to update, then I get failure because of that
[13:24] <zsombi> renatu: we just got this out with teh new Clock app and some MR of mine, where I only do handle the itemChanged() differently
[13:24] <renatu> zsombi, well the recurrence items will have a different id from the parent event
[13:25] <zsombi> renatu: I'm only interested about the parent ID, I even skip the recurrences
[13:25] <zsombi> renatu: so if a recurrence comes, I take teh parent ID, and use that for update
[13:25] <renatu> zsombi, yeah the id must be the same then
[13:26] <renatu> do you have a example that I can try?
[13:26] <zsombi> renatu: hmm, hold on....
[13:26] <zsombi> renatu: when I save the event, will the QOrganizerItemSaveRequest contain the recurrences as well?
[13:27] <zsombi> renatu: if will, then that's the problem
[13:27] <renatu> zsombi, let me check the unit test, i do not remember
[13:27] <zsombi> renatu: because I only take the first one's ID, which might actually be a recurrence
[13:28] <dholbach> mhall119, kalikiana, bzoltan, lool: ready for the hangout in ~30m?
[13:30] <zsombi> renatu: nik90: /brb
[13:30] <nik90> ok
[13:30] <renatu> zsombi, I do not have unit test for that
[13:30] <renatu> zsombi, I will create one to confirm
[13:31] <zsombi> renatu: so, use an event, change its data and save it, check if the ID is the same
[13:35] <renatu> zsombi, ok
[13:35] <Akiva-Thinkpad> gerlowskija, hey did you get a person to review your branch?
[13:36] <bzoltan> dholbach:  I just got a call from the mother of my kids that i have to be at home in half an hour :( I have to pass this hangout. Sorry.
[13:37] <dholbach> mhall119, lool, kalikiana: ^ are you at least going to make it?
[13:38] <Akiva-Thinkpad> oh is there a hangout going on?
[13:38] <dholbach> Akiva-Thinkpad, depending on the above guys' availability :)
[13:38] <Akiva-Thinkpad> ha
[13:39] <Akiva-Thinkpad> Well if his mom needs him to come home, i understand.
[13:39] <dholbach> I don't think it was his mom :)
[13:40] <lool> dholbach: I am available, but I haven't progressed on things which I think should be implemented
[13:40] <justCarakas> mom wife, don't care, if they need you you  drop everything and go them :p
[13:40] <lool> dholbach: there is one thing which is relatively important to discuss which are frameworks for RTM
[13:40] <dholbach> justCarakas, :)
[13:40] <justCarakas> forgot to add girlfriend :p
[13:41] <dholbach> lool, hum... I don't know - that sounds like a separate discussion to me for which we should invite folks, right?
[13:41] <dholbach> kalikiana, mhall119: what do you think? do you want to talk about api tracking some more?
[13:41] <lool> dholbach: there are three main subtopics to our chats so far: a) where frameworks live -- I now think we want to go to the archive; I've had various chats around this over the week, and it's preferable IMO  b) tracking of ABI, this one I wanted to write some poc code on, but didn't make progress; I think zoltan also wanted to research stuff  c) RTM frameworks, this one needs discussion, I have an opionion
[13:43] <dholbach> lool, so I think kalikiana and mhall119 wanted to talk about 2 some more as they both had some code available already - maybe it'd help to note down the next steps for this project
[13:43] <dholbach> lool, for 3) who can we invite on such short notice?
[13:43] <lool> dholbach: API tracking: I think the status of last call around "This needs implementation per language, this needs to be machine readable and available for click-reviewerstools/appstore/archive" was a good consensus and the rest is just implementation details
[13:43] <dholbach> I mean we have 17m until the hangout starts
[13:44] <lool> ok
[13:45] <dholbach> so.. I don't know what to do
[13:45] <kalikiana> I think we've got a fairly clear idea on b), we seemed to agree on json and having tools according to the language - what we didn't have is input from Js/HTML and Go sides
[13:46] <dholbach> ok... so there should be a discussion, maybe on the phone mailing list, to reach out to the Js/HTML and Go folks?
[13:46] <dholbach> shall I cancel the hangout now?
[13:46] <gerlowskija> Akiva-Thinkpad: Nope, can you take a look please?
[13:46] <gerlowskija> Thanks for asking btw
[13:46] <dholbach> lool, who would you need for discussing rtm frameworks some more?
[13:47] <Akiva-Thinkpad> gerlowskija, sure; what is the branch?
[13:47] <kalikiana> I think we still need to get a decision for where stuff lives - maybe that could be done on the ml also
[13:47] <kalikiana> so it seems we dont have much need for realtime discussion
[13:48] <popey> mhall119: if you have 5 mins can you confirm any of bug 1360265 bug 1360263 bug 1360271
[13:48] <Akiva-Thinkpad> wait found it.
[13:48] <mhall119> dholbach: I'll be there for it
[13:48] <mhall119> if it's not already canceled
[13:48] <dholbach> lool, who would you need for discussing rtm frameworks?
[13:49] <pitti> DanChapman: hey, how are you?
[13:49] <dholbach> mhall119, kalikiana: maybe you can figure out if there's still much that needs to be discussed?
[13:49] <pitti> DanChapman: just trying dekko for the first time -- do you plan to add SSL support? (it currently just as TLS and no encryption)
[13:49] <renatu> zsombi, this is enough : http://paste.ubuntu.com/8114427/
[13:50] <kalikiana> dholbach: mhall119 as far as the tooling goes I think we're pretty clear; I got delayed a bit but I'll have the qml side of it soon and the other languages should be dealt with per ml I think
[13:50] <DanChapman> Wellark, sorry was in a meeting. Great thanks for the workaround, and sure will file a bug for limited bandwidth detection is that against connectivity-api or Network Menu?
[13:51] <mhall119> kalikiana: I assume you have a different solution than what I'm doing for the API website, because I don't get enough detailed data to be useful for API checking of apps
[13:51] <zsombi> renatu: actually you should check if the itemChanged() signal gives the same ID as the one you get after the request completes
[13:51] <dholbach> kalikiana, mhall119: ok, I guess somebody just needs to write a mail to the phone list then to involve the Go and HTML/JS folks as well and we can cancel the call
[13:51] <dholbach> lool, if you let me know who you need for the discussion I can schedule another hangout
[13:52] <kalikiana> mhall119: for the website you only need to use the existing qdoc version tags, no?
[13:52] <kalikiana> you don't actually need to *check* it
[13:52] <renatu> zsombi, ok let me add that
[13:52] <kalikiana> dholbach: I can write an email to the list
[13:52]  * dholbach hugs kalikiana
[13:53] <Wellark> DanChapman: file it against Network Menu, please
[13:53] <mhall119> kalikiana: I meant that my parsers don't look at the methods or properties, it only cares about the higher levels
[13:53] <Wellark> either one is fine, but I will reassign the bugs to network menu then anyway
[13:53] <mhall119> so I can tell you what class is in a specific framework, but now what methods or properties it had in that version
[13:53] <DanChapman> pitti, hey there :-D Awesome!! Yes well the IMAP side does support SSL and is a bug if it's not working. But yes there is plans to add SSL to the SMTP submission side of it. It's just not possible at the moment with the current smtp lib it's using :-(
[13:54] <kalikiana> mhall119: maybe we need to clarify our expectations - I assumed all we want from the docs is to say "since: 1.1", always assuming the latest version - we don't do "back in the day this was different"
[13:54] <mihir> popey: ping
[13:54] <DanChapman> Wellark, ack... thanks
[13:54] <popey> mihir: yo
[13:54] <kalikiana> mhall119: as we have separate old docs anyway which one could use if needed
[13:55] <mihir> popey: i confirm this bug with 2-3 users and it works fine , could you confirm once when you get time today , https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1341697 ?
[13:55] <gerlowskija> Akiva-Thinkpad: https://code.launchpad.net/~gerlowskija/ubuntu-calendar-app/fix-for-bug1350605
[13:55] <mihir> Akiva-Thinkpad: ping
[13:55] <Akiva-Thinkpad> gerlowskija, cool. Want to return the table
[13:55] <Akiva-Thinkpad> mihir, pong
[13:55] <mihir> Akiva-Thinkpad: have approved all your MRs , thanks for that :)
[13:56] <Akiva-Thinkpad> mihir, thanks!
[13:56] <popey> mihir: sure thing
[13:56] <gerlowskija> Akiva-Thinkpad: return the table?
[13:56] <Akiva-Thinkpad> mihir, even the pan flickable one?
[13:56] <popey> Akiva-Thinkpad: gerlowskija thanks for your contributions to core apps recently! It's really appreciated!
[13:56] <Akiva-Thinkpad> gerlowskija, oh nvm, it appears my branch was mereged
[13:56] <Akiva-Thinkpad> popey, yah when is the rtm btw? aug 30th?
[13:57] <mihir> Akiva-Thinkpad: i am left with that , will review that today on my machine.
[13:57] <popey> meh, rtm isn't my priority at the moment ☻
[13:57] <Akiva-Thinkpad> mihir, cool beans
[13:57] <popey> I'm focussed on getting final features landed and making sure we don't regress at all, keeping the autopilot tests working.
[13:57] <mihir> Akiva-Thinkpad: thanks a lot for bitsize bug reports, that we couldn't find :( heheh
[13:57] <Akiva-Thinkpad> heh
[13:58] <mihir> popey: we are on it  for APs for calendar
[13:58] <popey> yeah, I saw, lots of activity from you guys, great work!
[14:00] <mihir> nik90: sure, let me know once you push that.
[14:00] <lool> dholbach: I was off for a bio break before hte hangout did you canclel it?!
[14:00] <dholbach> lool, yes - looks like mhall119 and kalikiana are going to work out "tracking api changes" on their own
[14:00] <dholbach> lool, and I wasn't quite sure who you need for "rtm frameworks"
[14:00] <lool> dholbach: we can skip the part about RTM frameworks this time around and have it some other place/time; I thought Martin was coming today, hadn't realized some folks had been tropped
[14:01] <dholbach> lool, I'm happy to schedule something - who do we need for this?
[14:01] <lool> dholbach: I wonder whether we'd want foundations; there's debconf this week though
[14:02] <lool> dholbach: I think I can work it out with Martin
[14:02] <lool> or on list
[14:03] <mhall119> kalikiana: I don't think there's anything for me to do for api tracking, other than keep the API docs website up to date, is there?
[14:03] <dholbach> lool, great, if that works, that'd be nice - maybe we can briefly catch up end of next week and see which parts still need discussion
[14:03] <mhall119> Wellark: DanChapman: http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Connectivity/
[14:03] <lool> ok
[14:04] <renatu> zsombi, is that ok now? http://paste.ubuntu.com/8114506/
[14:04] <Wellark> mhall119: whoa
[14:04] <Wellark> what did you do?
[14:04] <Wellark> that looks way much better from what I got on my computer
[14:04] <Wellark> mhall119: did you reprocess the xml ?
[14:04] <mhall119> Wellark: no, the HTML
[14:04] <kalikiana> mhall119: yes, that's what I thought. I was asking since you said you didn't get detailed data
[14:04] <mhall119> I just stripped off the header and footer and put in my own
[14:06] <zsombi> renatu: that should be fine, yes
[14:06] <renatu> zsombi, is passing for me
[14:06] <zsombi> renatu: hmm...
[14:06] <dholbach> mhall119, is https://bugs.launchpad.net/ubuntudeveloperportal/+bug/1334275 something we should do something about?
[14:06] <Wellark> mhall119: ok. cool. but in the long run we seriouosly need a tool that can recreate the docs based on the XML files
[14:07] <Wellark> that way we can consistently mix documentation coming from both doxygen and qdoc
[14:07] <Wellark> and somebody should really fix doxygen qml support
[14:07] <Wellark> qdoc is just _horrible_
[14:07] <beuno> dholbach, so, I keep opening and closing the MP
[14:07] <dholbach> beuno, good work!
[14:07] <dholbach> :-P
[14:07] <Wellark> and linking between the QML components and c++ classes just does not work properly even if you use qdoc for both
[14:07] <beuno> dholbach, the main reason is I'm a bit concerned about the maintainability of the way it chooses what to test
[14:08] <beuno> dholbach, as in, manually picking out the modules
[14:08] <mhall119> Wellark: probably, but this way was faster :)
[14:08] <Wellark> mhall119: :)
[14:08] <beuno> dholbach, so I'm worried we'll use this, and tests will slip through the cracks
[14:08] <mhall119> and also didn't involve XML
[14:08] <dholbach> beuno, that's the same issue here: https://bazaar.launchpad.net/~dholbach/click-reviewers-tools/1355215/view/head:/bin/click-run-checks
[14:09] <Wellark> mhall119: I'm just saying that when the time comes that we really want to fix this documentation problem I'm volunteering to share my ideas :)
[14:09] <dholbach> beuno, even more so
[14:09] <nik90> popey, mihir: How's http://imgur.com/Ld8X4GC :D ?
[14:09] <beuno> dholbach, true
[14:09] <beuno> dholbach, great, now I'm MORE worried!
[14:09] <nik90> popey, mihir: Still a wip as you can see in the duplicate Event Name entry field
[14:09] <beuno> :)
[14:10] <dholbach> beuno, right now we need to whitelist new scripts, which all do the same thing (instantiate an object, run .run_checks(), etc.)
[14:10] <mhall119> Wellark: I'd be thrilled if we had just one doc format and tool for everything
[14:10] <dholbach> beuno, that's why I thought we'd be cleverer by automatically finding all submodules where this can be done
[14:10] <Wellark> mhall119: doxygen is close
[14:10] <dholbach> beuno, so we can throw all of click-check-* away at some stage
[14:10] <Wellark> mhall119: but it would need some developer resources to perfect it
[14:10] <dholbach> beuno, and have tests automatically run
[14:10] <beuno> dholbach, I'm happy to defer that general concern seperately
[14:10] <mhall119> doxygen is my least-favorite :(
[14:11] <beuno> dholbach, do you envision this being *the* script to be run now?
[14:11] <Wellark> mhall119: but investing to that XML converter would be fastest way to go
[14:11] <dholbach> beuno, maybe I could add something which prints out all the classes which are omitted
[14:11] <dholbach> beuno, at some stage, yes
[14:11] <dholbach> beuno, right now it'd be popey and myself using it
[14:11] <dholbach> then we can talk to the SDK boys about how it can make their lives easier
[14:12] <beuno> dholbach, +1ed
[14:12]  * dholbach hugs beuno
[14:14] <zsombi> renatu: ok, thx, I think I found the problem: I convert them into variants, and then if I compare them, those are not equal :)
[14:14] <renatu> nice
[14:14] <renatu> welcome
[14:14] <zsombi> nik90: problem solved, I have to do some more changes for the ID :)
[14:15] <zsombi> nik90: renatu: whoaaaah, but teh alarm works ;)
[14:15] <renatu> zsombi, great
[14:16] <dholbach> popey, the next click-reviewers-tools update will have "click-review" :)
[14:16] <nik90> zsombi: woohoo. awesome
[14:24] <popey> dholbach: i branch from trunk ☻
[14:24] <dholbach> :)
[14:25] <popey> just need people to upload apps nwo ☻
[14:26] <dholbach> go go go app developers :)
[14:32] <dholbach> popey, I might have found a bug
[14:32] <dholbach> I'll let you know what my investigation brings up
[14:32] <popey> say it isnt so!
[14:36] <Akiva-Thinkpad> okay now that my family is no longer distracting me, I can look at your bug :P
[14:37] <Akiva-Thinkpad> gerlowskija, ^
[14:43] <dholbach> popey, fixed (r227) - let me know how it works for you :)
[14:44] <zsombi> nik90: a one liner fix for it :D
[14:45] <nik90> zsombi: hehe..they always evade us
[14:45] <zsombi> nik90: yes... I forgot to register the comparators so QVariant can compare the IDs :)
[14:51] <zsombi> nik90: both MRs updated
[14:51] <nik90> zsombi: ack. Will test
[15:02] <DanChapman> popey, does http://people.ubuntu.com/~dpniel/dekko/images/canonical.png look alright?
[15:02] <popey> it does!
[15:03] <popey> nic eone
[15:03] <DanChapman> sweet i'll package her up then
[15:03] <popey> will that change existing setups or necessitate an account delete / create?
[15:04] <nik90> popey: How's http://imgur.com/Pu7CUUi,nUKaHAO ? Is this acceptable?
[15:04] <nik90> popey: I sort of aped the address book app design
[15:06] <popey> nik90: that looks great! a nice improvement
[15:06] <DanChapman> popey, hmm no it may need a recreate as it sets the icon path on saving the account. I might actually change that to fetch it each time an account reloads so they can be changed with no hassle
[15:07] <popey> DanChapman: no bother, just wondered
[15:08] <mihir> nik90: looks good , but again there will be scrolling for rest of the info ?
[15:08] <nik90> mihir: yes, now this is where I would need your input :D. You were saying about moving the repeat option to another page?
[15:09] <mihir> nik90: yup
[15:09] <popey> could that not be revealed?
[15:09] <nik90> mihir: I will need to clean up the code and push it. Once that is done, you can add your idea by moving to another page.
[15:10] <popey> tick repeat, repeat options appear below.
[15:10] <mihir> nik90: wait
[15:10] <nik90> popey, mihir: How about using head.sections like the address book does with all contacts, favourites?
[15:10] <popey> like the way DanChapman has in the email account setup screen, where you tick a box to say "authenticate"
[15:10] <mihir> nik90: i was suggesting same like Google calendar does on mobile ,
[15:11] <mihir> Like  , whatever repeate scenarios are there , it will be end up in strings, when you tap on that it'll popup the mor eoptions
[15:11] <mihir> options*
[15:11] <nik90> I suppose that would Dialogs
[15:11] <nik90> that is a good idea too
[15:11] <nik90> Let's investigate both your idea and popey's idea
[15:12] <Akiva-Thinkpad> gerlowskija, ping
[15:12] <mihir> nik90: popey because , repeations is for only those who needs it
[15:12] <popey> nik90: mihir see http://popey.mooo.com/screenshots/device-2014-08-22-161206.png & http://popey.mooo.com/screenshots/device-2014-08-22-161212.png
[15:12]  * mihir looks to the screenshots
[15:12] <gerlowskija> Akiva-Thinkpad: pong
[15:13] <Akiva-Thinkpad> gerlowskija, hey
[15:13] <Akiva-Thinkpad> so I can verify the bug fixed for me
[15:13] <Akiva-Thinkpad> but there is another obvious bug within that
[15:13] <Akiva-Thinkpad> that I am not sure whether you should address
[15:13] <Akiva-Thinkpad> sec
[15:13] <mihir> popey: that's seems nice too , the checkbox and then visiblity , but again it will increase the length of page , and will become cumbersome
[15:13] <Akiva-Thinkpad> i'll screenshot it
[15:14] <nik90> mihir: u home?
[15:14] <wellsb> Is the Content Hub capable of posting to microblogging accounts like the sendForAccountAsync() method of FriendsDispatcher could?
[15:14] <mihir> nik90: yup , just reached home half an hour back :)
[15:14] <nik90> mihir: ok, give me 20-30 mins to push my code. Let's use that as a base to test out other stuff
[15:14] <mihir> nik90: sure :)
[15:15] <Akiva-Thinkpad> gerlowskija, http://i.imgur.com/wIENQXk.png
[15:15] <mihir> nik90: popey , the poup something like this , http://2.bp.blogspot.com/-JcYLZTVQt1I/UaihHpqTgAI/AAAAAAABJrU/ClkTwNHAxz4/s640/android-calendar-repeat.png
[15:15] <Akiva-Thinkpad> the width of these events prevent numerous events which happen at the same time to display
[15:15] <nik90> Akiva-Thinkpad, gerlowskija: Does any of your MP involve the NewEvent.qml file?
[15:15] <Akiva-Thinkpad> because they don't compress with the image.
[15:16] <Akiva-Thinkpad> nik90, not sure about gerlowskija mp, but my pending one does
[15:16] <Akiva-Thinkpad> think mihir said he'd be looking at it today
[15:16]  * mihir looking at Akiva-Thinkpad MP 
[15:16] <nik90> Akiva-Thinkpad, gerlowskija: Just a heads up, me and mihir are revamping that entire page to be much more cleaner. Mind if we go first? It might even fix other bugs as a result.
[15:17] <popey> mihir: i like that too! especially for a limited set of options.
[15:17] <mihir> nik90: can you cehck, google calendar new event ,
[15:17] <Akiva-Thinkpad> nik90, yah go ahead.
[15:17] <gerlowskija> nik90: no, the changes are all in TimeLineBase
[15:17] <nik90> mihir: I did ..I took inspirations from it :)
[15:17] <nik90> gerlowskija: ack
[15:17] <mihir> popey: i feel this more clean , and the purpose of main event details remains same .
[15:17] <nik90> Akiva-Thinkpad: thnx
[15:18] <mihir> nik90: i could see that :D , thanks for this :D
[15:18] <popey> mihir: yeah, saves excessive scrolling too
[15:18] <mihir> popey: hmm lets try doing that.
[15:19] <Akiva-Thinkpad> gerlowskija, you see the screenshot?
[15:19] <gerlowskija> Akiva-Thinkpad: Yep
[15:19] <gerlowskija> does that behavior (the clipping events on dayview) happen w/o my change?  (I'm at work, otherwise I'd check myself)
[15:19] <Akiva-Thinkpad> gerlowskija, I don't think so, but that is because the events dissappear, ala your bug :P
[15:19]  * Akiva-Thinkpad tries again
[15:20] <gerlowskija> haha, good point.
[15:20] <mihir> Akiva-Thinkpad: gerlowskija , i am not aware, which bug you guys are trying to resolv e?
[15:21] <Akiva-Thinkpad> mihir, https://code.launchpad.net/~gerlowskija/ubuntu-calendar-app/fix-for-bug1350605
[15:21] <mihir> nik90: also , i was planning to do some design when calendar  resize on desktop
[15:22] <mihir> nik90: like if it is new event page, it dispaly all the events on right side of pane :| just a thought , might not be possible for RTM
[15:22] <nik90> mihir: ack. I can review them, but can't really help with it since I am already busy with clock.
[15:22] <nik90> mihir: but that's a good item
[15:22] <nik90> idea*
[15:23] <Akiva-Thinkpad> mihir, here is the actual bug https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1350605
[15:24] <Akiva-Thinkpad> gerlowskija, so yah, it does exist before your bug fix
[15:27] <mihir> nik90: yup i can see that, I really appriciate your help in Calendar,  and i'll do that once we can cleare up RTM milestones.
[15:27] <mihir> Akiva-Thinkpad: i did comment on your MR , does that make sense ?
[15:27] <Akiva-Thinkpad> sec
[15:27] <mihir> Akiva-Thinkpad: it didn't work for me on desktop :(
[15:27] <gerlowskija> Akiva-Thinkpad: \o/ Woo..I didn't cause a new bug!  So I imagine the MP can be merged and the newly-discovered (but not new) bug should just be treated on its own?
[15:29] <mihir> Akiva-Thinkpad: i see,
[15:29] <Akiva-Thinkpad> gerlowskija, yah I am going to report it right now,
[15:29] <mihir> Akiva-Thinkpad: it actually does when i exapand first dropdown
[15:30] <Akiva-Thinkpad> mihir, not the second or third?
[15:30] <Akiva-Thinkpad> it is supposed to activate after expansion
[15:30] <mihir> Akiva-Thinkpad: yeah it does, i just resized more :P
[15:30] <Akiva-Thinkpad> and, it it is relative to your screen size
[15:30] <Akiva-Thinkpad> yah okay good
[15:30] <mihir> Akiva-Thinkpad: i see that
[15:30] <mihir> Akiva-Thinkpad: but i put some code comment , does that make sens ?
[15:30] <mihir> sense*
[15:30] <Akiva-Thinkpad> let me file this bug first, then i'll ping you
[15:31] <mihir> Akiva-Thinkpad: sure no issues , just to make code lil cleanrs.
[15:31] <mihir> cleaner*
[15:31] <mihir> Akiva-Thinkpad:  also , you might need merge from trunk
[15:31] <Akiva-Thinkpad> oh I can guess what you commented ;) I will see if I am right ~
[15:38] <Akiva-Thinkpad> mihir, oh yah, but just to confirm; the merge did work afterall on your desktop?
[15:39] <nik90> mihir: I am experiencing an interesting issue with trunk. When I open the calendar app (trunk), it goes straight to the New Event Page.
[15:39] <nik90> mihir, Akiva-Thinkpad: Can you confirm I am dreaming ^^
[15:39] <Akiva-Thinkpad> To your question about the functions... I wrote about it in one of my commits
[15:39] <Akiva-Thinkpad> Added an animation specifically for going to the bottom of the page. Had to do this to preserve the "to" property. The other animation is situated for going to the bottom of lists.
[15:39] <Akiva-Thinkpad> To go to a bottom of a certain list , utilizing that animation, you have to write a function which will define the "to" property. I wrote three functions for this:
[15:39] <Akiva-Thinkpad> a) Bottom of "This Happens"
[15:39] <Akiva-Thinkpad> b) Bottom of "Recurring events"
[15:39] <Akiva-Thinkpad> c) Bottom of "Recurring Events Date Selector"
[15:39] <Akiva-Thinkpad> brb, battery dying
[15:41] <wellsb> mhall119,  Is the Content Hub capable of posting to microblogging accounts like the sendForAccountAsync() method of FriendsDispatcher could?
[15:42] <wellsb> Or perhaps somebody could point in the right direction regarding the new preferred way to post to twitter, etc from within an app
[15:44] <Akiva-Thinkpad> mihir, sorry about that. Anyways, because nik90 says he will be revamping NewEvent.qml, I don't mind waiting until he does that.
[15:44] <Akiva-Thinkpad> nik90, although some of the bugs have been fixed in that; what exactly do you plan on revamping?
[15:46] <nik90> Akiva-Thinkpad: http://imgur.com/Pu7CUUi,nUKaHAO
[15:46] <nik90> Akiva-Thinkpad: also we plan on moving the Repeat options into a dialog since the new event page is too long
[15:47] <Akiva-Thinkpad> nik90, Ah very nice
[15:47] <Akiva-Thinkpad> nik90, if that is the case, then the bug mihir looked at can be put on hold
[15:47] <Akiva-Thinkpad> after you do the revamp, i'll revisit it
[15:48] <nik90> Akiva-Thinkpad: ack
[15:49] <Akiva-Thinkpad> one thing I may ask though, https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1359306 - I could not make heads or tails out of the function for setting the date times
[15:50] <Akiva-Thinkpad> I think I am going to unassign myself, because the function seems to be referencing a non existent item in the project; ie it behooves me how this is functioning
[15:50] <Akiva-Thinkpad> mind tackling it in my stead?
[15:51] <nik90> Akiva-Thinkpad: mind checking if the latest trunk opens the new event page directly on startup?
[15:51] <Akiva-Thinkpad> sure
[15:54] <Akiva-Thinkpad> bzr branch lp:ubuntu-calendar-app, ran it through the sdk, and the "Month View" is the default page.
[15:54] <nik90> Akiva-Thinkpad: thnx. then it is just a local issue with my sdk.
[15:54]  * nik90 sighs a relief
[15:54] <Akiva-Thinkpad> np
[15:54] <Akiva-Thinkpad> ah nice page
[15:55] <Akiva-Thinkpad> okay the issue for the pan flicking still exists. I'll try rewriting the code I used before but cleaning it up again as mihir suggested.
[15:55] <nik90> Akiva-Thinkpad: I confirmed all the bugs you reported
[15:56] <Akiva-Thinkpad> :)
[15:56] <nik90> Akiva-Thinkpad: feel free to take on them if you can
[16:13] <popey> balloons: heya, we could do with an end of week upload of some of the core apps - maybe later on today?
[16:13] <balloons> popey, sure.. I'll push up the world
[16:14] <popey> balloons: maybe in a bit, right now the guys are still actively reviewing things in calendar for example
[16:15] <balloons> I'll do it later on; if it's too late someone else can approve
[16:15] <wellsb> jdstrand, I can use Accounts policy in 14.10, which is great.  But I wanted to use accounts policy to share to social media streams.  Friends is deprecated now, and contenthub doesn't seem to be able to handle contenttype text yet.  Is this correct?
[16:17] <jdstrand> friends is gone
[16:17] <jdstrand> I can't speak for content hub. I do see 'sharing' to things in other places
[16:17]  * jdstrand points wellsb to kenvandine_, who may have answers
[16:18] <kenvandine_> wellsb, indeed there is nothing for type text
[16:20] <kenvandine_> content hub provides sharing of "content", like files and links
[16:20] <kenvandine_> doesn't provide a way to post like a status update
[16:21] <wellsb> That was my understanding, as well.  With friends gone, is there now no way to post to the microblogging accounts we've added to system settings?
[16:22] <nik90> mihir: https://code.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/revamp-newevent-page
[16:22] <wellsb> kenvandine_, ^  If true, do we not see that as a problem?  Is the reason because of the potential for abuse?
[16:22] <nik90> mihir: it has everything shown in the screnshot
[16:28] <mihir_> nik90: Akiva-Thinkpad sorry guys i got disconnected
[16:28] <mihir_> Akiva-Thinkpad: sure we can wait on that MR , i believe
[16:28] <mihir_> Akiva-Thinkpad: regarding bug https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1359306
[16:29] <mihir_> what exactly you meant to say , you would recommend this to have 1 hour gap instead of 30 mins gap ?
[16:29] <nik90> mihir_: In case you missed it, https://code.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/revamp-newevent-page
[16:29] <nik90> mihir_: I will take on that bug
[16:29] <nik90> mihir_: I know how to fix it
[16:30] <nik90> mihir_: actually feel free to take it. I need to do some clock app tests
[16:30] <mihir_> nik90: okay sure :)
[16:30]  * mihir_ looks at new event design 
[16:30] <nik90> mihir_: when you implement the new dialogs, push to a new branch. Once we both test it and think the design is good, then we merge into our common branch
[16:31] <nik90> mihir_: so branch from our common branch and push to a new branch
[16:32] <mihir> nik90: sure  will do that.
[16:32] <mihir> balloons: we're working on some new design for New Event on Calendar , so will look at AP afterwards , if that gets merged we can roll out till RTM
[16:33] <balloons> mihir, ohh a new design? cool
[16:34] <nik90> balloons: http://imgur.com/Pu7CUUi,nUKaHAO
[16:34] <mihir> balloons:  yup , nik90 and I are trying ,http://imgur.com/Pu7CUUi,nUKaHAO
[16:34] <nik90> mihir: :D
[16:34] <nik90> balloons: that's just the initial work.
[16:34] <kenvandine_> wellsb, you could use the online account to post in your own app
[16:35] <kenvandine_> wellsb, but no, we don't have a common api for microblogging anymore
[16:36] <balloons> mihir, ohh what's  the link? looks broken.. bah it works.. who puts a comma in a URL?
[16:36] <nik90> balloons: it works
[16:36] <nik90> balloons: that's how imgur shows a group of pictures
[16:37] <balloons> mihir, nice.. odds are you won't have to change the tests much as you will be using the same/similar UI components in the end
[16:42] <wellsb> popey, it looks like, even though the Accounts policy is fixed, I still can't use it to do what I want due to the deprecation of Friends API.  Bummer
[16:42] <popey> ☹
[16:43] <nik90> zsombi: I tested your 20-alarm-model-update branch. No more crashes.
[16:43] <zsombi> nik90: 30-... should be the final complete fix
[16:44] <nik90> zsombi: I noticed one tiny thing which I need to fix in the clock app which is I cant tell if the alarm is being saved or not.
[16:44] <nik90> zsombi: previously when the listview repainted i could tell something was being done :P
[16:44] <nik90> zsombi: install 30-... now
[16:44] <nik90> installing*
[16:45] <karni> zsombi: hey man! I hope you're all good. Got a question - would you know when this gets included in the image? https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1354321
[16:45] <karni> zsombi: We're becoming tight on time, and sort of blocked.
[16:46] <karni> by sort of I mean one important feature is blocked on it
[16:46] <nik90> karni: its in a silo atm
[16:46] <karni> YESSS
[16:46] <karni> made my day lol ;)
[16:46] <karni> nik90: which silo?
[16:46] <zsombi> karni: well, guess what, CI is again on strike :), we were about to land it today...
[16:46]  * nik90 checks just to make sure
[16:46] <karni> :O
[16:47]  * karni slaps his forehead
[16:47] <nik90> karni: silo-009 I think
[16:47] <zsombi> nik90: the silo failed last time, bzoltan is working on that, hopefully he manages to get it up, but I doubth it will be landed by next Monday :(
[16:47] <bzoltan> nik90: the UITK builds are busted a bit... we are working on it.
[16:48] <bzoltan> nik90:  if you need the latest and unsupported version please use the SDK Staging PPA
[16:48] <karni> zsombi: thank you, we are very much looking forward to that bugfix in the image :)
[16:48] <nik90> bzoltan,zsombi: I am in no hurry, karni is
[16:48] <karni> sorry to keep asking
[16:49] <karni> bzoltan: we need that feature in the _image_, actually, for an important app for RTM to work
[16:49] <zsombi> karni: no worries, we are as well looking for it
[16:49] <karni> :)
[16:49] <karni> thanks guys!
[16:49] <karni> appreciated, as always
[16:49] <bzoltan> karni: nik90: some version should be available there https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/staging/+packages the new llvm  broke the x86 builds at some point, but it is still newer that than archive
[16:50] <nik90> zsombi: preliminary testing shows the issues seems fixed!
[16:50] <karni> nik90: are you referring to the problem with sound?
[16:50] <zsombi> nik90: glad to hear that!
[16:51] <nik90> karni: sound? oh no thats already fixed :D
[16:51] <karni> oh rly! I can haz sound in the app?
[16:51] <zsombi> karni: no, the flickering of the alarm when edited + disable after edited
[16:51] <karni> ah
[16:51] <nik90> karni: it was due to media-hub not allowing clients to access the /usr/share/sounds folder
[16:51] <zsombi> :P
[16:51] <karni> ah. I was having issues with actually *playing* sound
[16:51] <nik90> karni: latest clock app, one can freely choose whichever rington you want per alarm :)
[16:51] <karni> nik90: sweet
[16:55] <mihir> nik90: I see there went something wrong with the branch, it automatically opens new event page :|
[16:55] <nik90> mihir: yeah I noticed that issue
[16:55] <nik90> mihir: can you check if trunk has that issue
[16:55] <mihir> nik90: nope trunk doesn't have that issue, still will confirm and look at it.
[16:56] <nik90> mihir: the funny thing is I didn't touch anything there which might do that
[17:02] <nik90> zsombi: so creating/deleting an alarm which triggers the listview repaint will be handled in a different bug after RTM?
[17:03] <zsombi> nik90: yes, unless is considered as critical, but file the bug first
[17:03] <nik90> zsombi: ack
[17:07] <nik90> zsombi: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1360359
[17:08] <nik90> zsombi: since the silo is already ready for SDK for this week, I am going to take the time to properly test your MRs to ensure there are no regression in the alarms experience before approving it.
[17:11] <zsombi> nik90: good idea! I'll step away soon, it has been a looooooooooooooong day
[17:11] <nik90> zsombi: Enjoy your weekend
[17:11] <zsombi> nik90: same
[17:24] <mihir_> nik90: is there any way to save the state of componant on dialog ? like textbox value , i enter close the dialog and when i again open it should be there..
[17:24] <mihir_> nik90: or we have to do it manually ?
[17:25] <nik90> mihir_: i think you need to do it manually
[17:28] <mihir_> nik90: storing in hash or array will be good option ?
[17:28] <nik90> mihir_: I dont think we need that
[17:28] <nik90> mihir_: so say you are entering into the dialog for the first time, then show the default values
[17:29] <nik90> mihir_: while exiting the dialog, send that data back to the ui
[17:29] <mihir_> nik90: already did
[17:29] <nik90> mihir_: when opening the dialog again, take the data from the ui and pass to the dialog
[17:29] <nik90> mihir_: so we dont really need an array?
[17:29] <mihir_> nik90: let me try that
[17:46] <balloons> mihir_, so can we land https://code.launchpad.net/~gerlowskija/ubuntu-calendar-app/fix-for-bug1350605/+merge/231252?
[17:57] <gerlowskija> mihir_, yeah, that'd be cool : )
[18:00] <balloons> mihir_, gerlowskija I approved, and will upload to the store as soon as it's merged
[18:09] <gerlowskija> balloons: thanks as always!
[18:11] <balloons> gerlowskija, I'm going to be very happy to see that bug gone.. Ohh, we should have undid the test workaround
[18:11] <balloons> d'ph
[18:12] <balloons> gerlowskija, want to modify it?
[18:12] <balloons> I'll cancel the landing
[18:12] <balloons> there's a workaround in the tests for the bug, we should undo it
[18:14] <gerlowskija> Yep, I can just remove the call to _workaround_bug_1350605() from the AP tests right?  (I don't think I saw the workaround go in, not sure if there's anything else.)
[18:16] <balloons> gerlowskija, yep, it should be self contained
[18:19] <gerlowskija> cool, I'll hop on it in an hour or so when I'm off work.  ping you when it's good to go.
[18:19] <balloons> gerlowskija, kk, sounds good
[18:21] <nik90> mihir_: hey, do you still get the issue where it open the new event page on app startup?
[18:35] <mihir_> nik90: yup , i haven't looked at that
[18:37] <nik90> mihir_: no worries, we will cherry pick the new stuff into another branch one by one to see what triggers that later
[18:47] <ikt> hello :)
[18:54] <mihir_> nik90: nik90: yup , i haven't looked at that
[18:59] <rpadovani> mhall119, hey :-) What's the difference between http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ProgressBar10/ andhttp://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ProgressBar/ ?
[19:16] <popey> ahayzen_:  - content_hub_valid_music_source
[19:16] <popey> 	'source' is empty
[19:16] <popey> I get that when reviewing music...
[19:16] <popey> jdstrand: ^
[19:17] <mihir> nik90: popey http://imgur.com/55bhsQ7
[19:17] <jdstrand> popey: I imagine they are shipping an empty file
[19:17] <jdstrand> popey: that is an error
[19:17] <mihir> popey:  nik90 still it is dirty , working on it..
[19:18] <jdstrand> popey: can you paste the output of click-run-checks?
[19:18] <popey> mihir: nice, I'd call it "Repeat" rather than "Repetition"
[19:18] <popey> jdstrand: ya
[19:19] <mihir> popey: sure will do that  ,
[19:19] <popey> jdstrand: http://paste.ubuntu.com/8116558/
[19:19] <rpadovani> popey, english questions time :D For a popup that advices there is no network connection, what sentence would you use?
[19:19] <jdstrand> "content-hub": "music-app-content.json",
[19:20] <rpadovani> No network available as title and Looking for network... as description?
[19:20] <jdstrand> == content_hub: music-app-content.json ==
[19:20] <jdstrand> {
[19:20] <jdstrand>     "destination": [
[19:20] <jdstrand>         "music"
[19:20] <jdstrand>     ],
[19:20] <jdstrand>     "source": [
[19:20] <jdstrand>     ]
[19:20] <jdstrand> }
[19:20] <jdstrand> ok, so 'source' is empty
[19:20] <jdstrand> it should just not be there
[19:20] <popey> ok, thanks
[19:23] <popey> rpadovani: lemme think
[19:23] <rpadovani> popey, the popup will close on itself when there is network again
[19:23] <rpadovani> it's for reminder
[19:23] <popey> ok
[19:25]  * popey tickles balloons or ahayzen_ with https://code.launchpad.net/~popey/music-app/fix-content-hub-source/+merge/231956
[19:27] <popey> rpadovani: "Network unreachable"  "Reconnecting..."
[19:28] <popey> mihir: i like what you're doing there with that repeat panel by the way, much better than my idea ☻
[19:28] <rpadovani> thanks sir!
[19:32] <popey> np!
[19:34] <mihir> popey:  :)
[19:35] <mihir> popey: but it require lots of change & testing
[19:37] <mihir> Akiva-Thinkpad: ping
[20:00] <ikt> anyone know how to stop javascript from running before the page is on is visible?
[20:03] <mihir> trivial MR review , https://code.launchpad.net/~mihirsoni/ubuntu-calendar-app/1360431/+merge/231963
[20:05] <ikt> anyone who can help? :(
[20:06] <ikt> I'm getting: Cannot assign object type QQuickListView with no default method when attempting to load the listview on visibility change
[20:08] <mihir> ikt: could you share your code , so that we can try to look at snippest and could suggest
[20:15] <twstddev> Guys, is there a documentation on how to load modified version of Ubuntu plugins in Qt Creator?
[20:15] <nik90> mihir: looks cool
[20:15] <nik90> mihir: nice work
[20:16] <mihir> nik90:  :)
[20:16] <mihir> nik90: could you review MR i just gave ?
[20:16] <nik90> mihir: link
[20:16] <ahayzen_> popey, thanks reviewing now :)
[20:16] <mihir> nik90: https://code.launchpad.net/~mihirsoni/ubuntu-calendar-app/1360431/+merge/231963
[20:16] <ahayzen_> popey, i initially read it as u making source support lol
[20:16] <mihir> nik90: the bug is , currently you can't edit event with weekly options..
[20:19] <ahayzen_> popey, top approved \o/ it'll land in a bit
[20:23] <ikt> ty mihir, this: http://pastebin.com/7kkZYBh8 is where I tried onvisiblechanging the whole page but it comes up with the error about the default method, this: http://pastebin.com/nLdFM3zi is closer to what I'm trying to do, I want to grab the text from the textfield and then use that to load the subreddit when you click K go, but instead as you can see from the console.logging it's taking every char straight away before you eve
[20:24] <mihir> ikt: why don't you use , dialog ?
[20:25] <mihir> ikt: http://developer.ubuntu.com/api/devel/ubuntu-13.04/qml/ui-toolkit/overview-ubuntu-sdk.html
[20:28] <mihir> nik90: you want me to create saperate branch for this ?
[20:28] <mihir> on ubuntue-calendar-dev ?
[20:29] <nik90> mihir: yes, and then propose it against our common branch
[20:29]  * mihir push new design changes
[20:30] <mihir> nik90: but still it is not 100% done
[20:30] <nik90> mihir: I know, but you are only proposing it. You can still keep adding stuff into your branch
[20:30] <nik90> mihir: once your branch is ready, I can review and then merge you branch into ours
[20:32] <ikt> mihir: ty i will try that
[20:34] <nik90> mihir: I can only review the MRs tomorrow. Going to have some dinner and then game on :D
[20:34] <mihir> nik90: no issues..
[20:34] <mihir> nik90: this changes, doesn't allow us to create new event.
[20:35] <mihir> but i made sure that we get popup and get those value back to the poups if again it is clicked.
[21:41] <gerlowskija> balloons: ping
[21:55] <mhall119> rpadovani: sorry for the late reply, I have no idea what the ProgressBar10 is, Kaleo might know
[21:55] <mhall119> or t1mp maybe
[21:58] <Kaleo> mhall119, ProgressBar10 is the version 1.0 of the ProgressBar implementation
[21:58] <mhall119> ah, rpadovani ^^ there you go
[21:58] <mhall119> Kaleo: it's an odd name for it though, reads as "ten" rather than "1.0"
[21:58] <Kaleo> mhall119, indeed
[21:59] <Kaleo> mhall119, I was not there when it was decided
[21:59] <Kaleo> mhall119, but anyway the API is still ProgressBar
[21:59] <mhall119> Kaleo: do we plan on supporting old implementations in newer versions of the UITK?
[21:59] <Kaleo> mhall119, not exactly
[22:00] <Kaleo> mhall119, but when there are API additions they are exclusive to the new versions
[22:00] <Kaleo> mhall119, so I guess we added an API in ProgressBar between 1.0 and 1.1
[22:00] <Kaleo> mhall119, so if you don't change your import to 1.1, if you keep it to 1.0 that is, you will have access to only the 'old' API
[22:00] <mhall119> it seems we might want a special namespace for those, rather than fill up the main namespace with Component##
[22:01] <Kaleo> mhall119, there is no such thing as "namespace"
[22:01] <Kaleo> mhall119, it's a file system
[22:01] <mhall119> Ubuntu.Components?
[22:01] <Kaleo> mhall119, so, either it goes in the filename or in the directory name
[22:01] <Kaleo> mhall119, that's separate
[22:01] <Kaleo> mhall119, the files for implementation and the API exposed are separate things
[22:01] <Kaleo> mhall119, the translation is done in the qmldir file
[22:01] <mhall119> could we have Ubuntu.Components.v1.ProgressBar?
[22:02] <Kaleo> mhall119, we could
[22:02] <Kaleo> mhall119, but that's just weird because you would still have to change the version in your import
[22:02] <Kaleo> mhall119, import Ubuntu.Components.v10 1.0
[22:02] <Kaleo> mhall119, import Ubuntu.Components.v11 1.1
[22:02] <Kaleo> mhall119, not so useful
[22:02] <mhall119> so is ProgressBar10 only used if you have the newer UITK, but your import line still references the old UITK?
[22:03] <Kaleo> yes
[22:03] <Kaleo> but to be precise
[22:03] <Kaleo> only if you do:
[22:03] <Kaleo> import Ubuntu.Components 1.0
[22:03] <Kaleo> then ProgressBar10.qml is loaded
[22:03] <Kaleo> if you do:
[22:03] <Kaleo> import Ubuntu.Components 1.1
[22:03] <Kaleo> then ProgressBar11.qml is loaded
[22:03] <Kaleo> and ProgressBar11 inherits from ProgressBar10
[22:03] <mhall119> do would a developer ever use "ProgressBar10" in their code?
[22:03] <Kaleo> no
[22:03] <Kaleo> it's not exposed
[22:04] <Kaleo> nobody has access to that
[22:04] <Kaleo> so that question is curious
[22:04] <Kaleo> (the original question)
[22:04] <Kaleo> I wonder where ProgressBar10 appeared in an app
[22:04] <mhall119> Kaleo: it was sucked up by my API docs parser and published on http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components/
[22:04] <Kaleo> mhall119, ah
[22:04] <Kaleo> mhall119, got it
[22:05] <Kaleo> mhall119, bad
[22:05] <Kaleo> mhall119, only things listed as public in the qmldir should have documentation publised
[22:05] <Kaleo> +h
[22:05] <mhall119> I don't see anything in the qdoc output that would tell me it's not public
[22:05] <Kaleo> mhall119, I need to get back to my profiling before I lose the thread
[22:05] <mhall119> <qmlclass name="ProgressBar10" qml-module-name="Ubuntu.Components" qml-base-type="::AnimatedItem" fullname="Ubuntu.Components::ProgressBar10" href="qml-ubuntu-components-progressbar10.html" access="public" status="commendable" title="ProgressBar10" fulltitle="ProgressBar10" subtitle="" groups="ubuntu" brief="The ProgressBar component visually indicates the progress of a process of determinate or indeterminate duration.">
[22:05] <Kaleo> mhall119, only in the qmldir you will have that info
[22:06] <mhall119> ugh, that means I have to pull in another package and parse something else :(
[22:06] <Kaleo> mhall119, hang on
[22:06] <Kaleo> mhall119, in fact it's more complex than that
[22:07] <Kaleo> mhall119, a) we should have either 2 separate documentations: one for 1.0 and one for 1.1 or only the one for 1.1
[22:07] <Kaleo> right
[22:07] <Kaleo> probably just the one for 1.1
[22:07] <mhall119> oddly, ProgressBar11 is marked as access="private" in the qdoc output, and wasn't published
[22:07] <Kaleo> ahahaah
[22:08]  * mhall119 apologizes if I've ruined your profiling work for the evening
[22:08] <Kaleo> mhall119, you have not because I will stop talking about doc :)
[22:08] <Kaleo> mhall119, but you have the gist of the idea now
[22:08] <mhall119> yeah
[22:08] <mhall119> if I didn't care about improving performance so much, I'd keep bugging you
[22:09] <Kaleo> mhall119, check with the toolkit folks on Monday if you don't figure it out
[22:09] <Kaleo> mhall119, :)
[22:09] <Kaleo> mhall119, app startup performance in this particular case..
[22:10] <mhall119> even more important, get back to that
[22:10] <Kaleo> mhall119, just so that it's clear, the qmldir tells you which QML file belong to which version
[22:10] <mhall119> I'll figure out what to do with the docs on Monday
[22:10] <Kaleo> mhall119, so qdoc should probably parse that and communicate that information to you
[22:11] <Kaleo> mhall119, ok
[22:11] <Kaleo> mhall119, have a good one then
[22:12] <mhall119> you too