== Meeting information ==
 * #ubuntu-touch-meeting: Ubuntu Touch Calculator app meeting, 13 Jun at 17:02 — 17:43 UTC
 * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2013/ubuntu-touch-meeting.2013-06-13-17.02.log.html]]



== Meeting summary ==

''LINK:'' https://code.launchpad.net/~dalius-sandbox/ubuntu-calculator-app/official-design 
''LINK:'' https://dl.dropboxusercontent.com/u/50603128/calculator_design_notes.pdf 
''LINK:'' https://dl.dropboxusercontent.com/u/50603128/Calculator_01.2.mp4 



== Vote results ==




== Action items ==

 * (none)



== People present (lines said) ==

 * daliusd (99)
 * popey (66)
 * boiko (11)
 * meetingology (3)



== Full Log ==


 17:02 <popey> #startmeeting Ubuntu Touch Calculator app meeting

 17:02 <meetingology> Meeting started Thu Jun 13 17:02:03 2013 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

 17:02 <meetingology> 

 17:02 <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:02 <popey> Some links...

 17:02 <boiko> hi guys

 17:03 <popey> blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-calculator-development

 17:03 <popey> bugs: https://bugs.launchpad.net/ubuntu-calculator-app/+bugs?orderby=-id&start=0

 17:03 <popey> reviews: https://code.launchpad.net/ubuntu-calculator-app/+activereviews

 17:03 <popey> burndown: http://status.ubuntu.com/coreapps-13.10/

 17:03 <popey> So, how we doing?

 17:03 <daliusd> Basically this

 17:04 <daliusd> Got some input on design

 17:04 <daliusd> I have started applying design to app

 17:04 <daliusd> (you can see branch if you want to)

 17:04 <popey> ooh, show me ☻

 17:04 <daliusd> https://code.launchpad.net/~dalius-sandbox/ubuntu-calculator-app/official-design

 17:05 <boiko> that's nice

 17:05 <daliusd> Currently missing: text annotation icon and delete icon

 17:05 <daliusd> I don't like how design team propose to implement delete action

 17:05 <daliusd> I don't like that very much because they propose to show button to users

 17:05 <popey> what's the current proposal?

 17:06 <daliusd> one minute

 17:06 <daliusd> https://dl.dropboxusercontent.com/u/50603128/calculator_design_notes.pdf

 17:06 <daliusd> https://dl.dropboxusercontent.com/u/50603128/Calculator_01.2.mp4

 17:07 <daliusd> I will implement delete from history the way I think it should be done

 17:07 <popey> so 3rd image on page 3?

 17:07 <popey> (of the pdf)

 17:07 <daliusd> Yes

 17:08 <boiko> the swipe to delete thing?

 17:08 <daliusd> I will make "Drag further to Delete" and "Release to Delete"

 17:08 <daliusd> yes

 17:09 <popey> the video doesn't show delete

 17:09 <popey> did you expect it to?

 17:09 <daliusd> Video doesn't but 4th image in 3rd page shows buttons

 17:09 <boiko> that'll be a standard pattern across all apps I think

 17:09 <daliusd> boiko, buttons?

 17:10 <boiko> daliusd: the swipe to delete, not sure to show buttons

 17:10 <popey> i can see why the buttons are there

 17:10 <daliusd> swipe to delete is OK

 17:10 <popey> given the whole ui is swipe based, it would be quite easy to accidentally delete a calculation by swiping in from the left

 17:10 <popey> as swipe in from left is used to bring the launcher out

 17:11 <popey> you might be going for the launcher and accidentially delete your work

 17:11 <daliusd> So I can make it swipe by half screen from the left

 17:13 <popey> are they expecting it to stop there?

 17:13 <popey> do you have a video showing the delete swipe action?

 17:13 <daliusd> I don't

 17:13 <popey> hmm

 17:14 <daliusd> Whatever, I will do the way I think it should be done

 17:14 <popey> heh

 17:14 <daliusd> and somebody will need to test it with real device

 17:14 <popey> i have one, and can test

 17:14 <daliusd> Good :)

 17:14 <daliusd> So if you will say - no

 17:14 <daliusd> we will adapt design team proposal

 17:14 <popey> so if you want to ping me at any time with a branch I can test

 17:14 <popey> cool!

 17:14 <daliusd> Thanks

 17:14 <popey> np

 17:14 <daliusd> OK

 17:14 <daliusd> What else

 17:15 <daliusd> Keyboard

 17:15 <daliusd> video shows some cool stuff with keyboard

 17:15 <daliusd> that is not yet available through SDK

 17:16 <popey> swiping the keyboard left/right?

 17:16 <daliusd> yes

 17:16 <daliusd> and color of keyboard

 17:16 <daliusd> so I have contacted one person that I was advised to contact

 17:16 <popey> who was that?

 17:16 <daliusd> and he said that custom keyboard will be available in the future

 17:17 <daliusd> let me find it

 17:17 <daliusd> Thomas Moenicke

 17:17 <popey> ok

 17:17 <daliusd> I was not given any estimates

 17:17 <popey> I'll see if I can get some more detail

 17:17 <daliusd> but I basically have promise that it will be possible to have custom keyboard with context

 17:18 <daliusd> color override is planned as well but it is low priority as far as I understand

 17:18 <popey> yeah, the SDK guys are working pretty hard at the moment, so it's on the list with all the other things

 17:18 <daliusd> and some bad news

 17:18 <daliusd> video shows nice

 17:19 <daliusd> behavior when new operation starts

 17:19 <popey> i would expect some consistency in colours between the designs from design team

 17:19 <daliusd> when number scrolls slowly to top

 17:19 <daliusd> I have added that (3 lines of code)

 17:19 <daliusd> but that breaks tear-off of active calculation

 17:19 <daliusd> It feels like Qt Quick bug actually

 17:19 <daliusd> so I'm not sure what to do actually

 17:20 <popey> is that in your branch?

 17:20 <daliusd> No it is not in my branch

 17:20 <daliusd> I can say what to add into which file

 17:20 <popey> ok

 17:21 <daliusd> You should add

 17:21 <daliusd> Behavior on height {

 17:21 <daliusd> SequentialAnimation{

 17:21 <daliusd> NumberAnimation {

 17:21 <daliusd> duration: 50

 17:21 <daliusd> }

 17:21 <daliusd> }

 17:21 <daliusd> }

 17:21 <daliusd> before Divider

 17:21 <daliusd> or before> Behavior on x

 17:21 <daliusd> it doesn't really matter

 17:21 <daliusd> you will get nice behavior as in video

 17:22 <daliusd> but it will break swipe up to start new calculation

 17:22 <popey> maybe I added it wrong, it didn't break for mew

 17:22 <popey> -w

 17:22 <boiko> daliusd: is that inside a listview?

 17:23 <daliusd> boiko - yes

 17:23 <boiko> or is it a repeater?

 17:23 <daliusd> inside repeater in listview

 17:24 <boiko> daliusd: if it was just a listview, we could set the "add" transition on listview

 17:24 <daliusd> problem is that Behavior or animation somehow affects atYEnd of Listview

 17:25 <boiko> daliusd: not sure it is the case

 17:25 <boiko> daliusd: http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-listview.html#add-prop

 17:25 <daliusd> boiko, I know about transitions

 17:25 <daliusd> popey, you say that swipe-up still works for you

 17:25 <daliusd> with that change

 17:25 <boiko> daliusd: ah ok, just thought I'd point it :)

 17:26 <daliusd> Repeater does not have transitions :-)

 17:26 <daliusd> ListView already uses some

 17:26 <popey> yes

 17:26 * daliusd checks for updates

 17:26 <popey> assuming i added it correctly

 17:26 <popey> but that's on my pc, not on-device

 17:27 <daliusd> popey, if it adds animation for operations then you have added it correctly

 17:28 <popey> hmm

 17:28 <daliusd> you might consider adding longer duration: like 200

 17:28 <popey> ok

 17:29 <popey> hah, 2000 is a bit big

 17:29 <popey> yes, that works

 17:29 <daliusd> OK strange now it works for me

 17:29 <daliusd> I have not changed anything

 17:30 <popey> must be sun spots or something ㋛

 17:30 <daliusd> :D

 17:30 <daliusd> Let's test again

 17:31 <daliusd> Now it doesn't work

 17:32 * popey tries on a device

 17:33 <daliusd> tried 6 times: 2 times work, 4 doesn't

 17:33 <popey> seems broken on device too

 17:33 <popey> i cant break off the result to start a new calculation

 17:34 <daliusd> OK I will report Qt bug

 17:34 <daliusd> They have access to source code as everyone else

 17:34 <popey> nice to see a bit of colour on the device ㋛

 17:35 <daliusd> :)

 17:35 <daliusd> I believe that's it from me

 17:35 <daliusd> bugs for autopilot

 17:35 <daliusd> are kind of blocked as well

 17:35 <popey> yeah, lots of those

 17:35 <daliusd> because if we will change keyboard

 17:35 <daliusd> we will need to throw out all tests

 17:36 <popey> even the swipe ones?

 17:36 <daliusd> except those :)

 17:36 <popey> heh

 17:36 <daliusd> while no

 17:36 <daliusd> even those

 17:36 <daliusd> as you need keyboard

 17:36 <daliusd> to create some test data

 17:36 <popey> ah right

 17:37 <popey> I am less concerned about the ap tests right now

 17:37 <popey> focus for now would be implementing the design

 17:37 <popey> I can find someone to help with AP later

 17:38 <daliusd> ok

 17:38 <popey> be good to see some of the design stuff landing

 17:38 <daliusd> ?

 17:39 <popey> in trunk, the work you're doing at the moment

 17:39 <daliusd> Well when I will implement icons

 17:39 <daliusd> I will request merge

 17:40 <popey> sweet.

 17:40 <popey> I didn't have anything else to raise right now.

 17:41 <popey> any other issues you guys have?

 17:41 <daliusd> No

 17:41 <popey> As you know we've been dogfooding the devices

 17:42 <popey> I was out having a meal last night.. we used the calculator app.. in the real world!

 17:42 <popey> ☻

 17:42 <popey> to work out the bill

 17:42 <daliusd> cool :)

 17:42 <popey> and the restuarant didn't complain that we didn't pay enough, so good work there! :D

 17:43 <popey> ok, lets wrap up then. thanks guys!

 17:43 <popey> #endmeeting



Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)