17:01:54 #startmeeting Ubuntu Touch Calculator app meeting 17:01:54 Meeting started Thu Apr 4 17:01:54 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 17:01:54 17:01:54 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:10 welcome! 17:02:13 Hi 17:02:22 hi dalius 17:02:22 Hello 17:02:30 some good news for you.. we're looking to put the calculator app in the Ubuntu Touch preview image today 17:02:39 so it should be in the automatic builds which get made overnight 17:02:46 nice! 17:02:49 this should get it a lot more testing 17:02:54 (and possibly bug reports) :D 17:02:56 Great :) 17:03:06 Good news :) 17:04:00 also, mhall119 has some information for you.. 17:05:16 right, just hit publish actually 17:05:17 http://mhall119.com/2013/04/core-apps-road-to-october/ 17:05:32 we now have progress tracking on status.ubuntu.com for all of the core apps 17:05:41 the charts are built based on your work items in the blueprints 17:06:25 good! 17:06:29 so as you start a work item, mark it as INPROGRESS, and when you finish it mark it as DONE, and the chart will automatically update 17:06:46 the black line shows what the average progress should be in order to reach out goal 17:07:17 ideally, everything above that line will be green, showing that we're finishing enough work items that we can get them done by October 17:07:44 read the rest of the blog post for more information about the different charts available 17:08:03 but again, make sure to keep the BP updated, so we can all see your progress 17:08:04 great, thanks mhall119, any questions about that? 17:08:59 * daliusd has no questions 17:09:06 so, for calculator app, month-0 milestone, this is what we have: http://status.ubuntu.com/coreapps-13.10/ubuntu-calculator-dev-coreapps-13.10-month-0.html 17:09:33 hi guys, sorry I'm late 17:09:52 hi boiko 17:09:55 hi boiko 17:10:20 np boiko the meeting is logged so you can catch up after 17:10:33 is it finished already? :-O 17:10:51 not yet 17:11:08 popey: ah ok, good, sorry to interrupt :) 17:11:13 np :D 17:11:21 Do you guys have any blocking issues or problems we can help with in general? 17:11:46 i don't think 17:11:46 * mhall119 had 2 bugs to track down 17:11:57 I just noticed I have TODO item: fix animation 17:12:02 what's idea behind that? 17:12:17 [dalius-sandbox] Fix "pull to start new calculation" animation: TODO 17:12:50 daliusd: last meeting you (or somebody) brought up that there was some finishing work to do on making the animation look good and match design 17:13:10 dalius, the animations are not playing well with the tearing formula i think 17:13:20 OK got it 17:13:27 I will look what could be done 17:13:35 thanks! 17:15:24 so we had a call with the design team earlier today, and we should start getting visual designs next week, which will include colors and textures for the various widgets 17:15:42 Very good :) 17:15:43 but hopefully few or no layout changes, and there should be no functionality changes 17:18:50 so, is there any specific area or topic you guys think I could help as a mentor? 17:19:39 boiko, I think you should look what's done and say to us what looks wrong 17:20:11 you can review bugs we have or have fixed - maybe that will give ideas 17:20:31 daliusd: yep, I'll be pointing some things that could be improved, indeed, but nothing really wrong in the code so far 17:20:43 thats good to hear 17:21:05 yes, code reviewing is something I can definitely help with 17:22:56 I've a question: for internalization, how we understand if users wants AM/PM or 24h in date-time? Are there a super-setting or similar? 17:23:31 WebbyIT: I think in general you just use Qt.formatDate and it will take care of that 17:24:15 err, Qt.formatDateTime actually 17:24:24 boiko: ok, thanks 17:25:01 boiko, I guess that does not really answer our question 17:25:33 I look at documentation now 17:25:52 We use custom format 17:26:06 and I'm not sure if that respects user settings by default 17:26:17 boiko: i think the question is more, how do we know if the user (in a separate settings app) has changed the date format 17:26:45 daliusd: yes, that's something I saw in the code: the custom date formatting, but I don't think it is necessary (apart from the "Today" and this kind of stuff) 17:26:50 popey: yep, looking it up 17:28:45 daliusd: WebbyIT: http://qt-project.org/doc/qt-4.8/qlocale.html#dateFormat 17:29:02 that's C++ though, not sure there is a QML function for that, let me see 17:29:16 we're running low on time, it's only a 30 min meeting.. 17:29:49 this is an important topic though.. "Settings" in general is not solved yet I believe 17:30:10 indeed, I don't think settings is something sorted out at system level yet 17:30:18 What calendar team is doing with that? 17:30:36 http://qt-project.org/doc/qt-5.0/qtqml/qml-qtquick2-locale.html#dateFormat-method 17:31:10 rferrazz: nice! exactly that 17:31:57 guys, maybe we can continue the discussion on another channel? (as the meeting is time is already over) 17:32:09 #ubuntu-touch would be good 17:32:13 ok! 17:32:20 ok 17:32:24 popey: yep 17:32:25 ok 17:32:26 thanks boiko 17:32:47 we'll mail the list once we have a build of the phone which incorporates the calculator app as it is 17:32:59 anything else before i wrap up? 17:33:24 nope, nothing from my side 17:33:31 nothing 17:33:54 nothing 17:34:00 great, thanks guys! 17:34:02 nothing 17:34:11 thanks popey! 17:34:14 thank anyone! 17:34:16 keep up the great work, and keep an eye on the burndown chart! :D 17:34:20 #endmeeting