15:03 #startmeeting Calculator meeting 15:03 Meeting started Thu May 8 15:03:22 2014 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 15:03 15:03 Available commands: action commands idea info link nick 15:03 hi gang65 ☻ 15:03 Hi gang65 rpadovani popey 15:03 Hi 15:04 :-) 15:04 Hi guys :-) 15:04 So a couple of days ago I pushed the latest version of calculator to the store.. 15:04 bzr r253 i think 15:04 \m/ 15:05 Yup. thats right. 15:05 Currently the only thing which is open for discussion is the advanced function merge we've been discussing 15:05 popey: how is feedback from device manf 15:05 https://code.launchpad.net/~gang65/ubuntu-calculator-app/advanced_function/+merge/212530 15:07 Good question. 15:07 The feedback I have had so far is "Current functionality meet requirements" 15:07 ☻ 15:07 :) 15:08 :-) 15:08 I see you guys have a separate branch for the advanced functions.. 15:08 https://code.launchpad.net/~ubuntu-calculator-dev/ubuntu-calculator-app/advancedFunctions 15:08 great idea ☻ 15:08 popey: yeah , but not yet started 15:08 I will merge it soon 15:08 ok. 15:08 would be good to do some testing of that. 15:09 I made same testing 15:09 manual testing 15:09 But I stuck with autopilot tess 15:09 test 15:09 I don't know how to get KeyboardCalc object 15:10 gang65: how many advance function we can incorporate ? 15:10 i guess first we should change the backend stuffs instead of changing front end 15:10 what say rpadovani ? 15:10 gang65, you can join #ubuntu-autopilot and ask to balloons to help you with autopilot 15:10 mihir, gang65 and I chatted a bit yesterday about advanced functions, and seems we have to change something to made them work: During the weekend I'll work on the storage 15:11 yes 15:11 * balloons waves 15:11 hi balloons : 15:11 for storage, it is another bug report 15:11 https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1315799 15:11 Our idea is to have another table to save results of calc, so we havent' to think about ( ) , what do you think mihir ? 15:12 rpadovani: can't we brainstorm to get in same table with some flag columns ? 15:12 I have another idea 15:13 Maybe we should storage it in some local variable 15:13 and after swipe up it will be storaged 15:13 gang65: it will eat up memories 15:13 if i am having large calculations 15:14 Now it is eat CPU 15:14 :-) 15:14 Mhh, dunno, I don't study it yet, I want to do some search to understand what's the best way, I never work on something like this 15:14 rpadovani: neither do i, popey any suggestion based on your exp ? 15:15 hm 15:15 I suggest to make same prototype and see how it is works 15:16 I like an evidence based approach. 15:16 test it, see which is better. 15:16 okay 15:16 ok 15:17 gang65: rpadovani we can try both the way and choose the better on , what do you say? 15:17 also, is engine.js and bigNumber.js are able to handle advance functions ? 15:17 yes 15:17 of course 15:17 it was designed for that 15:17 :) 15:18 unfortunately Simple Calculator is not ready for that 15:18 for example problem with brackets 15:18 yeah, 15:19 So, our problem is that frontend and storage don't work, but the backend is ready 15:19 seems like an easy problem :-) 15:19 I think it is not so easy 15:19 Of course, given our "customer" says they're happy with existing functionality, I'd put advanced functions down as a low priority "nice to have". 15:20 and while it's a fun thing to hack on, I worry about us spending a lot of effort on it. 15:20 When there's bugs in other core apps. 15:20 rpadovani: trup 15:20 Does that sound fair? 15:20 yes 15:20 popey: yes 15:20 popey, sure, I don't write code for calculator since a while :D 15:21 neither do i 15:21 I do :-) 15:22 ☻ 15:22 so popey you meant to say, lets low down this priority of work as of now, 15:22 So I'm happy to support you guys, and will help with testing and unblocking things, that's for sure. 15:22 I'm not going to try and stop you working on this. 15:23 popey: sounds fair 15:23 I just look at all the other bugs and think "oh my!" ☻ 15:23 So, the end is: calculator is awesome, and it's ready. If we have time, we can try to add advanced functions, but isn't a priority, right? 15:24 Yeah. 15:24 How often Ubuntu Core apps releases are made? 15:24 To the store? 15:24 yes 15:25 depends, currently it's manually done by me and balloons 15:25 ok 15:25 The criteria is basically:- 15:25 a) If the app has a large number of changes built up in trunk 15:25 b) if there have been a significant number of days since last upload, and there's worthwhile changes in trunk 15:25 c) if we have time 15:25 In the future, it will all be semi-automatic 15:26 Will go Trunk -> automated testing on desktop and phone -> store 15:26 (massively simplified) 15:26 Then it just takes one of us to accept the change into the store, so it doesn't do anything silly 15:26 popey: what are expected dates of device to be in market , or still not fixed? 15:26 but that too will eventually be automated 15:26 Uh, "this year" is the standard answer to that. 15:26 Okay:) 15:26 I don't have a date. 15:27 And if I did, I probably wouldn't be allowed to say anyway. 15:27 But my personal expectations are that I'll buy a new phone before the end of the year. 15:27 :) 15:28 Ok, so final question. Do you want to continue having the calculator meeting, or is it no longer necessary? 15:28 Up to you guys. 15:28 popey: feel that we can do chat up whenever it is required, what do you say rpadovani gang65 ? 15:28 and we can resume regularly once we will go to full on development mode. 15:29 For me we can stop, if we need we can find each other here or on G+. popey I suggest to ping you when we have something working for advacend features maybe tomorrow, maybe in a couple of months :-) 15:32 sounds good. 15:32 You know where I am ☻ 15:32 ok 15:32 And I'm always keeping an eye on the branches anyway. 15:32 Ok, shall we wrap up? 15:32 popey: you need to you fall out of the trees else ;) 15:32 please let me know if meeting will be resumed 15:33 I will do. 15:33 popey: sounds good :) 15:33 Thanks guys 15:33 #endmeeting