/srv/irclogs.ubuntu.com/2015/06/14/#ubuntu-app-devel.txt

ahoneybunhey all how do you use flickable with columns?02:39
melesmhall119: you are the maintainer of ubuntu-calendar-app. right?08:00
DanChapmanmeles, IIRC kunal and mihir are the main developers working on calendar.08:05
nik90meles: ping09:42
awadhi11:21
meleshey nik90 i just saw it now13:02
melesnik90 any progress?13:03
melesnik90 GOT IT!13:23
nik90meles: can you test the click package on your phone and see if it fixes the bug13:24
melesmy patch: http://paste.ubuntu.com/1171408913:26
melesnik90 ^ where is the click package13:26
nik90meles: I added a comment in the bug report with the click package13:27
melesnik90: ok13:28
melesnik90 the app fails to open13:37
nik90meles: eh?13:40
nik90meles: which device image are you running?13:40
nik90meles: I built it against a vivid 15.04 image. Are you running BQ with 14.10 instead?13:40
melesnik90 splash screen is appearing and than it crashes. I'm running 14.10 indeed13:41
nik90meles: that's why it doesn't open for you..its compiled to work on 15.04 and not 14.10 considering that OTA-4 will be released tomorrow which is based on vivid :)13:42
melesnik90 i m building it myself13:42
nik90meles: rest assured, let me build it for 14.10 and send you the click package if you want13:42
nik90meles: ok..ping me if you hit any issues and I can send it to you if required13:42
melesnik90 ping13:52
nik90meles: i'm here13:52
melesnik90 no the fix does not work. but I have to say that I have a special issue. Since I changed the date so many times for testing purposes I had some alarms created at a future date. Reactivating this alarms makes them just go off at the day they were originally created. My fix considers this problem. Can you test it? I can push it if you want.13:54
nik90meles: would the phone issue change their date and go backwards though?13:55
nik90meles: can you upload your fix into a branch that I can grab and test quickly?13:55
melesnik90 no normally not but who knows :-)13:56
melesok otw13:56
nik90meles: fair enough13:56
melesnik90 ok it's up14:03
melesnik90 lp:~themeles/ubuntu-clock-app/bugfix-144251814:04
* nik90 tests now14:06
nik90meles: yup your patch works better14:11
nik90nice work!14:11
meles:-)14:12
nik90meles: just requires 2 minor code fixes, 1) Better variable names 2) add an entry to the debian changelog14:13
melesnik90 just might have to rename the variables a bit, since they are pretty bad14:13
nik90:)14:13
nik90meles: if you look at https://code.launchpad.net/~nik90/ubuntu-clock-app/fixes-1442518/+merge/261905, you will see the debian changelog entry I used14:14
nik90ofcourse add your own name to the entry14:14
melesnik90 ok i fix it14:14
nik90meles: Why do you do var tdate2 = new Date(d.getFullYear(),d.getMonth(),d.getDate()+1,alarmData.date.getHours(),alarmData.date.getMinutes(),0,0) instead of d.setDay(d.getDate()+1) ?14:20
nik90is it to set the minutes and seconds to 0?14:20
melesnow because i coud not get the other variant working14:21
melesnik90 no because i coud not get the other variant working14:22
nik90other variant?14:25
melesnik90 the one u suggested14:25
nik90ah ok14:26
melesnik90 i pushed the new code and entered the information suggested. Is there anything more neccessary14:30
nik90meles: sec, taking a look14:31
nik90meles: two things...update debian changelog and also specify a commit msg to the merge proposal you created14:32
meleswhere do i change the debian changelog14:35
nik90meles: nano debian/changelog14:35
nik90meles: one other thing..the two variables "currentTime" and "now" are redundant..you just need one of them14:40
melesnik90: you are right. I stick with now, I think its easier, even though the other was used before. ok?14:41
nik90meles: fine by me14:42
melesnik90: ok i think now its complete14:44
* nik90 checks14:45
nik90meles: commented in the MP proposal.14:50
melesnik90 MP?14:51
melesI have to go now urgently, i ll be back later14:51
nik90meles: ok..you should have got an email about the merge proposal14:51
nik90meles: tty later14:51
meleshey nik90, thanks for your comments. I changed it as you suggested. I hope it's good to merge now. If not let me know.17:19
nik90meles: they look good now. I am going to test this for a 2-3 days to ensure that we didn't miss out any rare cases where the bug might reappear. I would recommend you do the same.17:21
nik90meles: and then I will merge it and try to include it in our release after OTA-417:22
nik90popey, balloons: Could either of you trigger jenkins on https://code.launchpad.net/~themeles/ubuntu-clock-app/bugfix-1442518/+merge/261910 pls. thnx17:22
nik90meles: I approved the merge proposal. Will merge in a few days after I finish testing it.17:23
melesnik90 allright I will. I'm very glad that I had your great support!!! Maybe I can contribute to some other bugfixes now, which might make the planed selling of my phone obsolete. :-)17:25
nik90meles: you made the bug fix possible..so a huge thanks to you! And yes feel free to contribute to other bug fixes that grab your attention.17:26
nik90meles: be sure to assign the bug to yourself on launchpad before starting to work on it since otherwise we might have multiple people working on the same thing.17:28
melesnik90 actually there is even one that annoyed me quite a bit at the beginning. It's Bug #1437316. And I would agree to racb's comment, to make the off button red and the snooze green.17:32
ubot5bug 1437316 in Ubuntu UX "[Clock] Too easy to accidentally turn off the alarm instead of snoozing" [Undecided,Triaged] https://launchpad.net/bugs/143731617:32
* nik90 looks at the bug report17:32
nik90meles: that bug report is a bit off scope at the moment since it is not the clock app that draws the notification on the screen. Indicator-datetime does at while using the unity8 notification framework.17:33
nik90meles: also it requires feedback from the design team before proceeding to fix it.17:34
nik90I do agree to the bug report as stated in the first comment there17:34
nik90meles: the bugs which are listed in https://launchpad.net/ubuntu-clock-app/+milestone/3.x.backlog are usually blocked atm by things like design, platform limitation etc.17:35
melesnik90 ok I understand. I will see what else I could do.17:38
popeynik90: I am not sure I know how to manually trigger, so gave it a go. lets see if it works17:55
popeynik90: http://91.189.93.70:8080/job/ubuntu-clock-app-ci/17:55
nik90popey: ack.18:00
melesnik90 my alarms don't trigger any sound or vibration anymore, they just pop up. Does it work on your system18:00
popeythanks for the contribution meles !18:00
nik90meles: for me it triggers sound and vibration even after installing your patch. I tested this on my Nexus 4 running 15.0418:02
melespopey: no prob. I'm happy that I could contribute and that I got great support!18:02
nik90meles: good news is that jenkins ran the autopilot and qml tests and found no regressions in your patch! It will be merged in 2 days after we both are confident of the bug fix.18:04
popeywoah! My random button pressing worked!?18:05
popeysweet18:05
nik90haha ;)18:05
melesnik90 is there somewhere a proper how to about how to fix and commit a bug, if not I would work on an easy to read summary18:30
nik90meles: https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide18:31
melesand about Ubuntu SDK, like how to open the project (CMakeList.txt).18:32
melesnik90 ^18:32
nik90meles: well stuff like how to run an app, build it for the phone etc are all documented at developer.ubuntu.com18:33
nik90meles: it is common knowledge that cmake projects are opened via the CMakeList.txt file, qmake via .pro etc18:33
melesnik90 not to everybody and without your help i might have just given up.18:35
nik90meles: We could make the core apps contribution guide a bit more descriptive by include such info and for further info redirect the to the official documentation pages?18:36
melesnik90: yes would limit the step to join. And I also think that there is to much text, when I want to check something out I want to get quickly through it. E.g http://paste.ubuntu.com/11715854/18:45
nik90meles: well yes some pictures would come in handy to explain it in a more intuitive manner18:48
popeyI have an item on my to-do to improve the on-ramp for new developers nik90 meles19:00
nik90popey: did you have any particular idea/mockup on how to improve it?19:03
popeythe idea was to have a pretty home page for each app19:03
popeyand a general page for all the cross-app info19:03
popeyand move the content off the wiki19:03
popeyno mock ups yet19:04
nik90off the wiki?19:05
nik90dedicated homepages/website for each app?19:05
popeyyeah, move it to developer.ubuntu.com19:05
popeyyes19:05
popeypage per app19:05
popeywith links to where the source is, bitsize bugs, planning docs etc19:06
nik90ah19:06
melespopey nik90 i was on the phone. I think developer.ubuntu.com would be the better place since this was also where I was looking for such info. but couldn't the quick start guide be quicker to read. All the info but less text.19:24
popeythanks for the feedback19:24
popeyI agree19:24
nik90+119:28

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!