[00:12] <ppd> hi. Is there any way to set the icon theme where QML "Icon" gets its icons from? I'd like to use some icons from ubuntu-mobile on the desktop
[09:14] <JamesTait> Good morning all; happy Monday and happy Carrot Cake Day! :-D
[12:47] <mivoligo> hi
[12:48] <mivoligo> nik90: sorry I wasn't here before to discus that bug, but somehow I couldn't connect to IRC
[12:49] <nik90> mivoligo: no worries, a MP is a good place to discuss corrections as well :)
[12:49] <daker> there was a DDOS attack on freenode a few hours ago
[12:50] <nik90> oh yeah
[12:50] <nik90> mivoligo: but nice work...you fixed one of my personal annoying bug :)
[12:52] <mivoligo> nik90: thanks
[12:54] <mivoligo> nik90: Jenkins Bot bothers me about commit message whereas it clearly says "optional" grrrr...
[12:54] <nik90> mivoligo: ah I forgot to mention..the commit message on the MP is not optional
[12:55] <nik90> mivoligo: the "Description of Change" is optional :)
[12:56] <nik90> mivoligo: I reapproved..it will rerun the tests and merge
[12:58] <mivoligo> nik90: nevermind, as I said in the alarm to achieve the snapping I need to change a lot more code
[12:58] <mivoligo> nik90: as a start the maximumValue for dialerHands are now 60, but for snapping to work it have to be 12 or 24 for the hour hand
[12:59] <mivoligo> nik90: so functions:  circlePositiontoHours and hourstoCirclePosition have to be changed
[13:00] <mivoligo> nik90: are these only used in the alarm part?
[13:00] <nik90> mivoligo: you should be able to change the maximumValue of the dialerHand to 12 or 24 depending on the time format used.
[13:00] <nik90> mivoligo: yes those functions are only used in the alarms part.
[13:01] <nik90> mivoligo: maybe in onHoursChanged: { maximumRange  = 12; }
[13:02] <mivoligo> nik90: ok, that's good
[13:03] <mivoligo> nik90: yes, it will be something like this, today I'm limited with time but hopefully tomorrow I'll show you the code
[13:04] <nik90> mivoligo: take your time.
[13:05] <mivoligo> nik90: one more think, about when you can't set an alarm if it's later than the alarm time
[13:06] <nik90> mivoligo: I think you mean "earlier" than the alarm time
[13:06] <mivoligo> nik90: right
[13:07] <mivoligo> nik90: maybe instead of showing the error better to set the alarm for next day?
[13:08] <nik90> mivoligo: But in the alarms page, the alarm day is also shown. So if the user has chosen "Monday", shouldn't the alarm be created 7 days later next monday?
[13:09] <nik90> mivoligo: but I agree with your idea that instead of showing an error, we should automatically move the alarm to tomorrow or the next week monday
[13:09] <mivoligo> nik90: I guess it'd need opinion from Canonical designers
[13:09] <nik90> mivoligo: +1
[13:09] <nik90> mivoligo: I will try finding out
[13:17] <mivoligo> nik90: ok, thanks. Speaking of design, in the preset alarms, can you move the alarm name to the left and alarm time to the right before on/off switch. That way it will be consequent across the app (timer presets, world clock) and aligned nicely :)
[13:17] <nik90> mivoligo: yeah I was just thinking of that now. I was just not sure on where to place the switch.. But yes I will do that
[13:18] <aquarius> nik90, nice u1db g+ post. :)
[13:18] <nik90> aquarius: thnx :)
[13:19] <nik90> aquarius: we need to find people to review those u1db-trunk branches...they bring in some nice fixes :)
[13:19]  * nik90 is annoyed that he doesn't know much c++ to help there
[13:19] <aquarius> nik90, yeah, that's why I filed the bugs about them. kalikiana_ asked if I could, but I am no C++ person.
[13:20] <nik90> aquarius: yeah he asked me as well :/
[13:25] <aquarius> best thing would be to bridge the python u1db implementation's test suite so that it can be run against the qml implementation; it is massively comprehensive
[13:25] <aquarius> but that's a lot of complicated work which requires someone with a lot of time who knows qt/c++ and python well, and I'm not sure there's anyone who knows all that stuff and has the time :(
[13:26] <nik90> true
[13:26] <nik90> aquarius: btw I saw your chat with kalikiana_ regarding the u1db query. Is it safe for me to use it now for the clock app?
[13:27] <nik90> aquarius: I would need it to store and retrieve the timer presets using dynamic U1db document creation.
[13:27] <aquarius> nik90, well. I think it's safe *if* those fixes are merged and released and in the phone...
[13:28] <aquarius> I do not know what the release schedule on these things is...
[13:28] <aquarius> or whether querying works now. :(
[13:28] <nik90> aquarius: ah okay..so I just need to ensure that u1db is updated on phone before updating clock
[13:28] <aquarius> I would experiment with it first, if I were you
[13:28] <aquarius> confirm that it does what you're expecting it to do
[13:29] <nik90> yeah I can do that. I am not doing complicated querying by name..just querying by type "Timer" or "Alarm" etc etc
[13:29] <aquarius> I can probably cover what u1db is *supposed* to do, so if you write some code and it doesn't do what you want, I can probably say whether that's because you're doing the right thing and there's a bug or that you're not quite doing the right thing, if that would help
[13:29] <aquarius> ya
[13:30] <nik90> okay. I will let you know when I finish the transition
[13:33] <aquarius> you can work around the problem of not indexing top-level fields by having your docs be { typedata: { type: "Alarm" }} or something, which is annoying but will at least work without the fixes.
[13:34] <nik90> ok
[13:56] <om26er_> boiko, hey! can you give me tests branch a review ?
[13:56] <om26er_> https://code.launchpad.net/~om26er/dialer-app/add_new_tests/+merge/202732
[14:21] <kalikiana_> nik90: this branch includes the top-level element issues, if you'd like to test it https://code.launchpad.net/~kalikiana/u1db-qt/queryLog/+merge/204327
[14:27] <nik90> kalikiana_: I will test it when I get home. I should also be able to review the example included in that MP :) and let you know if it helps.
[14:27] <kalikiana_> that would be awesome
[16:57] <shailesh> hi
[16:58] <shailesh> i  need a help to devaploe
[17:56] <seb128> could somebody told me what is wrong in http://paste.ubuntu.com/6868420/ ?
[18:04] <WebbyIT> seb128, your column has no height, add anchors.fill: parent
[18:07] <seb128> WebbyIT, columns are not supposed to have an height afaik, that code works if you comment the expanded property
[18:08] <seb128> WebbyIT, or if you stack another object
[18:08] <seb128> WebbyIT, e.g if you use a ListItem.Standard it works fine
[18:09] <WebbyIT> mhh
[18:35] <qtros> popey ping
[18:40] <popey> qtros: hey
[18:41] <qtros> popey hello! :) How are you?
[18:41] <popey> fine thanks. am in florida at a sprint, in meetings, so my replies may be delayed
[18:41] <popey> wassup?
[18:48] <qtros> popey sorry for afk )
[18:49] <qtros> popey I am working on https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1267869
[18:49] <ubot2`> Launchpad bug 1267869 in Ubuntu RSS Feed Reader App "List view takes up too much space, split" [Undecided,New]
[18:49] <qtros> popey and I found bug in sdk related with toolbars
[18:50] <qtros> popey I can provide simple example to reproduce it
[18:50] <qtros> popey I am writing to you because my previous bug reports were skipped, no any activity by sdk team
[18:51] <qtros> popey but this bug is very old and so critical for RSS Reader
[18:51] <popey> qtros: ok. the sdk team are here with me, I'll see if i can get someone to take a look
[18:52] <qtros> Popey so I should file a bug and provide url to you? :)
[18:52] <popey> sure, if you have one
[19:00] <qtros> popey here you are https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1275877
[19:00] <ubot2`> Launchpad bug 1275877 in Ubuntu UI Toolkit "Two pages in one Tabs - toolbar issue" [Undecided,New]
[19:00] <qtros> popey have a good time :)
[22:46] <ahayzen> elopio, ping
[22:46] <elopio> ahayzen: hey, hello
[22:46] <ahayzen> elopio, u said to update the copyright in Empty.qml
[22:47] <ahayzen> elopio, should i change it to 2012-2014 .. or just 2014?
[22:47] <ahayzen> or 2012,2014
[22:47] <ahayzen> elopio, in this merge https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-002/+merge/202171
[22:49] <elopio> ahayzen: the correct way according to the fsf would be 2012, 2013, 2014, if the file was touched on all of those years.
[22:49] <ahayzen> elopio, hmm was it changed in 2013 lol?
[22:49]  * ahayzen tries to remember when he last changed it
[22:50] <ahayzen> elopio, my previous work was right at the end of 2013 start of 2014 https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-001/ ... wht should i put?
[22:51] <elopio> ahayzen: bzr blame helps for this. Let me check.
[22:53] <ahayzen> elopio, it appears to have changed in 2013 according to lp http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/changes?filter_file_id=base.qml-20120713093335-wm10clvau8hcagow-1
[22:54] <elopio> ahayzen: yes, so please put 2012, 2013, 2014
[22:54] <ahayzen> elopio, cool :)
[22:55] <elopio> it might not be important, but copyright is a mess, and 99% of the lawyers are bad people. Maybe it's better to do it as they recommend :)
[22:55] <ahayzen> elopio, hehe done it :)
[22:55] <elopio> ahayzen: about the failure, is my comment understandable?
[22:56] <ahayzen> elopio, i'm hoping i have fixed the issue...but i'm awaiting my trusty VM to update itself
[22:56] <ahayzen> elopio, yep ur comment made sense thanks :)
[22:56] <elopio> ahayzen: cool, let me check to learn a bit more about qml.
[22:56] <ahayzen> elopio, i suddenly realised wht u were meaning
[22:57] <ahayzen> elopio, i've changed it so tht the waitingforconfirmation flag is changed after the animation is complete
[23:00] <elopio> ahayzen: it still fails here.
[23:00] <ahayzen> elopio, damn :/
[23:01] <elopio> ahayzen: do you know how to run the tests? It's a little tricky.
[23:01] <ahayzen> elopio, i'm nearly there with the VM so if it fails on mine then i'll have a better chance at fixing
[23:01] <ahayzen> elopio, do u just do $ autopilot run ubuntuuitoolkit.tests.test_emulators.SwipeToDeleteTestCase ?
[23:02] <elopio> ahayzen: this is what I do to run them:
[23:02] <elopio> $ qmake
[23:02] <elopio> $ make
[23:02] <elopio> $ source export_modules_dir.sh
[23:02] <elopio> $ cd tests/autopilot/
[23:02] <elopio> $ autopilot run ubuntuuitoolkit.tests.test_emulators.SwipeToDeleteTestCase.test_delete_item_moving_left
[23:02] <ahayzen> elopio, ah u have to build it
[23:03] <elopio> ahayzen: yes, and if you don't do the source export... you will be using the installed one.
[23:03] <elopio> an alternative is to build the deb, and install it, but that's slower for me.
[23:03] <ahayzen> elopio, 'Unknown module(s) in QT: organizer'
[23:03] <ahayzen> elopio, wht dependencies do it need?
[23:04] <elopio> ahayzen: ah, right, sorry: $ sudo apt-get build-dep ubuntu-ui-toolkit
[23:06]  * nik90 reads intently...
[23:06] <nik90> I have been meaning to also build ui-toolkit for a long time
[23:06] <elopio> ahayzen: shouldn't this be the opposite?
[23:06] <elopio> 35	+ if (x !== 0) { // waiting if not at 0 pos
[23:06] <elopio> if x == 0, commit the drag.
[23:07] <ahayzen> elopio, maybe
[23:07] <ahayzen> elopio, but if u look where it was before it was after body.x = finalX
[23:07] <elopio> nik90: the README file is pretty decent, there's some extra details you might find interesting.
[23:08] <elopio> ahayzen: well, I really don't know what I'm talking about :)
[23:09] <ahayzen> elopio, well it fails for me in the VM so at least i can work on it :)
[23:09] <nik90> elopio: thnx
[23:10] <elopio> nik90: about your branch in the clock, we could copy the textfield emulator there while it gets released on the toolkit. Or we could wait, your choice.
[23:10] <nik90> elopio: if we wait, how long would that be?
[23:11] <elopio> nik90: In the ideal case, no more than a week.
[23:11] <elopio> but things can go wrong.
[23:11] <nik90> elopio: I think that's fine. The emulator is already in the PPA. So I will continue my test refactor with that and test on my local machine
[23:12] <nik90> elopio: we can then merge when it is released
[23:12] <elopio> nik90: sounds good.
[23:13] <ahayzen> nik90, o/
[23:14] <nik90> ahayzen: hi :)
[23:14] <ahayzen> nik90, appears u beat me to U1DB support lol :)
[23:14] <nik90> ahayzen: lol
[23:14] <nik90> ahayzen: although this is only 30% of all the storage needs of clock app
[23:14]  * ahayzen hasn't checked if things have been patched upstream yet
[23:15] <nik90> ahayzen: it hasnt
[23:15] <ahayzen> :(
[23:15] <nik90> ahayzen: but I am testing one of those MP for kalikiana
[23:15] <nik90> ahayzen: if it passes, it might go in :)
[23:15] <ahayzen> nik90, i might attempt to add sorting if no one else does as recent items would work if tht lands
[23:15] <ahayzen> nik90, ooo u got a link?
[23:16] <nik90> ahayzen: https://code.launchpad.net/~kalikiana/u1db-qt/queryLog/+merge/204327
[23:16] <ahayzen> nik90, so tht would fix the issues i'm having with playlists correct?
[23:17] <nik90> ahayzen: yup :D
[23:17] <nik90> ahayzen: so pls test it as well
[23:18] <ahayzen> nik90, awesome :) if sorting was done then tht would be awesome
[23:18] <nik90> ahayzen: more testers means more probability that the MP is approved
[23:18] <ahayzen> nik90, i'll take note and comment if i find any issues
[23:18] <ahayzen> nik90, cool will do :)
[23:18] <nik90> ok
[23:18] <ahayzen> nik90, how do u test tht one? build it to replace the current then run a test app?
[23:19] <nik90> ahayzen: or you could grab the deb file from the jenkins comment and install it on your system
[23:19] <ahayzen> nik90, thts sounds simpler :)
[23:19] <nik90> ahayzen: if you reinstall the package, it will downgrade it to the older version
[23:19] <ahayzen> nik90, i'll have a crack at tht after dinner
[23:19] <nik90> revert*
[23:19] <nik90> ahayzen: ok