[01:12] <samertm> any calendar app devs here?
[01:12] <samertm> I fixed the bug :D
[01:13] <Datsundere> nice
[01:13] <samertm> Datsundere: literally took all 7 hours :P
[01:13] <Datsundere> haha
[02:41] <ahayzen> balloons, ping
[02:42] <balloons> ahayzen, just who I wanted to speak with
[02:42] <ahayzen> balloons, if this has been merged how long until Jenkins can use it? https://code.launchpad.net/~thomir/autopilot-qt/export-qobject/+merge/201865
[02:42] <balloons> I asked chris to land that :-)
[02:42] <ahayzen> balloons, uhoh wht have i done ;) lol
[02:42] <ahayzen> balloons, thanks :)
[02:43] <balloons> to your question, I'm not sure\
[02:43] <ahayzen> balloons, does it have to be put into the 1.4/1.3 branches?
[02:43] <balloons> I don't believe so..
[02:43] <balloons> We should try now and see
[02:43] <balloons> if it doesn't work, we'll ask around tomorrow
[02:44] <ahayzen> balloons, i tried pulling my branch but then didn't know if my terrible knowledge of autopilot was actually causing the issue lol
[02:44] <ahayzen> balloons, this failed 1hr ago https://code.launchpad.net/~andrew-hayzen/music-app/mediaplayer-simplify/+merge/201265
[02:44] <balloons> ahh you tried already :-)
[02:45] <ahayzen> balloons, should return self.select_single("*", objectName="player") work?
[02:45] <ahayzen> balloons, because i tried a few things before and didn't know which was the correct one tht 'should' work
[02:46] <ahayzen> balloons, i also suspect once it has got past tht issue there will be other things i've missed in the conversion but they'll be easier to patch
[02:46] <balloons> looks like the only ppa used is the core apps drivers
[02:46] <balloons> so yea, I suppose it might
[03:08] <ahayzen> balloons, was this wht u wanted to talk to me about or was there something else as well?
[03:08] <balloons> ahayzen, yes
[03:08] <balloons> also https://code.launchpad.net/~sergiusens/music-app/flaky_1272996/+merge/203349
[03:08] <balloons> ahayzen, ^^
[03:08] <ahayzen> balloons, oh yh i saw tht
[03:09] <balloons> do you know anything about this test? either way be on the lookout for such things. As you can see, we shouldn't be just disabling tests :-(
[03:09] <ahayzen> balloons, we did have a flaky test on the hack day which i said to Victor we needed to investigate...
[03:10] <ahayzen> balloons, or i thought we did somewhere
[03:11] <balloons> yes I seem to remember also
[03:11] <balloons> anyways, I'll have a closer look tomorrow
[03:11] <balloons> that was it howevr
[03:11] <balloons> working on fixing the nexus 4 I broke :-(
[03:11] <ahayzen> balloons, wht did u do to it?
[03:12] <balloons> ahayzen, I'll post pics I think
[03:12] <balloons> I dropped it over xmas
[03:13] <ahayzen> balloons, uhoh
[03:13] <balloons> shattered the screen
[03:13] <balloons> yep.. new screen is finally here and installed
[03:13] <balloons> time to reflash everything and make sure it all works :p
[03:15] <ahayzen> balloons, \o/ ... good luck
[03:16] <ahayzen> balloons, think this was the error of the flaky test http://paste.ubuntu.com/6829928/
[03:59] <Datsundere> too much hassle setting up sdk on a different distro
[07:25] <nik90> zsombi: hey good morning
[07:26] <zsombi> nik90: hey good morning there too :)
[07:26] <nik90> zsombi: hey would you happen to know how to change the colors of the dialer widget that I use in the clock app?
[07:26] <zsombi> nik90: thru style
[07:26] <nik90> zsombi: so I define the style file in the clock app which targets the dialer widget..
[07:26] <zsombi> nik90: there's no color parameter exposed in the component, nor style hints are not there yet
[07:27] <nik90> zsombi: can I change the style file dynamically?
[07:27] <zsombi> nik90: or you simply create your own one... but that's not really good
[07:27] <nik90> zsombi: we are thinking of changing the background gradient based on the time of the day.
[07:28] <zsombi> nik90: we had been thinking of having style hints to control certain aspects of a style, but thi sidea has not been baken yet... as we could simply expose some properties that drive the style, but these are pretty style-specific so... we are still debating that
[07:29] <nik90> zsombi: hmm okay, I was looking for a more temporary solution for now.
[07:29] <zsombi> nik90: right... uhh... damn it... I don't remember now whether the colors were declared as public properties fop the style or were simply using Theme.palette colors...
[07:30] <zsombi> nik90: a temporary solution would be to import the Ambiance theme, declare the style in place (not loaded with Theme.createThemeComponent()) and set the colors there... just need to check whether these colors are exposed or not...
[07:32] <nik90> ah..something like import Ubuntu.Components.Themes.Ambiance 0.1
[07:32] <nik90> and then style: TextFieldStyle {
[07:32] <nik90>         background: Item {}
[07:32] <nik90>     }
[07:32] <nik90> just an example I took from the textfield stlying
[07:33] <nik90> zsombi: oh one last thing, I was asked to use the Alarms API for setting timers as well. Is there a way to distinguish between timers and alarms in the API?
[07:33] <nik90> zsombi: since I wouldn't want to list timers in the alarms page
[07:34] <zsombi> nik90: timers?! who asked that?? No, there is no way to separate them, and noone asked ME to provide support for timers...
[07:35] <nik90> zsombi: I was talking to bfiller about this :)
[07:35] <zsombi> nik90: you can set an alarm to kick in the next 10 seconds for instance, but that simply does not make sense!
[07:35] <nik90> zsombi: there is an issue where if a timer is running and the clock app is in the background, then it doesnt ring when the timer is complete
[07:35] <zsombi> nik90: these alarms will also be listed in between the other ones...
[07:35] <nik90> zsombi: so bfiller, tvoss told me to use the alarm service for this
[07:36] <zsombi> nik90: yes, it's OK, but we need to support that properly
[07:36] <zsombi> nik90: otherwise it'll be listed in between the other alarms...
[07:36] <nik90> zsombi: yup that's what I thought as well
[07:36] <zsombi> nik90: so I'm wondering why I have not been asked for...
[07:37] <nik90> zsombi: this issue with the timer only cropped up recently
[07:37] <nik90> zsombi: so may be the use case wasnt known before
[07:37] <zsombi> nik90: ok... however... there are bigger issues with these alarms... as they are listed in the Calendar, or more precisely in between the Todo items
[07:38] <zsombi> nik90: so the only backdraw of using QtOrganizer is that the alarms database will be the same... :/
[07:38] <zsombi> nik90; sharing the same DB as the rest of the calendar items... which is bad
[07:39] <nik90> zsombi: couldn't we introduce a type property to filter out what is shown in the calendar and the alarms tab?
[07:39] <zsombi> nik90: so... I we need to support a separate type which should not be listed in between alarms
[07:39] <nik90> although not sure if it is supported in the qtOrganizer
[07:39] <zsombi> nik90: yes, we could, but we need to handle that on the Alarms level...
[07:40] <nik90> ok
[07:40] <zsombi> nik90: so we need to duplicate the organizer DB ToDos...
[07:41] <nik90> zsombi: I think considering the amount of work, it would be best if you discuss to bfiller to confirm this..
[07:41] <nik90> zsombi: but definitely there is a need for apps (not just clock app) to trigger a notification in the near future about something
[07:42] <zsombi> nik90: it's not the amount of work, that bothers me, it's the DB mess we are going to get... especially that we cannot hide the Alarms from ToDos... that's what bothers me the most
[07:43] <nik90> I can understand, same db used by two apps
[07:45] <nik90> zsombi: going back to the dialer style, on looking through the toolkit code, I see you defined this statement style: Theme.createStyleComponent("DialerStyle.qml", dialer)
[07:46] <nik90> but I cannot find the DialerStyle.qml file
[07:46] <zsombi> nik90: DialerStyle.qml is under Ubuntu.Components.Themes.Ambiance
[07:46] <zsombi> nik90: under /usr/lib/*/qt5/qml/->
[07:47] <zsombi> nik90: subst the dots with /
[07:47] <zsombi> nik90: and the Style API is not fixed :/
[07:48] <nik90> zsombi: ok, I will keep an eye out on this.
[07:57] <nik90> zsombi: here is the DialerStyle.qml file at http://paste.ubuntu.com/6830730/. I figured out how to change the outer background color, but I am not sure how to change the center item color
[07:57] <nik90> zsombi: do you know how can I refer to that component to change it?
[07:57] <dholbach> good morning
[07:58] <zsombi> nik90: first of all, all colors must be exposed as properties... this component wasn't confirmed by the UX, as the TimePicker design got changed, and this wasn't a high priority anymore...
[08:00] <nik90> dholbach: good morning
[08:00] <nik90> zsombi: considering that the design for the picker changed, would the dialer remain part of the SDK?
[08:01] <zsombi> nik90: yes
[08:01] <dholbach> hey nik90
[08:01] <zsombi> nik90: as it could be benefficial for all sorts of apps, just we need to standardize the design of it
[08:02] <nik90> zsombi: can I propose a MR to expose the colors as public properties in the style file?
[08:02] <zsombi> nik90: sure
[08:03] <zsombi> nik90: that'd be awesome!
[08:03] <nik90> zsombi: alrite..thnx :)
[08:04] <zsombi> nik90: ywc
[08:40] <JamesTait> Good morning all; happy Data Privacy Day! :-D
[08:45] <dpm> morning mzanetti, when you've got a minute, here's some trivial MP to review: https://code.launchpad.net/~dpm/reminders-app/update-translations-after-cleanup/+merge/203487
[09:42] <WebbyIT> vthompson found a bug in calculator app that is perfect for Hack Days :-) Bug 1273555
[09:42] <ubot2`> Launchpad bug 1273555 in Ubuntu Calculator App "Pressing minus and plus keys followed by a number produces odd results" [Medium,Triaged] https://launchpad.net/bugs/1273555
[10:35] <nik90> dpm: I just saw your reminder bug https://bugs.launchpad.net/reminders-app/+bug/1273311
[10:35] <ubot2`> Launchpad bug 1273311 in Ubuntu Reminders app "Add Alarm API integration in reminders" [Medium,Triaged]
[10:37] <nik90> dpm: I am afraid that the current Alarm API would not help fix the bug. If the reminders-app start using Alarms API to trigger notifications, then we will see those alarms in the clock app which shouldn't happen
[10:37] <nik90> dpm: this requires the alarms api to be reworked further (potentially for v2.0 or later)
[10:46] <dpm> nik90, ah, thanks for the heads up. I hadn't thought about that. To be honest, I don't think it'd be bad to have the reminders showing up in the clock or calendar for now (since we want to integrate them in the system and not show up only when you open Reminders, it makes sense to have them in other apps). That said, it might make sense to have more finely-grained control on which alarms belong to which app. You've been deeply involved in the Alarm
[10:46] <dpm> conversations, do you happen to know if there has been any talks in that direction (i.e. per-app alarms)?
[10:47] <nik90> dpm: I just had a chat with zsombi about this in the morning :)
[10:47] <dpm> ah, great!, what was the conclusion?
[10:47] <nik90> dpm: the thing is they all the apps share the same database, and as a result we have to be careful about what we put there
[10:47] <dpm> ack
[10:48] <nik90> dpm: currently per-app alarms is not yet there and zsombi wasn't aware of that requirement
[10:48] <nik90> dpm: I requested him to talk to bfiller and plan this out in detail before considering implementation
[10:49] <dpm> thanks nik90
[10:49] <nik90> np
[10:57] <timp> so there are three apps now that can set an alarm? calendar, reminders, clock?
[10:59] <nik90> timp: technically yes :P
[10:59] <nik90> timp: but we will ensure that there are appropriate filtering mechanisms in place for that to work
[11:00] <nik90> I need to send an email to the ML about this.
[11:01] <timp> and all three can have their own additional information associated with the alarm?
[11:01] <timp> hmm
[11:01] <timp> that will require some thought :)
[11:01] <nik90> true, I certainly wouldn't want the clock app to show alarms about calendar or reminder events
[11:02] <nik90> that would just result in actual alarms being lost in a midst of events and reminders
[11:02] <timp> but in calendar you may want to show reminder events
[11:02] <nik90> +1
[11:03] <nik90> calendar can choose to display all types of alarms since they are filtered by the date technically
[11:03] <nik90> but in clock app we have no such filter by date option
[11:05] <popey> davmor2: https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1273637
[11:05] <ubot2`> Launchpad bug 1273637 in Ubuntu Calculator App "can't input decimals without a numeric value at start" [Undecided,New]
[11:09] <dpm> nik90, is there any way you think we could filter those alarms as a workaround until we would get this filtering implemented? E.g. a marker an app can set when filing an alarm, and that it can recognise when it reads the list of alarms, so that it only loads those with the marker? It'd be a hack by all means, but I'm thinking of ways to get there before the full implementation, as MWC is coming closer, and alarms would be a nice feature to show
[11:09] <dpm> Well, not only nice, but it's pretty essential :)
[11:10] <dpm> zsombi, where's the best place to file bugs against the alarms API?
[11:11] <dpm> the UITK itself?
[11:11] <nik90> dpm: unfortunately no..the alarms API does have a proprerty "type" but that is just to indicate whether the alarm is recurring or not
[11:11] <nik90> dpm: yes to the bugs question..report to UITK
[11:12] <nik90> dpm: one rather bad hack would be to append the title with "Event" or "Reminder"
[11:13] <nik90> dpm: this way I could hide those from the clock app, but again it seems very very hacky to do
[11:13] <nik90> dpm: also any improvements to the alarms API will not land on the phone until qt 5.2 lands in the phone
[11:14] <dpm> nik90, but that's what I meant with a hack, also perhaps we could use that type to indicate the app it's coming from. Then we'd have to think about migration: once filter would be properly implemented, the app would need to rewrite the type of the alarm to get it back to use its proper meaning. The thing we'd have to. In any case, just a thought for now.
[11:14] <nik90> dpm: considering that the entire UITK package is frozen for 2 months now.
[11:15] <nik90> dpm: the type property is offered by the alarms API. So I guess zsombi will have to agree to that :)
[11:48] <kalikiana> aquarius: I wonder if you'd like to review some U1Db-Qt branches
[12:03] <mzanetti> dpm: approved your branch and proposed this one: https://code.launchpad.net/~mzanetti/reminders-app/reminders/+merge/203522
[12:04] <mzanetti> dpm: and fixed the issues in here: https://code.launchpad.net/~mzanetti/reminders-app/shoot/+merge/203418
[12:04] <dpm> mzanetti, oh, wow, we're getting reminders! \o/
[12:04] <dpm> mzanetti, I want to ask Dani to join our meeting tomorrow to review the latest changes
[12:06] <mzanetti> dpm: please also read the updated description in this MP: https://code.launchpad.net/~mzanetti/reminders-app/shoot/+merge/203418
[12:06] <mzanetti> jfi
[12:07] <dpm> ack, refreshed the page, thanks
[12:10] <dpm> mzanetti, so the camera helper does rotation and exports the standard paths to QML, right? Would it make sense to have it as a plugin instead of in main.cpp, so that we can keep using qmlscene as the rest of the apps? Note: I'm not proposing, just asking
[12:11] <mzanetti> dpm: with click apps that wouldn't be a problem. with installed apps however it is. Because the plugin would be installed to /usr/lib/arch/qt5/qml/ which is where all the other plugins are and all apps can find it
[12:12] <mzanetti> which would pollute the folder quite badly if everyone does that
[12:12] <mzanetti> as this is really app-specific and mot really of much use for other apps I think linking it into the main binary makes the most sense
[12:13] <mzanetti> dpm: as a side note: qmlscene is not intended to be used in a production environement
[12:13] <mzanetti> so I'm not a huge fan of what we're doing with the other apps either
[12:16] <mzanetti> dpm: ouch. just found a bad bug in the camerahelper. let me fix before approving
[12:17] <dpm> mzanetti, ah, I see. I think it might actually be usable by other apps using the camera, as they're going to come across the same issues. However, I guess that the two pieces of functionality that we need it for will be fixed eventually somewhere else (although I'm not sure about the rotation one), so it doesn't really make sense to put them in the plugin. I don't have an opinion on using qmlscene, but I think where we can, it makes sense to be cons
[12:17] <dpm> istent with the rest of the platform, that's why I was asking.
[12:17] <dpm> mzanetti, ack, will wait with the review
[12:18] <mzanetti> dpm: yeah. consistency is definitely good. but not at any price ;)
[12:18] <mzanetti> and in this case I think the downside of using it would be bigger then the little gain of consistency
[12:20] <mzanetti> dpm: actually imho in the long run we should have the SDK generating a minimalistic main when you start a new app from template. Which would be consistent with the rest of the world ;)
[12:20] <mzanetti> dpm: fixed the bug in the camerahelper.
[12:20] <dpm> mzanetti, ack, thanks
[12:21] <dpm> mzanetti, btw, are you coming to the Orlando sprint? The templates might be something worth discussing in person there
[12:21] <mzanetti> dpm: nope, not invited
[12:21] <dpm> mzanetti, also, it seems Jenkins wasn't too happy with https://code.launchpad.net/~mzanetti/reminders-app/reminders/+merge/203522
[12:22] <mzanetti> dpm: the cleanup branch needs to land first
[12:22] <mzanetti> because this one still has the autopilot suite called reminders_app
[12:22] <dpm> ah
[12:22] <mzanetti> could set it as prerequisite
[12:22] <WebbyIT> mzanetti, do you have a minute? I found a way with C++ to implement the RTF, but I'm not able to write the C++ code for add <b>. This is my snippet of code: http://paste.ubuntu.com/6831669
[12:24] <aquarius> kalikiana, I am massively unable to comment on C++ code :(
[12:24] <mzanetti> WebbyIT: this seems to be fishy: if (textPos <= boldStartPosition && textPos + textString.length() > boldStartPosition) {
[12:25] <WebbyIT> It deletes the text :/
[12:25] <mzanetti> :D
[12:26] <WebbyIT> mzanetti, also with textPos == boldStartPosition doens't work
[12:26] <mzanetti> WebbyIT: well, it a first glance you miss some corener cases too
[12:27] <mzanetti> WebbyIT: I'd reccommend to do this:
[12:27] <kalikiana> aquarius: okay. could you verify this resolves your bug? try if it works and just leave a normal comment https://code.launchpad.net/~kalikiana/u1db-qt/entireContentsInQuery/+merge/203058
[12:27] <mzanetti> WebbyIT: write down some example html
[12:28] <mzanetti> WebbyIT: then walk through the code of this function and change the html to what you think should happen on each step
[12:28] <mzanetti> WebbyIT: and add qDebug() after each like to print the whole m_enml string
[12:28] <kalikiana> now I need to see whom to recruit for some c++ code reviews on u1db-qt… most of the users seem not very fond of c++ :-/
[12:29] <mzanetti> WebbyIT: compare the printed enml with what you think it should be. then you'll find where its off
[12:29] <mzanetti> WebbyIT: if you can't manage, push it to some branch and I'll give it a look in the evening
[12:30] <WebbyIT> mzanetti, ok, I'll try in the afternoon, if I don't find a solution I'll do a branch
[12:30]  * kalikiana wonders if dpm could give some inspiration on how to recruit c++ devs for u1db-qt since he is no good at marketing
[12:31] <kalikiana> (where dev for now means mostly reviews)
[12:37] <dpm> kalikiana, let's ask our app devs community: https://plus.google.com/+DavidPlanella/posts/H1khx3zo45i
[12:37] <kalikiana> dpm: dude, you are the awesome! thanks!
[12:38] <dpm> kalikiana, no worries, let's wait first to see if we get any traction :)
[12:42] <zsombi> dpm: nik90: timp: sorry guys, I was afk for quite some time... I had some stuff to solve and it took more than expected
[12:42] <dpm> no worries!
[12:42] <zsombi> ndpm: nik90: timp: about alarms and reminders: an alar IS a reminder, so there' sno reason to mess up a calendar reminder with an alarm
[12:42] <zsombi> dpm:^
[12:43] <zsombi> dpm: nik90: so, calendar reminders can be set with QtOrganizer API, no need to use Alarms API
[12:43] <zsombi> dpm: nik90: let's keep the Alarms for what it is needed.
[12:43] <zsombi> dpm: nik90: on the other hand I was aware of several apps need to be able to set Alarms, it is the fact that we want to use it as countdown timer, that was sthing I wasn't aware of
[12:44] <zsombi> dpm: nik90: but, as we agreed to use the QtOrganizer+EDS as backend, that brings us some limitations
[12:45] <zsombi> dpm: nik90: like the fact that we cannot separate the Alarms from the ToDos (as Alarms are actually stored as Todos in QtOrganizer)
[12:46] <zsombi> dpm: nik90: so first we need to be sure we can clearly separate the Alarms from the rest of the Calendar DB (maybe use a separate calendar DB if possible)
[12:46] <zsombi> dpm: nik90: then we need a way to create separate DBs (or if not, we can add tags that would serve as app-specific identification)
[12:47] <dpm> zsombi, ack on calendar and Qt Organizer. But with the Reminders app I think we've got a genuine use case for alarms use in another app (reminders in the Reminders app are events which you get a notification for)
[12:48] <zsombi> dpm: and why should that use Alarms API?
[12:48] <dpm> zsombi, which other way would there be to set a reminder in the system and get a notification?
[12:48] <zsombi> dpm: Reminders are also Todo items with audible+visual notification, why to set alarms for it?
[12:48] <zsombi> dpm: just said
[12:49] <zsombi> dpm: honestly, a clear architecture is one where the Calendar reminders use Alarm services, and not the way we do
[12:50] <aquarius> kalikiana, comment added; in my testing that returns the whole document, hooray.
[12:50] <aquarius> kalikiana, bear in mind that this is potentially a breaking change.
[12:50] <zsombi> dpm: reminders are classified to be calendar (PIM) specific, so why to set Alarms for that?
[12:51] <dpm> zsombi, I'm not sure I can follow. I'm not suggesting the way to do it, I'm just trying to understand what Reminders could use to set a reminder and get a notification. AFAIK the alarms API is the only way we've got today to do that (pending the notification bit landing this week)?
[12:51] <zsombi> dpm: when we had chosen the QtOrganizer as backend for Alarm API I already said that the single-DB for Alarms is gonna be a problem
[12:52] <zsombi> dpm: QtOrganizer API, that's where Reminders belong to
[12:52] <zsombi> dpm: wrong, Alarm API is NOT the only one, especially that Alarms API uses QtOrgenizer ToDo (audible+visual) reminders to set the alarms...
[12:53] <zsombi> dpm: either way we do, Todos and Alarms will land in the same DB, and that's bad
[12:54] <zsombi> dpm: we may be able to filter out other Todos in Alarm API, but we won't be able to do the same with QtOrganizer
[12:59] <kalikiana> aquarius: the main one would be if one for some reason compares exact results values… I hope that's not something apps do
[12:59] <kalikiana> and thanks a lot for testing!
[13:02] <dpm> zsombi, so to make sure I understand before continuing, could you confirm this is correct and help me filling in the missing pieces in http://pastebin.ubuntu.com/6831847/ ?
[13:03] <aquarius> kalikiana, no. If you had a doc with contents { topfield: { subfield: "value"; }} and a ListView { delegate: { Text: contents.subfield }} you now have to change it to { delegate: { Text: contents.topfield.subfield }} which is how it should have been from the beginning
[13:03] <zsombi> dpm: not entirely correct
[13:03] <aquarius> kalikiana, I think? Or did we maintain the *structure* before, but just not add all th fields?
[13:04] <aquarius> kalikiana, I don't think we did, so this is a breaking change.
[13:04] <aquarius> kalikiana, there can't be many people using query though because it's so incomplete :)
[13:04] <zsombi> dpm: http://pastebin.ubuntu.com/6831880/
[13:05] <dpm> aha, thanks zsombi!
[13:06] <zsombi> dpm: in theory QtOrganizer API allows to have separate DBs, but AFAIK it's EDS which limits us there...
[13:06] <dpm> ok, gotcha
[13:06] <dpm> renato_, I'm not sure if you've had a chance to follow the conversation above, but do you think it'd be possible to get EDS to use different databases instead of a single one for all apps?
[13:07] <dpm> zsombi, and for notifying when a timer goes off in the clock app, would you recommend using the Alarms API?
[13:09] <zsombi> dpm: we could use that API, however I'd use a different layer if possible, which does not register the event into any DB
[13:09] <dpm> ok, thanks
[13:10] <zsombi> dpm: when we started Alarms API, we suggested to port timed to UbuntuTouch, but tvoss was against it
[13:10] <zsombi> dpm: that would have given us DB-less timer registration too
[13:11] <dpm> zsombi, aha, thanks for the context, that helps
[13:11] <zsombi> dpm: and would not collide with QtOrganizer DB
[13:12] <zsombi> dpm: I'll think of a DB-less timer with Alarms API, or how to create a sub-layer of the API, but I doubth it woudl be doable :(
[13:14] <zsombi> dpm: the biggest issue I see is that whatever alarm is registered with Alarm API, it will land in the DB, and will (eventually) kick after a phone restart, whereas timers should not survive a phone reboot
[13:17] <dpm> zsombi, because it's hooked to Qt Organizer and it will be registered in whichever backend it uses? This might be overly simplistic, but could the memory backend work for that?
[13:18] <zsombi> dpm: no, the memory backend is not linked with the datetime indicator :(
[13:18] <nik90> sorry I was away for lunch, but I did read up on the discussion above
[13:18] <zsombi> dpm: however... hmm... we could fork the memory backend and integrate it with the indicator...
[13:19] <dpm> aha
[13:19] <renato_> dpm, yes you can use many db as you want
[13:19] <zsombi> dpm: need to consult with renato about this!!!
[13:19] <dpm> ah, there he is :)
[13:19] <zsombi> renato_: hey, dude, save us!!
[13:19] <dpm> :-)
[13:19] <zsombi> :)
[13:19] <zsombi> renato_: can EDS handle several DBs?
[13:19] <nik90> :)
[13:19] <renato_> zsombi, yes
[13:20] <renato_> every collection is a DB
[13:20] <zsombi> renato_: awesome, so basically then Alarm API could connect to QtOrganizer so that it would open separate DB for different Apps, right?
[13:20] <renato_> zsombi, you can create a diff collection for each app
[13:21] <zsombi> renato_: hold on, do you say that Alarm collection is not gonna be shown in the Evolution Todos?
[13:21] <nik90> zsombi: but wouldn't you want all system alarms to be in the same collection irrespective of the app which created it?
[13:21] <renato_> zsombi, evolution it shows all collections
[13:21] <zsombi> nik90: nope
[13:21] <nik90> zsombi: Do note that I am not referring to calendar event or reminder etc
[13:22] <renato_> zsombi, what I am saying is that use a collection for each app
[13:22] <zsombi> nik90: I know, but if I create an app I don't want to see the Clock App's alarms, right?
[13:22]  * dpm fondly remembers Evolution being the first open source project he contributed to :)
[13:23] <nik90> zsombi: true +1
[13:23] <renato_> then you can filter by collection if you want filter by app
[13:24] <zsombi> renato_: ok, I can assume that Alarm collections won't be shown in Calendar Todos, right?
[13:25] <renato_> zsombi, yes
[13:26] <renato_> in the future we can create policies to block apps to access data from other apps
[13:26] <zsombi> renato_: not even if I querry collectionless Todos?
[13:26] <renato_> zsombi, in this case the alarms will appear
[13:27] <zsombi> renato_: ah, that's a problem :/
[13:27] <zsombi> dpm:^
[13:27] <renato_> zsombi, why?
[13:28] <dpm> zsombi, renato_ so if I understand it correctly, we would still have one single database, but it would contain a collection for each app, right? And these collections could be then filtered out to show ?
[13:28] <renato_> evolution has a default name for todo colection
[13:28] <zsombi> renato_: because if I use QtOrganizer API, I don't even want to see Alarm collections, that' swhy
[13:28] <renato_> and a collection for alarms
[13:30] <zsombi> renato_: dpm: the problem is that if someone uses QtOrganizer API without collection filter, then when fetching QtOrganizerTodos, it will get all the alarm entries too :/
[13:31] <renato_> zsombi, what is the problem with that?
[13:31] <zsombi> renato_: the problem is that it can mess up the alarms outside of Alarm API
[13:34] <Laney> timp: hiya, just wondering if there's an SDK release planned for $soon?
[13:35] <Laney> & what's the latest on the stock Date/Time pickers?
[13:35] <renato_> zsombi, we can block the alarms to be returned if the user do not specify the collection id
[13:36] <zsombi> renato_: that makes sense, I mean all the collections where there's a specific pattern on the collection name
[13:36] <zsombi> renato_: the one more thing: could we get somehow memory backend connected with datetime indicator?
[13:37] <zsombi> Laney: the PickerPanel will bring the final aspect of DatePicker for you
[13:37] <renato_> zsombi, since the date time uses EDS api, I do not think so
[13:37] <zsombi> Laney: just landed in UI toolkit trunk yesterday
[13:37] <renato_> zsombi, if they implement the date  time using qorganizer this will be possible
[13:37] <zsombi> renato_: ehh....
[13:38] <Laney> zsombi: oh, cool, is that for date & time?
[13:38] <Laney> i.e. what we want for system-settings
[13:38] <kalikiana> aquarius: hmm the structure should be the same as far as I'm aware
[13:38] <zsombi> renato_: hmm.. what pops up the indication? wasn't datetime indicator?
[13:38] <aquarius> kalikiana, it isn't. :(
[13:38] <zsombi> Laney: yes, popped up on OSK area when on phone, and as a popover when on tablet+
[13:39] <Laney> okay, I'll give it a go
[13:39] <Laney> thanks for the info
[13:39] <zsombi> welcome
[13:40] <kalikiana> aquarius: oh, I see now what you mean. tricky.
[13:41] <dpm> zsombi, afaik, yes, it's the datetime indicator that pops up the alarm indicator (charles is working on it)
[13:41] <renato_> zsombi, yes both talks direct with EDS
[13:41] <zsombi> dpm: whet I'm after is what makes the datetime indicator to pop up
[13:41] <zsombi> renato_: ^
[13:42] <aquarius> kalikiana, so you need to do one of these things, I think: break anyone who is using Index and Query, implement an "enable backwards compatibility" switch and make existing Index/Query users turn it on, or implement an "enable fixed queries" switch and make every u1db user from now on use it forever and ever.
[13:42] <zsombi> who triggets the indicator to wake up?
[13:43] <aquarius> kalikiana, I think option 1, break everyone, is the way forward, but it'll require documentation and possibly contacting everyone (at least with a post to ubuntu-phone, but ideally a direct email -- it might be worth talking to, say, beuno, and asking for some way to grep the list of apps in the click store for U1db.Query?)
[13:43] <zsombi> charles: do U have a timer in the indicator which pops up the event when needed?
[13:46] <zsombi> renato_: ok, so the Alarm is somewhat sorted out - I'll come up with it again when I reac there to implement the changes
[13:47] <renato_> zsombi, ok
[13:47] <zsombi> renato_: anothet thing is the StateSaver with your app
[13:47] <zsombi> renato_: so you need to get the app state to be saved in certain circumstances, right?
[13:47] <renato_> zsombi, yes
[13:48] <zsombi> renato_: and that is when the app crashes or gets killed, right?
[13:48] <renato_> zsombi, exactly
[13:49] <zsombi> renato_: ok, this distinction we can do it on teh desktop, but how about the device?
[13:49] <renato_> zsombi, for example right now the close itself in some cases and it cause the state to be saved, what is not what I want
[13:49] <renato_> s/the close/the app close
[13:50] <zsombi> rento_ closes itself means that it crashes?
[13:50] <zsombi> renato_: ^
[13:50] <renato_> zsombi, app.quit()
[13:51] <renato_> and when the page stack destroy the page
[13:51] <zsombi> renato_: so a normal close, right?
[13:51] <renato_> yes
[13:51] <zsombi> renato_: this is not the case on the device, right?
[13:51] <renato_> zsombi, in the device
[13:51] <kalikiana> aquarius: option 1 sounds brutal, though I would agree I don't like the idea of enableFixedQueries - maybe let's hold this a bit and see it in the bigger context of the Synchronzier API additions (https://code.launchpad.net/~kalikiana/u1db-qt/syncWithU1/+merge/202508) and open query bugs. if this can be somehow coordinated the new stuff might overshadow the
[13:51] <kalikiana> pain
[13:52] <zsombi> renato_: what happens when the app gets on the background on the device?
[13:52] <aquarius> kalikiana, it would be brutal if lots of people were using u1db.query, but I bet they are not. I bet there are, say, ten apps at most which use it right now. Fixing it early means it'll stay fixed. :)
[13:52] <zsombi> s/on/to
[13:53] <renato_> zsombi, if the dialer app calls the address book for add a new contact the app will show the page to save the contact and will close itself when the user click on save button
[13:53] <renato_> and will go back to dialer app
[13:54] <zsombi> renato_: hold on, the app gets an argument to know whether it should do a special thing, right?
[13:54] <renato_> zsombi, yes
[13:54] <dpm> zsombi, so in summary, the alarm storage/filtering from different apps could in theory be sorted out with the usage of app-specific collections in EDS, but how to trigger in-app DB-less timers still remains to be discussed, right?
[13:54] <renato_> this is one case
[13:54] <renato_> the other case is if the user close the app manually
[13:54] <zsombi> renato_: awesome. that could be used to say not to use the statesaver in that case
[13:54] <renato_> it should not save the state
[13:55] <zsombi> renato_: the close manually means the app is woken up and closed, right?
[13:55] <renato_> basically is that, if the app quit normally it should not save the sate
[13:55] <zsombi> renato_: is this a requirement from UX?
[13:56] <renato_> I do not know
[13:56] <renato_> this is how I see the things
[13:56] <renato_> for example if the user reset the phone the app should not save the state
[13:56] <kalikiana> aquarius: by the way, have a look at this and see how you like it http://bazaar.launchpad.net/~kalikiana/u1db-qt/syncWithU1/view/head:/examples/notes-cloud/notes-cloud.qml not completely ready just yet since the sync code doesn't push changes back, but working api
[13:56] <zsombi> renato_: well, that's one thing. I'd say it's pretty handy that the app always starts where I left last time.
[13:56] <renato_> zsombi, are you going to orlando?
[13:57] <zsombi> renato_: yes
[13:57] <zsombi> renato_: I sense we will ahve a debate on this :)
[13:57] <zsombi> *have
[13:57] <renato_> zsombi, yes lets do this there with the other app guys
[13:57] <kalikiana> popey: I faintly recall you having some huge archive of click apps in greppable form eons ago? does that still exist? I'd like to assert uses of U1Db.Query
[13:59] <zsombi> renato_: awesome. honestly I see the need to have such a thing, but I'm trying to get the default behavior. I see we could also provide the alternative wheich can be set thru the app setting or runtime, like depending on teh arguments received, will or will not save the state
[13:59] <beuno> well, not all click apps have source code?
[13:59] <renato_> zsombi, what I think is that some app need to do some special actions when it is going to be close, and we should have a signal for that
[13:59] <zsombi> dpm: right (sorry to respond so later)
[13:59] <aquarius> kalikiana, blimey, that's complex UI.
[13:59] <renato_> zsombi, for example a irc app, it need to send a quit message
[13:59] <aquarius> kalikiana, er, complex API, I mean
[14:00] <zsombi> renato_: sure, that's also an extra that you as app need to know. What bothers me the most is that we do not have a clear UXrequirement on these
[14:01] <dpm> zsombi, np, thanks! So a final iteration to make sure I've understood the conclusions. Does this make sense? -> http://pastebin.ubuntu.com/6832147/
[14:01] <kalikiana> aquarius: the example does go out of its way to use it all for debugging - though I'm unsure how much apps would need, for example user not being logged in. I could picture a convenience qml component for that
[14:01] <dpm> renato_, ^
[14:01] <aquarius> kalikiana, ya. I personally think that my code should just call db.sync(remoteURL) and that's it ;-)
[14:01] <zsombi> renato_: so th eonly thing remaining is the timers: how to use Alarm API (QtOrganizer) in a way that timers do not get registered in DB and still would be notified...
[14:02] <kalikiana> aquarius: there is one thing you also need that is bool resolve_to_source
[14:03] <zsombi> dpm: I would also add to Notifications that Clock Timer should not be a notification but should open the app itself when kicked
[14:03] <zsombi> renato_: ^
[14:03] <renato_> zsombi, dpm what is timer notifications?
[14:03] <zsombi> renato_: like the clock timer shpould not show any notification but simply open the app
[14:03] <dpm> zsombi, ack. renato_, on the clock app, there is a timer tab, where you can set a timer (e.g. 5:00). When the timer reaches 0, you would get a notification
[14:04] <dpm> or rather show the app
[14:04] <dpm> as zsombi says
[14:04] <zsombi> dpm: renato_: and thi snot just for the Clock app, but also for any app
[14:04] <renato_> in my point of the view this should be handled by the app
[14:04] <dpm> but how would it handle it if it's not in the foreground?
[14:04] <zsombi> renato_: uhm, but datetimer indicator gets the knowledge when the alarm is triggered...
[14:05] <zsombi> renato_: so it cannot be application
[14:05] <kalikiana> aquarius: but yeah, I wonder if we actually want something like U1db.U1Synchronizer { name: "foo.db", resolve_to_source: true, loginIfNeeded: true }
[14:05] <popey> kalikiana: yeah, it's not up to date though, i can update it and ping you
[14:05] <zsombi> renato_: the app can be on background (tombstoned) so...
[14:06] <zsombi> dpm: renato_: not sure whether we should have trusted helper for that
[14:06] <kalikiana> popey: that would be awesome
[14:06] <zsombi> dpm: renato_: honestly, for such a thing I woudl use crond
[14:06] <renato_> zsombi, maybe the date time indicator should provide some api for that
[14:07] <renato_> since it is running all time
[14:07] <popey> kalikiana: ok, doing
[14:07] <zsombi> renatio_: right!
[14:07] <zsombi> renato_: that's why I wanted timed  to be ported :)
[14:08] <dpm> zsombi, renato_, is that not what charles is working on already? He can probably give us more details when he's up
[14:08] <aquarius> kalikiana, yeah, the credentials stuff. Maybe db.sync(synchronizerItem) where synchronizerItem is a U1db.Synchronizer { url: http://u1db.one.ubuntu.com; credentials: U1Credentials } or similar? I don't understand what name or resolvetosource or loginifneeded are for
[14:09] <zsombi> dpm: renato_ pls, in case U meet him while I'm away, let me know about the status
[14:09] <renato_> zsombi, sure
[14:09] <dpm> zsombi, sure!
[14:09] <zsombi> strong sure :D thx dpm, renato_
[14:09] <dpm> :-)
[14:09] <dpm> thanks guys, that was an excellent discussion
[14:10] <zsombi> my pleasure :)
[14:10] <zsombi> we will continue this in orlando :)
[14:10] <dpm> \o/
[14:12] <kalikiana> aquarius: "name" would be the file on the remote end - it may not match the name on disk, especially given folders aren't allowed on u1db.one.ubuntu.com – I don't think 'credentials' would work very well given that the api is rather arbitrary, it is specialized enough that I would combine it with supplying u1db.one.ubuntu.com, that's what my suggestion was
[14:12] <kalikiana> implying
[14:13] <kalikiana> you cannot actually make use of either without the other
[14:20] <aquarius> kalikiana, that's in the URL, in my opinion?
[14:21] <dpm> hey boren, how are you?
[14:21] <aquarius> kalikiana, you can't combine the credentials with the URL, because the credentials are used to *sign* the URL
[14:21] <aquarius> that's oauth.
[14:22] <boren> dpm, feels perfect. Have a day off school because of extreme weather.
[14:22] <kalikiana> aquarius: yes, you have 2-3 different credentials for one go, so it cannot be a static value. plus the signing happens async and *may* require user intervention if they're not logged in
[14:22] <aquarius> kalikiana, and ideally my app would never actually have access to the U1 credentials directly -- in an ideal world I'd pass a URL to Online Accounts and it would give me back that URL signed with my U1 credentials, but i'm not sure mardy agrees with that ;)
[14:22] <dpm> boren, oh, wow
[14:23] <kalikiana> aquarius: well, that is what you have there *if* you are logged in
[14:23] <mardy> aquarius: you are talking about the OAuth 1.0a signature, or something else?
[14:23] <dpm> boren, just saying hi, and let us know if there is anything we can help with :)
[14:23] <aquarius> kalikiana, ya, but if I'm not logged in, it's not my app's job to log me in to U1, it's Online Accounts's job.
[14:23] <aquarius> mardy, ya, oauth 1.0
[14:24] <boren> dpm, you were talking about let me join the core app team, how does it work?
[14:24] <aquarius> kalikiana, if I'm not using u1 but some other u1db server with a different login method, sure, but that's different :)
[14:24] <dpm> boren, well, you've done the hardest part already, which is submitting your first contributions :)
[14:25] <kalikiana> aquarius: mardy: the example has ui asking for login only for the case where the user isn't signed in, in which case it just signs urls - I don't know of any way to make the login happen "magically"
[14:25] <dpm> boren, then the next thing is to pick an app you'd be interested in contributing to. That's really up to you which one you pick, but perhaps the one where we need most help right now is the reminders app
[14:26] <dpm> boren, would you be interested in that one?
[14:26] <aquarius> kalikiana, ya, but I think that online accounts should make it happen magically. If my app says "hey, online accounts! sign this URL with my U1 credentials!" and I haven't *got* any U1 credentials, then it is online accounts's job to get some, possibly by popping up a login window. But as i say mardy might disagree with that. Also, if you haven't got U1 credentials then you can't install apps from the click st
[14:26] <aquarius> ore ;)
[14:27] <boren> boren, yes, I will first try to fix somg bitesize bugs you mentioned.
[14:27]  * mardy is on a meeting, will reply later
[14:27] <boren> dpm, yes, I will first try to fix somg bitesize bugs you mentioned.
[14:28] <kalikiana> aquarius: you'll at the least have preinstalled apps using u1
[14:28] <kalikiana> and you'd want to be asked to sign in if they have a sync feature
[14:29] <aquarius> ya
[14:30] <kalikiana> aquarius: strictly speaking I'm not sure if having the UI in the accounts API would just make it work. you still need to handle the credentials passing
[14:30] <dpm> boren, cool. https://bugs.launchpad.net/reminders-app/+bug/1273111 might be a good one to start with. Also, tomorrow at around this time we've got a meeting to discuss development of Reminders. If you want to join us, let me know and I'll send you an invite
[14:30] <ubot2`> Launchpad bug 1273111 in Ubuntu Reminders app "Font size in notes must be bigger" [Medium,Triaged]
[14:33] <boren> dpm, I have got class in the morning. I think I will pass
[14:33] <timp> dpm: is reminders app a new name for notes app?
[14:34] <dpm> boren, ok, no worries!
[14:35] <dpm> timp, there have been some discussions about phasing out the Notes app and have Reminders be the new (and only) Notes app. So we might even need to do some Reminders -> Notes renaming soon
[14:35] <dpm> mzanetti, ^
[14:35] <mzanetti> waahh
[14:36]  * mzanetti doesn't want to store all his notes online
[14:37] <dpm> that's a valid point we will need to forward to the design team, perhaps we could have an offline mode for those who don't want to associate an online acount with it
[14:38] <timp> dpm: ok I was a bit confused because the apps seem to do something similar
[14:38] <dpm> indeed
[14:38] <timp> makes sense to keep only one
[14:39] <mzanetti> there's one bit difference: one requires you to have an evernote account, the other doesn't
[14:39] <kalikiana> dpm: offline mode sounds as if it breaks when there's no network. I hope it's more robust than that
[14:39] <mzanetti> its not right now
[14:39] <timp> in general I don't mind storing stuff online. but I don't have evernote and it is not nice to be forced to get an account
[14:39] <mzanetti> exactly
[14:39] <mzanetti> and well, I do mind storing stuff online
[14:40] <mzanetti> I understand that's a personal thing tho
[14:40] <mzanetti> still, we can't force everyone to either user evernote or not keep notes
[14:40] <timp> I have a simplenote account. It would be cool if reminders supported several online note-saving/syncing accounts, which are all optional
[14:40] <mzanetti> which the code really is not prepared for
[14:41] <dpm> I'm sure there will be others who'll be thinking the same, and we will need to discuss an option for that. For now I just wanted to clarify the confusion between the status of the two apps
[14:41] <dpm> and get everyone involved in the loop
[14:42] <dpm> rather than clarifying the confusion, I wanted to _clear_ the confusion :)
[14:42] <mzanetti> dpm: not sure which one you succeeded with :D
[14:42] <dpm> hahaha, at least I got 50% success rate
[14:43] <timp> it got cleared up for me :) currently there are two notes apps, notes-app is offline and reminders-app syncs with evernote. But in the future it would be nice to have only one with optional online storage of notes
[14:43] <mzanetti> yeah...
[14:44] <mzanetti> but this comes quite late as a requirement for the reminders app tbh
[14:44] <timp> for me the ideal way to store notes online would probably be using ubuntu one or dropbox
[14:44] <dpm> mzanetti, this is not a requirement by all means
[14:45] <timp> just save text files
[14:45]  * timp is just thinking out loud. maybe in 1h I'll think I was typing nonsense
[14:46] <dpm> everyone likes writing notes and todos apps :)
[14:46] <mzanetti> that's true
[14:46] <mzanetti> I'm actually wondering why we only have 2 shopping list apps in the store
[14:46] <dpm> :)
[14:46] <mzanetti> usually they're like 50% of the apps in the store
[14:48] <boren> How to build reminder-app. It failed with this message:"[ 95%] Built target evernoteplugin            cp: 'src/plugin/Evernote/qmldir' and 'src/plugin/Evernote/qmldir' are the same file". I run "cmake . && make " in the root directory of reminder-app.
[14:49] <dpm> mzanetti, we're going ahead with the plan as it is, no changes in the requirements/blueprint, it's just that at some point in the future we will be merging the two apps. If that merging will mean that the Reminders app replaces Notes or if there will be an offline backend for Reminders, remains to be discussed
[14:49] <mzanetti> interesting... boren, do an out of source build
[14:49] <mzanetti> boren: as in: mkdir builddir; cd builddir; cmake ..; make
[14:49] <dpm> but in any case, an offline backend for Reminders would be out of scope for 14.04
[14:51] <dpm> boren, what you can also do is to open the app in Qt Creator and let Qt Creator invoke cmake and do the build. You can do that by starting Qt Creator and then opening the top CMakeLists.txt file as the project file.
[14:51] <dpm> boren, then you can press the big green play button to do the build and run the app
[14:52] <dpm> boren, you'll need to do 'sudo apt-get install libboost-dev libssl-dev' in case you didn't have these packages installed for the build to succeed
[14:53] <aquarius> mzanetti, ya -- I expect that there will be a zillion notes apps once we get going. Having one app that tries to do everything is, I think, a bad idea -- lots of small apps, not big monolithic things, that's the way forward.
[14:53]  * mzanetti tends to agree
[14:55] <kaimast> do ItemLayouts inheirt the size of the item?
[15:01] <boren> mzanetti, after I run "cmake ..", there is no Makefile in builddir. So I cannot run make
[15:01] <boren> mzanetti, I remove the cache, it works
[15:03] <mardy> aquarius: so, for signing OAuth 1.0a requests, IIRC you need the secret token and the consumer key, both of which can be retrieved from OA (not the username and password)
[15:03] <popey> kalikiana: http://people.canonical.com/~alan/20140128_clicks/  lots of clicks
[15:03] <aquarius> mardy, agreed.
[15:03] <mardy> aquarius: however, currently the U1 plugin is not using OAuth 1.0a
[15:03] <aquarius> mardy, what's it using?
[15:03] <mardy> aquarius: and as far I've been told some time ago, it won't use it
[15:03] <mardy> aquarius: ATM, just username and password
[15:04] <mardy> aquarius: they will write an authentication plugin for signond, specific for U1
[15:04] <mardy> aquarius: so it may be that they'll add a way for the client to pass a URL and have it signed
[15:06] <aquarius> mardy, um. But you have to use oauth in order to talk to U1 APIs.
[15:08] <mardy> aquarius: mmm... I don't think so: if you create an account from Ubuntu Touch, you won't see anything web based; it's all done programmatically
[15:08] <aquarius> mardy, and the click scope does exactly that. So it must be getting the oauth credentials from somewhere... although I do not know where. kalikiana, it might be worth you getting together with ralsina or alecu or someone and working out how best to do this
[15:08] <aquarius> mardy, definitely -- you can use the username and password to talk to SSO and get oauth credentials
[15:08] <aquarius> mardy, but you need the oauth credentials to talk to U1 APIs that aren't SSO.
[15:08] <mardy> aquarius: ah, maybe that's what they are doing
[15:09] <aquarius> mardy, it is entirely possible that the click scope asks OA for the credentials and then does the oauth itself
[15:09] <aquarius> mardy, but since every app that wants to talk to U1 will have to do that, it would be nice if OA provided it somehow :)
[15:09] <alecu> aquarius: we store oauth tokens in OA
[15:09] <aquarius> still, this is nothing to do with me, these days ;)
[15:10] <mardy> aquarius: the only thing I know, is that currently OA is only used to store the U1 credentials, and that it's only a temporary solution
[15:10] <aquarius> alecu, ah... and you fetch the oauth tokens from OA and then oauth0sign requests yourself?
[15:10] <alecu> aquarius: sounds like it. What is to do with you these days, btw? :-)
[15:10] <aquarius> alecu, see http://www.kryogenix.org/ :-)
[15:10]  * alecu looks
[15:11] <aquarius> basically, the click scope needs to talk to a U1 API, and so asks OA for oauth tokens and then signs its API requests with those tokens. U1DB.Synchronizer needs to do the same thing, so maybe the best way is for U1DB to do that as well, kalikiana... ask OA for tokens.
[15:12] <aquarius> mardy, alecu, if we do not *have* U1 credentials when the click scope asks, is it the click scope's job to get them, or OA's job?
[15:13] <alecu> kalikiana: I suggest you use the ubuntuone-credentials library to get at those credentials, let me find the state of that library regarding 3rd party apps
[15:13] <alecu> aquarius: it's OA's job. Well, it's the u1 plugin inside OA's job
[15:13] <alecu> we need a plugin there due to the sso ping and friends
[15:14] <mardy> alecu: so it's basically and OAuth 1.0a plugin, with some added functionality?
[15:15] <kalikiana> alecu: aquarius mardy: I'm not sure what you are discussing right now - the sync branch of u1db-qt uses UbuntuOne API in qml to sign URLs with OAuth
[15:15] <alecu> mardy: I don't know the details of that plugin, but we can ask mmcc or dobey about that.
[15:16] <alecu> mardy: all I know is that I ask ubuntuone-credentials, and it fetches them from OA for me :-)
[15:16] <alecu> mardy: and if they are not there, then the click scope shows an error message and tells the user to login/register in OA
[15:16] <kalikiana> the only open question from my pov is how to handle a not signed in or not registered user without re-implementing it in every app
[15:17] <alecu> kalikiana: ah, great. How do you get the u1 creds when they are available?
[15:18] <kalikiana> alecu: signUrl(url,method) → one of two signals gets me the creds or tells me it failed
[15:19] <kalikiana> just the whole thing becomes some 20 or 50 lines of qml easily right now if you handle all the details
[15:21] <kalikiana> alecu: http://bazaar.launchpad.net/~kalikiana/u1db-qt/syncWithU1/view/head:/examples/notes-cloud/notes-cloud.qml
[15:23] <alecu> kalikiana: in the click scope, if there are no credentials (or the credentials are wrong), we show an error message with a button that says "Go to Accounts". That button tells the dash to open this url: "settings:///system/online-accounts"
[15:31] <kalikiana> alecu: oh. can that be opened from a normal qml app? then basically this would handle all the cases like registration/ login, right?
[15:35] <alecu> kalikiana: I'm not sure how that can be opened from a normal qml app, but that's the way to go, yes.
[15:35] <alecu> kalikiana: I would check for something on the SDK to open such urls, and if it's not there, then it should be added.
[15:36] <oSoMoN> balloons, hey, I submitted https://code.launchpad.net/~osomon/ubuntu-calendar-app/tests-unset-locale/+merge/203574 to fix bug #1268574, would you mind reviewing?
[15:36] <ubot2`> Launchpad bug 1268574 in Ubuntu Calendar App "Autopilot tests assume English locale" [Medium,In progress] https://launchpad.net/bugs/1268574
[15:36] <balloons> oSoMoN, sure thing
[15:36] <oSoMoN> thx!
[15:37] <balloons> oSoMoN, did you get a chance to look at carla's bug?
[15:37] <oSoMoN> balloons, yes, I marked it invalid and explained why in a comment
[15:38] <balloons> a-hah.. indeed, so this knocks out that bug as well
[15:39] <balloons> well "bug"
[15:52] <charles> dpm, zsombi, renato__: what I'm working is a C API for third parties to interact / create the alarms that get processed by indicator-datetime, using the same EDS backend renato__'s code uses for the clock app
[15:52] <charles> indicator-datetime will dogfood the C API
[15:54] <zsombi> charles: ok... so that C API will also use some EDS databases then, right?
[15:56] <charles> zsombi: right, along the same lines of renato__'s qtorganizer-eds that gets used by the clock app
[15:56] <zsombi> charles: damn... we need something which does not land in any DB...
[15:57] <charles> why?
[15:57] <zsombi> charles we need something like chrond: to wake up an app on a given time
[15:57] <zsombi> charles: Clock app countdown timer is one example
[15:58] <zsombi> charles: we need to have th etime running while the app is bg
[15:58] <charles> ah, gotcha
[15:59] <oSoMoN> balloons, thanks for the review
[15:59] <oSoMoN> balloons, another trivial one for you, when you have a minute: https://code.launchpad.net/~osomon/ubuntu-calendar-app/unittests-cmake/+merge/203577
[16:00] <balloons> ahh, adding unit tests, good call
[16:19] <oSoMoN> balloons, hold off approving it for now, I just saw that there is an override_dh_auto_test in debian/rules that can probably go away with this
[17:09] <oSoMoN> balloons, ok, I updated https://code.launchpad.net/~osomon/ubuntu-calendar-app/unittests-cmake/+merge/203577, it’s now ready for review
[17:11] <balloons> noted
[17:30] <WebbyIT> Hello mzanetti :-) Sorry to disturb you again! So, I started to work on RTF and have a first implementation of the function. There are a lot of issues, but I think I can fix them!
[17:30] <WebbyIT> Could you give me an opinion on the approach, please? :)
[17:30] <WebbyIT> https://code.launchpad.net/~rpadovani/reminders-app/startedRTFMode/+merge/203599
[17:30] <WebbyIT> I proposed the merge only to have diff file
[17:35] <mzanetti> WebbyIT: hi
[17:36] <mzanetti> WebbyIT: cool, will have a look
[17:39] <mzanetti> WebbyIT: hmm... the rtf panel is empty here. is that expected?
[17:40] <WebbyIT> mzanetti, there would be bold icon
[17:40] <WebbyIT> mhh, probabily icon I used it isn't present on 14.04
[17:40] <mzanetti> yeah... I guess so... just looking
[17:40] <WebbyIT> during the weekend I'll try and upgrade to 14.04
[17:41] <WebbyIT> *an
[17:41] <mzanetti> yep, its the icon
[17:41] <mzanetti> I think its because you didn't use one from the ubuntu-mobile-icons package
[17:42] <mzanetti> but no problem for now
[17:42] <mzanetti> try to stick to the icons from the ubuntu-mobile-icons package
[17:42] <WebbyIT> ok
[17:43] <mzanetti> ok, so: I think this is the right approach! very good!
[17:43] <mzanetti> Not sure what other issues we will hit going forward, but I think I would try the same approach for now
[17:44] <mzanetti> I'll leave a comment on the MP for a few coding style alignments with the rest.
[17:44] <mzanetti> but cool stuff! looking forward to your upcoming stuff!
[17:44] <WebbyIT> mzanetti, thanks :)
[17:44] <WebbyIT> I'll ping you when I'll have upgrade!
[17:45] <mzanetti> awesome
[17:56] <mzanetti> WebbyIT: https://code.launchpad.net/~rpadovani/reminders-app/startedRTFMode/+merge/203599/comments/475167
[18:03] <WebbyIT> mzanetti, ok, thanks, I'll take a look, if I need something I'll ping you :-)
[18:03] <mzanetti> ok. have fun!
[19:02] <stefano92100> HI everybody, I don't know how is the workflow now, but if it's still not assigned, I can start to work on this (I think I still have the code I wrote for the mockup): https://bugs.launchpad.net/ubuntu-clock-app/+bug/1270092
[19:02] <ubot2`> Launchpad bug 1270092 in Ubuntu Clock App "Not able to change "Repeats" setting in AddAlarm page when "Daily" value is set" [Medium,Triaged]
[19:02] <stefano92100> nik90: you wrote some days ago about it, do you have more information?
[19:02] <nik90> stefano92100: hey
[19:03] <nik90> stefano92100: I can in detail post the instructions for the workflow. I am having dinner at the moment. Can I get back to you in another 20-30 minutes?
[19:03] <nik90> stefano92100: also your design is good to go btw. :)
[19:04] <stefano92100> No problem, have a good dinner!
[20:55] <boren> How to set up Evernote account on phone? It shows that my account or password is incorrect in the online account setting.
[20:57] <boren> After I run the reminder app, and the app stuck at the add note button. I cannot go into the online account setting page again.
[20:58] <ybon> boren: wasn't that the app works only with sandbox accounts?
[21:05] <samertm> If no one is currently working on it, I'm going to start on https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1273555
[21:05] <ubot2`> Launchpad bug 1273555 in Ubuntu Calculator App "Pressing minus and plus keys followed by a number produces odd results" [Medium,Triaged]
[21:14] <nik90> hey WebbyIT, you are also using the Difficulty information in the hackday bugs eh :P
[21:17] <nik90> samertm: if the bug is not assigned to anyone, feel free to take it
[21:38] <labsin> popey, if you're interested, I got it working on the phone. http://ubuntuone.com/2ECSspw1A5N1RwKdcTh1BM
[21:39] <labsin> *emulator
[21:39] <popey> cool!
[22:01] <nik90> renato_: hey I updated bug 1272333 with the sample app. I am starting to receive multiple reports from people about alarms not being saved properly. I hope we can first confirm the issue on your side.
[22:01] <ubot2`> Launchpad bug 1272333 in Ubuntu Clock App "Saving an alarm does not work reliably" [High,Triaged] https://launchpad.net/bugs/1272333
[22:02] <renato_> nik90, ok thanks, i will take a look tomorrow
[22:03] <nik90> renato_: ok
[23:56] <WebbyIT> nik90, I learned from the master ;-)
[23:57] <WebbyIT> samertm, please assign the bug to yourself ;-) If you need an help feels free to ask here :-)