15:00 <popey> #startmeeting Calculator app meeting
15:00 <meetingology> Meeting started Thu Apr 16 15:00:24 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
15:00 <meetingology> 
15:00 <meetingology> Available commands: action commands idea info link nick
15:00 <gang64> Hi
15:00 <popey> how are you guys?
15:00 <rpadovani> o/ good enough, thanks
15:00 <rpadovani> what about you?
15:00 <popey> Super!
15:00 <popey> Great!
15:01 <popey> I have some good news.
15:01 <gang64> great, thanks!
15:01 <popey> meet JMulholland who is a UX designer at Canonical.
15:01 <popey> He's been tasked with providing us design support.
15:01 <popey> (and all the core apps)
15:02 <popey> (he may be in another meeting right now though)
15:02 <popey> So, for an desi
15:02 <JMulholland> Hihi, just got in :)
15:02 <popey> .. design related bugs - add a task for ubuntu-ux and JMulholland can take a look and provide feedback
15:02 <rpadovani> Hi JMulholland nice to meet you :-)
15:02 <rpadovani> That's a great news!
15:02 <JMulholland> nice to meet you too
15:02 <JMulholland> :)
15:03 <gang64> Hi. Nice to meet you
15:03 <popey> We recently replaced the calculator in the default image with the new reboot iteration
15:03 <gang64> Maybe next time we will setup hangout session :-)
15:03 <popey> yeah.
15:03 <popey> gang64: you had some things to discuss..
15:04 <popey> https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1444564 being the first, right?
15:04 <gang64> yes
15:04 <popey> I must say I didn't find it as hard as the reporter...
15:04 <popey> But I imagine it must be frustrating when it happens
15:05 <popey> So, suggestions welcome!
15:05 <rpadovani> indeed, it happens, but not so ofter
15:05 <rpadovani> *often
15:05 <rpadovani> maybe we should enable bottom edge exposure only from the label itself, and not from all the bottomedge?
15:06 <gang64> But reveal from bottom edge is common design for Ubuntu Touch
15:07 <rpadovani> that's true
15:07 <popey> and there are still buttons in the middle
15:07 <gang64> exactly
15:07 <rpadovani> I'm quite sure it happens more often with bq due the resolution than with others phones
15:07 <popey> one option would be to "lift" the keyboard up a bit, leaving a gap at the bottom
15:07 <popey> smaller hit target, yes.
15:08 <gang64> Frankly I don't like lifting
15:08 <gang64> At the end we will l need border for every edge
15:08 <gang64> How it is working for left/right swipe?
15:09 <gang64> left and right edge ?
15:09 <popey> well, we could argue this is an sdk issue
15:09 <popey> it shouldn't detect presses as off-screen to on-screen swipes
15:09 <gang64> There should be also the same problem
15:10 <rpadovani> gang64, it doesn't happen. I don't know how, but seems Unity is more intelligent
15:10 <gang64> Could you please check if the same issue is when you try click near the right/left edge ?
15:10 <gang64> ok
15:10 <gang64> i know !
15:11 <gang64> For swiping you don't release touch
15:11 <gang64> for clicking you release tocuh
15:11 <popey> hm
15:12 <gang64> So:
15:12 <gang64> If you would like to swipe from bottom edge, you should release minimum 40 px away
15:12 <popey> i asked mzanetti to join us
15:13 <popey> mzanetti: context https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1444564
15:13 <popey> basically tap events at bottom edge are triggering swipe up in calculator
15:13 <gang64> If you would like to swipe from bottom edge, you should press at the bottom and release minimum 40 px away from edge
15:13 <popey> makes hitting buttons at the bottom hard
15:13 <mzanetti> gang64, how come 40px?
15:13 <popey> we note unity (dash) doesn't seem to suffer this way when tapping near the edge
15:13 <mzanetti> right :)
15:13 <popey> do you have some smarts in unity / toolkit / dash somewhere for that?
15:14 <mzanetti> right now in unity. called DirectionalDragArea
15:14 <mzanetti> however, we're preparing to upstream that component to the sdk
15:14 <rpadovani> and that's is the solution :-) Thanks mzanetti
15:14 <gang64> mzanetti: 40px it was example
15:15 <JMulholland> hi Michael, and thanks :)
15:15 <popey> mzanetti: ETA ?
15:15 <JMulholland> just tried it out in landscape on my meizu, seems to be the same probelm there so it’s not BQ specific
15:15 <mzanetti> it'll still be a while until that lands though... We will merge some API improvements early next week.
15:16 <mzanetti> after that we'll propose the whole thing to the SDK people
15:16 <JMulholland> (newly styled calculator looks great by the way :))
15:17 <rpadovani> :-) thanks
15:18 <popey> So it doesn't seem sane for us to work around this (unless it's simple and low-impact) but wait for SDK component to "fix" it for us? :)
15:18 <rpadovani> gang64, popey ok let's say we wait the upstream component for this one. What's next?
15:18 <popey> thanks mzanetti
15:18 <mzanetti> popey, I would like to say yes, but again, it might be still a while
15:18 <mzanetti> but I suppose a workaround shouldn't be too hard
15:19 <gang64> Topic 2. Do we need to switch to BigNumbers (math.js)?
15:19 <popey> if someone has time, and we feel its worthwhile, i.e. sufficiently annoying to more users, yeah.
15:19 <popey> gang64: what's the issue here?
15:20 <gang64> As I remember there was some issues with rounding:
15:20 <gang64> (1/3)+(2/3)=0.99999998
15:20 <gang64> Something like that
15:21 <gang64> In previous calculator we have used BigNumbers
15:21 <mzanetti> close enough :D
15:21 <gang64> I just wondering if it is worth of efford
15:22 <gang64> I will investigate it further and create tickety for that
15:22 <popey> ok
15:22 <popey> great
15:22 <rpadovani> It's a bit slower, but I think yes. The problem is: Jenkins fails when we switch to BigNumber, and I don't understand where is the issue
15:23 <gang64> ok
15:23 <gang64> I will ask math.js dev eloper about that
15:23 <popey> it works on phone and fails on desktop?
15:23 <gang64> It is failing also on desktop
15:24 <rpadovani> yap, that's the strange
15:24 <rpadovani> but the calculator works
15:24 <popey> but autopilot passes on the device?
15:24 <gang64> I will ask math.js developer
15:24 <popey> ok
15:24 <gang64> Can we switch to topic 3 ?
15:24 <popey> would be good to narrow down exactly where it fails.
15:24 <popey> yes :)
15:24 <gang64> Topic 3. Calculator's Convergence:    -  What needs to be done to enable Calculator as default Calculator on Ubuntu 15.10?
15:24 <gang64> Is it even possible ?
15:25 <popey> handy having mzanetti here
15:25 <gang64> :-)
15:25 <popey> mzanetti: What are we going to expose to apps, to let them know when a pointing device is there, or a keyboard is there?
15:25 <popey> As I understand it we're not thinking in terms of phone / tablet / desktop
15:26 <popey> but the apps / desktop need to behave differently based on a set of circumstances...
15:26 <popey> "is there a pointing device present?" "is there a keyboard?" etc
15:27 <gang64> yes
15:27 <gang64> What is screen size ?
15:27 <popey> Exactly.
15:27 <popey> Some of this may not yet be decided.
15:27 <gang64> The most important : Is is run in windowed mode
15:28 <gang64> ?
15:28 <popey> I am going to be in London next week at a Desktop sprint, where I think we will be discussing some of these items.
15:28 <JMulholland> yea convergence is an interesting set of challenges
15:28 <gang64> Should I create bug report about that ?
15:28 <JMulholland> touch vs pointer vs key input
15:28 <gang64> But it is not a bug :-)
15:29 <JMulholland> and single focus (phone etc) vs windowed environment
15:29 <JMulholland> none of which are mutually exclusive
15:29 <popey> its a wishlist enhancement (bug)
15:29 <gang64> ok
15:29 <popey> I dont think we have the details nailed down yet.
15:30 <popey> I'll see what comes out of the sprint next week (I expect something) and feedback to you guys.
15:30 <rpadovani> sounds great
15:30 <gang64> What about creating BluePrints or something ?
15:30 <mzanetti> popey, good question... We're working on a QML api for it
15:31 <mzanetti> but also that is quite a bit away still
15:31 <popey> ok.
15:31 <popey> gang64: glad you mentioned blueprints. :)
15:31 <popey> gang64: rpadovani http://summit.ubuntu.com/uos-1505/
15:31 <popey> we should create a session for UOS which is 5-7 may.
15:31 <mzanetti> popey, https://code.launchpad.net/~mzanetti/ubuntu/vivid/qtsystems-opensource-src/inputinfo
15:32 <popey> to talk about these things and plan out exactly these features
15:32 <rpadovani> \o/
15:32 <rpadovani> Thu & May at this hour, to replace weekly meeting? Should work for all :-)
15:33 <popey> yes, makes sense
15:34 <popey> rpadovani: gang64 I'll reply to your mail and we can setup a session.
15:34 <popey> ok, we're overrun .. Anything else?
15:35 <gang64> mzanetti: Could you please add comment to https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1444564
15:35 <rpadovani> popey, for me it's all
15:35 <gang64> regarding to bottom edge solution ?
15:37 <gang64> thanks
15:37 <JMulholland> good meeting you rpadovani & gang64!
15:38 <popey> thank you!
15:38 <gang64> Have a nice Evening.
15:38 <rpadovani> see  you guys :-)
15:40 <popey> #endmeeting