== Meeting information == * #ubuntu-touch-meeting: Clock App, 30 Aug at 19:44 — 20:10 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2013/ubuntu-touch-meeting.2013-08-30-19.44.log.html]] == Meeting summary == == Vote results == == Action items == * (none) == People present (lines said) == * mhall119 (51) * nik90_ (50) * meetingology (3) == Full Log == 19:44 #startmeeting Clock App 19:44 Meeting started Fri Aug 30 19:44:44 2013 UTC. The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 19:44 19:44 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 19:45 alright, some bugs: https://bugs.launchpad.net/ubuntu-clock-app 19:45 Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-clock-development 19:45 Burndown: http://status.ubuntu.com/coreapps-13.10/ubuntu-clock-dev.html 19:46 My plan is to get the Alarms feature ready by this weekend. 19:46 cool, do you have the necessary designs for that? 19:46 I was told by Zsombi that Renato is working on the alarms from platform point of view. However Jono says renato is on a holiday 19:47 Can you confirm who is assigned that task? 19:47 I have the necessary designs, however the SDK *does not* have the widget that I need to implement the design. 19:47 I'll track down who's assigned, yeah 19:48 what widget do you need? 19:48 However I talked to mehow and juihi, who said that the new option selector which landed recently will be extended to fill ththe missing functionality 19:48 I basically need a multiple option selector 19:48 the new one which landed only allows the user to select one option 19:49 However for setting an alarm on multiple days like Monday and Wednesday for instance, I need the multiple option selection widget 19:49 right, I think the new value selector was just going to allow more kinds of option components, but not multi-select 19:49 nik90_: so we might need to make a custom component for that 19:49 maybe as a subclass of value selector 19:50 However Juini who is in charge of the widgets going into the sdk said he will talk to the dev to implement this 19:50 ok 19:50 So I was thinking for now, just use the option selector with the limitation of 1 day and then later fix it 19:50 would that be okay? 19:51 either that or just use 7 different checkboxes in a ListView 19:51 that was what was done previously but it increases the code quite a bit actually 19:52 ok 19:52 because with a option selector I just have to do value: ["Monday", "Tuesday"....] while otherwise I would have to create 7 listitem standards with a checkbox in them 19:52 as long as somebody is working on a multi-select version of the option selector, I'm okay with using it for now with the 1-day limitation 19:53 ok 19:53 My next question is regarding a c++ plugin 19:53 for reading timezone files? 19:53 Is there any core app making use of a custom C++ plugin? 19:53 yes 19:53 I already created the plugin 19:53 I am only worried about the debian rules file modification 19:53 yes, file manager, music and terminal all use custom C++ plugins 19:53 but it is going to make packaging them as Click difficult 19:54 they are currently all building their plugin as a separate .deb, and the code is in a separate branch 19:54 which is fortunate, because music and file manager both use the same plugin now 19:54 yeah I noticed that. But I do not have a choice since QML does not offer timezone support. 19:55 However what I and Chocanto did was create a standard file reader plugin 19:55 we were thinking of integrating it to the SDK itself 19:55 so anybody wanting to read a file can use this plugin 19:56 would be useful, but we have to talk to bzoltan about it and make sure it's 1) a clean API, 2) well documented and 3) well tested 19:56 but yes, it would be quite useful I would think 19:56 exactly. Also reading files does not cause any security concerns and was accepted by the security team in my mailing list discussion 19:57 yeah, apparmor will prevent it from reading things it shouldn't 19:57 ok, so it sounds like you're unblocked until such time as you need to test the actual alarm service implementation 19:58 and I'll track down who's working on that and find out when it'll be ready 19:58 Which timezone is bzoltan in? 19:58 Norway time 19:58 okay. 19:58 UTC+1 or +2 19:58 I am free in the evening, so I will try to contact him on irc, otherwise I will email him with a cc to you 19:58 sounds good 19:59 so you're working on alarms first, then timezones 19:59 yes 19:59 we should have GPS working too, with QtLocation 19:59 IIRC, that was another thing you were blocked on 19:59 yup 19:59 have you tried it yet? popey tried to get the example code working and it was failing 20:00 I tried it sometime back and it was failing 20:00 ok...I'll see who's responsible for that too then 20:00 so I asked on g+, and on IRC 20:00 but no one had working examples 20:00 I think it is thomas vobb 20:00 ok 20:00 working on qt location, the last time i talked to him 20:01 I tried the clock app on the nexus 4, it has certain issues that I understand now 20:01 did you get your N4? 20:01 hopefully I can get a fix for them soon enough 20:01 yeah I already informed you 20:01 you gave me your script to install common stuff 20:02 oh right, now I remember :) 20:02 it's been a crazy busy week 20:02 btw the camera app does not work for me 20:02 it just shows a black or white screen 20:02 really? it works fine for me... 20:02 do you see the camera on-screen buttons 20:02 ? 20:02 or nothing at all? 20:02 nothing at all 20:03 just blank white or black screen 20:03 is there a way to get terminal output? 20:03 perhaps I can file a bug report 20:03 launching it via the terminal will get you output 20:03 or over adb 20:04 is it called via camera-app on the terminal? 20:05 I think so, but you can cat it's .desktop file in /usr/share/applications/ to see exactly how 20:05 okay 20:06 ok, got an update from tvoss about QtLocation 20:06 the blocker is https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1218896 20:07 once location-service is accepted into main, then QtLocation should be able to use it, then it will be accessible from QML 20:07 ah okay 20:08 ok, so any other topics to discuss? 20:08 nope 20:09 cool, can't wait to have alarms working, that's the only thing my old Android phone is doing anymore 20:09 me too :D 20:09 it's a very very smart alarm clock :) 20:10 ::) 20:10 ok, tvoss is going to write up instructions for manually installing the location-service and QtLocation builds that use it, should have a link tomorrow or by monday 20:10 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)