17:00:26 <popey> #startmeeting Ubuntu Touch Calculator App meeting
17:00:26 <meetingology> Meeting started Thu Apr 11 17:00:26 2013 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
17:00:26 <meetingology> 
17:00:26 <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
17:00:32 <popey> who's here?
17:01:55 * popey pokes mhall119 & rferrazz
17:03:32 <boiko> hmm :/
17:03:34 * popey taps the mic
17:03:39 <popey> is this thing on?
17:03:57 <boiko> popey: I can hear the mic :)
17:05:03 <popey> ok, lets start..
17:05:19 <popey> some handy links for the minutes...
17:05:25 <popey> blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-calculator-development
17:05:31 <popey> bugs: https://bugs.launchpad.net/ubuntu-calculator-app
17:05:38 <popey> reviews: https://code.launchpad.net/~ubuntu-calculator-dev/ubuntu-calculator-app/trunk/+activereviews
17:05:55 <popey> boiko: I understand you've taken a look at the code?
17:05:58 <popey> any concerns?
17:06:37 <boiko> popey: so yes, I took a look at the code, no real concerns for now, there is certainly room for improvement though
17:06:59 <boiko> I have reported some entries in the blueprint already, and one bug I found (which rferrazz fixed already, btw)
17:07:05 <popey> sweet
17:07:21 <popey> is it all stuff specific to the calculator app or in general that our other app devs may need help with?
17:07:24 <boiko> I have also written two autopilot tests for the bugs that got fixed to serve as example for writing more tests
17:07:58 <popey> can you link to the branch & bugs for me?
17:08:10 <boiko> nope, it is more specific to the calculator apps, like some hints on doing things a different way in QML, or better using some components from SDK, etc
17:08:20 <boiko> yes, sure, finding the bugs and the MR
17:08:24 <popey> ta
17:08:56 <boiko> popey: this is the MR (placed against rferraz's fix): https://code.launchpad.net/~boiko/ubuntu-calculator-app/add_tests_for_new_formula/+merge/158227
17:09:23 <daliusd> hi
17:09:42 <boiko> and bugs: https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1164973
17:09:48 <boiko> https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1165894
17:09:51 <boiko> hi daliusd
17:09:52 <popey> hi daliusd
17:10:38 <boiko> popey: that's it from my side
17:10:56 <popey> thanks boiko
17:10:59 <popey> hows it going daliusd ?
17:11:10 <daliusd> Everything is fine :)
17:11:27 <daliusd> trying irc client from command line
17:11:39 <popey> irssi, the only true irc client ? ☻
17:11:43 <daliusd> how it is going for you?
17:11:55 <popey> great, happy to be playing with the app on a device..
17:12:03 <popey> just looking through the work items...
17:12:03 <popey> https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-calculator-development
17:12:21 <popey> one week till end of milestone 0
17:12:50 <popey> we have a few "TODO" and "INPROGRESS" items.
17:12:59 <boiko> btw, I added items to the milestone 0, I should have added to the Work items section in the end, let me edit that
17:13:21 <daliusd> boiko, edit it and let's look what will left
17:13:28 <boiko> done
17:13:43 <daliusd> popey, maybe you have tested that bug with keyboard size on real device ?
17:14:15 <popey> daliusd: which bug?
17:14:31 <popey> https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1156523 that one?
17:14:45 <daliusd> https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1156523
17:14:52 <daliusd> Yes :)
17:15:07 <popey> it looks much better
17:15:13 <popey> let me get a screenshot and add to the bug now
17:15:23 <daliusd> Please do it :)
17:15:33 <daliusd> while I suspect how it will look like but do it anyway
17:15:37 <daliusd> for design team to see
17:16:20 <popey> https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1156523/+attachment/3640935/+files/device-2013-04-11-181537.png
17:16:38 <daliusd> About other tasks from blueprint: [popey] Get final visual design: TODO - maybe this should be moved outside of this milestone
17:16:55 <popey> yes, i agree, I'll move it - we're blocked on design
17:17:00 <daliusd> popey, looks better than I have expected :)
17:17:16 <popey> done
17:17:19 <popey> ☻
17:17:36 <daliusd> not sure what to do with mhall119 bugs
17:18:13 * boiko added one more item to the Work items section
17:18:14 <popey> hmm, its a bit sluggish on the device
17:18:22 <daliusd> boiko, what views?
17:18:23 <popey> I suspect that's not the fault of the calculator but the platform
17:18:49 <mhall119> daliusd: which bugs?
17:18:50 <daliusd> popey, slugish or stattering (damn not sure what's correct word in English)
17:19:00 <boiko> daliusd: Simple, Scientific, etc
17:19:06 <daliusd> [mhall119] Fix packaging bugs (1153787 & 1155969): TODO
17:19:13 <popey> If I stab the buttons repeatedly, quickly, it doesn't react
17:19:32 <popey> Hmm, C doesn't work how i'd expect
17:19:37 <popey> it acts like "undo"
17:20:15 <mhall119> daliusd: the first I believeis corrected or being corrected by the SDK tema
17:20:26 <daliusd> popey, we need Riccardo input on C
17:20:29 <mhall119> the second is part of a larger package change that'll be coming soon (maybe today) from me
17:20:44 <daliusd> mhall119, please close if that's the case as I have no idea :)
17:20:51 <popey> hmm
17:20:59 <mhall119> daliusd: I'll double check then close
17:21:35 <daliusd> popey, about buttons not reacting: I would bet on platform as those are simple mouseareas
17:21:40 <daliusd> popey, but there is another option
17:22:07 <daliusd> popey, I have seen problem on BB10 but not on Symbian and Meego that might affect Ubuntu Phone
17:22:10 <daliusd> try following
17:22:14 <boiko> daliusd: btw, I think we should use Button from SDK for the buttons, even if the visuals are different
17:22:17 <daliusd> press button and move your finger
17:22:27 <daliusd> I wonder if button will lose pressed state
17:22:40 <popey> it does
17:22:55 <mhall119> daliusd: boiko: is it performing any calculations still on button press, or does it delay that until = is pressed?
17:22:56 <daliusd> popey, how sensitive is it
17:22:57 <daliusd> ?
17:23:02 <daliusd> I guess that's the problem
17:23:05 <popey> only need to move a tiny bit
17:23:50 <boiko> daliusd: popey: I might be wrong, but I think we get a fix for that if we switch to use Button from SDK
17:23:56 <daliusd> popey, maybe that's the problem
17:24:02 <boiko> daliusd: popey: that's what I am using for the dialer in phone-app
17:24:05 <popey> maybe, i dont know. worth a try
17:24:12 <daliusd> boiko: most probably not but there is small chance
17:24:26 <daliusd> boiko: it is related to fact that button is in ListView
17:24:37 <boiko> popey: do you see the same problem in phone-app?
17:24:43 <boiko> daliusd: ah yes, that might indeed be
17:24:52 <popey> yes
17:25:02 <popey> only move a bit off a button and it un-hilights
17:25:16 <daliusd> I will fix that
17:25:16 <boiko> popey: great! then we can report the bug for SDK ;)
17:25:24 <popey> press (highlights) drag a tiny bit to the side, the screen moves
17:25:44 <popey> ok. some actions!
17:25:59 <popey> #action popey file bug about c not working quite right (undo)
17:25:59 * meetingology popey file bug about c not working quite right (undo)
17:26:14 <popey> #action popey file a bug on sdk about buttons not holding state while moving finger
17:26:14 * meetingology popey file a bug on sdk about buttons not holding state while moving finger
17:26:20 <popey> what else ?
17:26:24 <daliusd> popey,
17:26:29 <daliusd> I doubt that it is SDK buttons
17:26:33 <daliusd> we are using custom buttons :)
17:26:35 <boiko> daliusd: can you change the calc buttons to use Button from SDK? I can help with that to make it look custom
17:26:52 <daliusd> boiko: I can but they will look wrong
17:26:54 <boiko> daliusd: it is not, but then if we use SDK buttons we can report the problem there and get fixed for all apps ;)
17:26:58 <daliusd> are we OK with that?
17:27:15 <popey> daliusd: same happens in dialler
17:27:25 <daliusd> boiko: I have reported one bug before one month or something like that
17:27:50 <popey> let us have the bug number and we can push for an answer
17:28:16 <boiko> yep
17:28:36 <daliusd> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1152888
17:29:23 <popey> ok, thanks
17:29:32 <boiko> daliusd: ah ok, well, in phone-app we do something different: we set the class of the button to transparent, and then draw text and background by hand
17:29:44 <popey> #action popey get response for bug 1152888
17:29:44 * meetingology popey get response for bug 1152888
17:29:55 <popey> anything else blocking daliusd ?
17:30:00 <daliusd> boiko, what's the point of using button then?
17:30:51 <boiko> daliusd: to get the logic from the button (and not just using a plain mousearea), not sure if the code there for now is just a mousearea, but then if bugs like the one popey found get fixed, all apps get the fix
17:31:06 <boiko> daliusd: instead of having many custom buttons doing the same fix all over the place
17:31:30 <daliusd> I doubt that there is fix for such scenario
17:31:45 <daliusd> I have one idea how to fix that
17:32:00 <daliusd> but it is inefficient
17:32:05 <daliusd> not sure if there is efficient solution
17:32:21 <daliusd> while I agree with you
17:32:28 <boiko> daliusd: well, that bug (and that fix) specifically were just examples, the point is that if we get a robust button handling implementation in SDK, everybody benefit from it
17:32:42 <daliusd> Yes, I agree with you
17:33:30 <daliusd> How to set button class to transparent (in case it is not documented)?
17:33:53 <boiko> daliusd: ItemStyle.class: "transparent"
17:34:13 <daliusd> boiko, thanks :)
17:34:24 <popey> sweet, we're out of time, any further questions / blockers?
17:34:37 <boiko> I just have a question for daliusd
17:34:52 <boiko> daliusd: also about the buttons, any reason not to use QML Grid to layout them?
17:35:15 <daliusd> boiko: there are some buttons that are non-standard
17:35:26 <daliusd> "=" and "0"
17:36:07 <boiko> daliusd: ah yes, hmm, I think Grid had something for spanning items, I'll double check and get a solution for you
17:36:14 <daliusd> You can fix grid's column's or row's width/height
17:36:22 <daliusd> can't
17:36:51 <boiko> daliusd: probably not, but I think there is a way to span an item across two rows or two columns, that would be enough for the case here
17:37:06 <daliusd> boiko, maybe. I sometimes find that Qt Quick 2.0 has something handy I am not aware about :)
17:37:29 <boiko> daliusd: ok, I'll check that :)
17:37:45 <boiko> that's it from my side
17:38:03 <daliusd> I don't have anything to add as well
17:38:09 <daliusd> I think blueprint is covered
17:38:12 <popey> awesome. expect some new bugs soon
17:38:12 <popey> :D
17:38:19 <boiko> popey: I think we can wrap up the meeting
17:38:22 <daliusd> I hope Riccardo will handle his side
17:38:25 <popey> yup.
17:38:28 <popey> thanks guys
17:38:31 <popey> #endmeeting