[00:00] <aquarius> what you want is img[data-ubuntu-icon] { generated-attr(src): "file:///icon/path/" + attr(data-ubuntu-icon); }
[00:00] <aquarius> which css can't do :)
[00:00] <aquarius> you can use the values of attrs in generated content, but you can't *set* the value of an attribute with generated content
[00:01] <aquarius> so you'd need an onload handler
[00:01] <aquarius> since we don't handle dom mutation observers at all, afaict, and Chrome doesn't handle observers on a whole subtree (only on generated children) unless I'm doing it wrong :)
[00:02] <aquarius> ah, no, I bet subtree does work, but it snapshots the target at observer.observe so newly-added elements aren't part of the subtree. Darn.
[00:02] <aquarius> could just inhale everything in ubuntu-mobile-icons into UbuntuUI.css at build time ;)
[00:03] <aquarius> div[data-ubuntu-icon="microphone"] { background-image: url(file:///icon/path/microphone.svg); }
[00:03] <aquarius> but that's horrid.
[00:04] <aquarius> So I suppose it'd have to be either a magic translate-to-data-url handler, or UbuntuUI parsing.
[00:06] <aquarius> and the translate-to-data-url thing would need a native code hook; you can't do it in pure JS, unless you're prepared to use sync XHRs, which are a sin.
[00:10] <aquarius> Current best effort:
[00:10] <aquarius> <img src="theme:microphone">
[00:10] <aquarius> and then, ondmcontentloaded:
[00:11] <aquarius>     Array.prototype.slice.call(document.querySelectorAll('img[src^="theme:"]')).forEach(function(i) {
[00:11] <aquarius>         i.src = "file:///usr/share/icons/ubuntu-mobile/actions/scalable/" + i.src.replace(/^theme:/,'') + ".svg";
[00:11] <aquarius>     });
[00:11] <aquarius> which is mildly horrid, but only mildly, and the qSA engine is doing most of the work.
[00:13] <aquarius> mhall119, you could add that yourself to your HTML if you wanted it, in advance of a more permanent solution. YOu're still hardcoding the long path, but at least it's only in one place.
[00:15] <aquarius> anyway, time for bed, before daker punches me for making up a url scheme ;)
[00:15] <aquarius> ttfn, all.
[00:15] <aquarius> uds on the morrow. :)
[00:38] <daker> :)
[05:02] <BobJonkman1> Hi: Are Ubuntu SDKDays still ongoing? I just updated the Wiki page to include the year (2013) for the event listed there: https://wiki.ubuntu.com/UbuntuSDKDays
[06:51] <zsombi> nik90: ping
[07:20] <useryy> As an android developer, how to port my apps to Ubuntu mobile? Any tools or tips?
[07:56] <sridhar_> pllzzz help ....installed 14.04 dual boot with 13.10 go error in 14.04 Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[07:56] <sridhar_> plzzzz help
[07:56] <sridhar_> Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[07:57] <sridhar_> Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[08:54] <JamesTait> Good morning all; happy Organize Your Home Office Day! :-D
[09:01] <justCarakas> dakar: where you able to find something out about the datapicker ?
[09:09] <justCarakas> goodmorning JamesTait
[09:09] <JamesTait> justCarakas, o/
[09:11] <aquarius> justcarakas: there are about a zillion input type="date" polyfills; just have a google around and choose your favourite one which is touch compliant, until input type=date handling arrives in the Ubuntu browser
[09:12] <justCarakas> okidoki :) thx :)
[09:13] <justCarakas> aquarius, wasn't sure and didn't want to make a design mistake :p
[09:13] <mzanetti> rpadovani: good morning. I thought I had approved that already.
[09:13] <aquarius> justCarakas, yeah; daker mentioned yesterday bug 1170136 and bug 1170138 which you may want to mark as affecting you, and track so that you can see when a fix lands
[09:13] <ubot2`> Launchpad bug 1170136 in webbrowser-app (Ubuntu) "[browser] Add support for HTML5 date input" [Medium,Confirmed] https://launchpad.net/bugs/1170136
[09:13] <ubot2`> Launchpad bug 1170138 in webbrowser-app (Ubuntu) "[browser] Add support for HTML5 time input" [Medium,Confirmed] https://launchpad.net/bugs/1170138
[09:15] <justCarakas> already marked it
[09:15] <aquarius> cool. :)
[09:15] <justCarakas> :) thx
[09:15] <justCarakas> to bad I cant work on it now since I'm at work :p
[09:22] <nik90> zsombi: pong
[10:12] <zsombi> zsombi
[10:12] <zsombi> hehe
[10:12] <zsombi> me is :)
[10:12] <zsombi> nik90: there's one more SDK Alarm API MP 4 U to tes
[10:13] <zsombi> nik90: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/alarm-date-fix/+merge/210181
[10:14] <nik90> zsombi: testing
[10:15] <zsombi> nik90: when running the unit tests on desktop, I get loads of alarm notifications :)
[10:15] <nik90> zsombi: lol
[10:15] <zsombi> nik90: the first time sice we're having this API
[10:15] <nik90> zsombi: I got the notifications on desktop the past week
[10:16] <zsombi> nik90: lucky you :)
[10:16] <ahayzen> dpm, ping
[10:16] <nik90> zsombi: well I did create alarms for like 10:00 PM...so it shows up while watching a tv show sometimes :P
[10:19] <zsombi> nik90: LOL
[10:20] <dpm> hey ahayzen
[10:20] <zsombi> nik90: 4 me this was the first time I get alarm notes while running unit tests, which feels awesome :D
[10:20] <ahayzen> dpm, would u mind having a check over this MP https://code.launchpad.net/~vthompson/music-app/fix-1290492-music/+merge/210316
[10:20] <ahayzen> dpm, i don't know how translations work so don't want to approve something tht will break them ;)
[10:20] <dpm> ahayzen, sure, on it :)
[10:20] <ahayzen> dpm, thanks
[10:23] <nik90> zsombi: yay it is saved in the correct timezone!
[10:23] <nik90> zsombi: so the one remaining issue is that the alarm doesn't get updated in the indicator when I edit it
[10:23] <zsombi> nik90: :) so this was the one you were waiting of, right? ;)
[10:23] <nik90> zsombi: yup!
[10:24] <mzanetti> nik90: hey
[10:24] <mzanetti> nik90: just trying the current clock app
[10:24] <zsombi> nik90: ok, and I guess renato is on it, right?
[10:24] <nik90> zsombi: what happens if I change my timezone?
[10:24] <nik90> zsombi: not sure
[10:24] <nik90> mzanetti: hey
[10:24] <mzanetti> nik90: alarms, in specific.
[10:24] <mzanetti> nik90: and I thought it'd be great if the alarms page could show the time until the next alarm goes off
[10:24] <zsombi> nik90: it should kick according to that timezone, at the same time as on your previous one
[10:25] <zsombi> nik90: so if you set an alarm to kick @ 8AM UTC+2 it will kick @8AM UTC+10 too
[10:25] <nik90> zsombi: awesome
[10:25] <zsombi> nik90: I think so too :D
[10:25] <mzanetti> right now I made the mistake to mess up with AM/PM. If there would be some label somewhere saying "20:47 to the next alarm" or something like that, it would make it more obvious
[10:26] <nik90> mzanetti: atm it shows the next immediate alarm time but doesn't show the time to the next alarm.
[10:26] <mzanetti> nik90: also, when I set up an alarm in the evening I always liked when a phone told me "You've got 6:30 left to sleep" or the like
[10:26] <nik90> mzanetti: but I believe this was part of the original design..so I will get on that when I get some time
[10:27] <zsombi> mzanetti: push a wishlist to clock app :)
[10:27] <mzanetti> nik90: imo it would be enough to show this countdown just once for the next alarm. no need to have it for all alarms
[10:27] <nik90> mzanetti: can you file a bug so that I dont forget
[10:27] <mzanetti> nik90: maybe just replace the "current time" with that countdown in the alarms page? You can see the current time in the panel anyways
[10:27] <mzanetti> ok. I'll file a bug
[10:28] <nik90> zsombi: I see charles's branch as well for the tz fix at https://code.launchpad.net/~charlesk/indicator-datetime/lp-1283236
[10:28] <nik90> zsombi: is this required?
[10:29] <mzanetti> nik90: and it failed to trigger the alarm :/
[10:29] <zsombi> nik90: that's a good question... I dopn'y think that will nbe required as now it works without his one
[10:30] <zsombi> don't (I meant)
[10:30] <nik90> mzanetti: we have a few daily blocker bugs concerning alarms which is what zsombi, charles and renato are working atm.
[10:30] <mzanetti> ah ok
[10:30] <nik90> mzanetti: Also it seems that if your phone goes to deep sleep, the notification won't appear
[10:31] <nik90> mzanetti: I believe there is some more platform work that need to be done for that
[10:31] <mzanetti> nik90: ah ok. yeah. the phone was in deep sleep
[10:31] <zsombi> nik90: yes, for that there's no support yet :(
[10:31]  * mzanetti wanted to test if the alarm boots the phone when its off, but I guess I can skip that for now :)
[10:32] <nik90> zsombi, mzanetti: I talked to pat about this who said it was definitely a priority and should land soon enough
[10:32] <zsombi> mzanetti: if you want that, you should port UTouch to Nokia X :D
[10:32] <mzanetti> zsombi: why is that?
[10:32] <zsombi> mzanetti: they have that feature in those ;)
[10:33] <mzanetti> zsombi: that worked with every phone I had so far, except the openmoko
[10:33] <dpm> ahayzen, approved with comments
[10:33] <dpm> thanks for the heads up!
[10:33] <zsombi> mzanetti: I didn't get it working with the Android I had and with iOS either...
[10:34] <mzanetti> really?
[10:34] <zsombi> yep
[10:34] <ahayzen> dpm, thanks :) i'll let Victor see them before top approving
[10:34] <mzanetti> find it hard to blieve that
[10:34] <zsombi> I haven't seen it working in Moto either
[10:34] <dpm> ahayzen, no worries, it looked good to me, so I wrote the comment and top-approved already
[10:34] <ahayzen> dpm, ah cool :)
[10:34] <nik90> zsombi: In https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1283236, can I mark the other projects invalid since a fix in UITK seemed to have solved the issue
[10:34] <ubot2`> Launchpad bug 1283236 in Ubuntu UI Toolkit "Alarms are triggered in UTC tz despite saving in local tz" [High,In progress]
[10:36] <mzanetti> zsombi: just googled around. indeed android and iphones don't do that. all others do
[10:36] <zsombi> nik90: strange.... looks like renato hasn't attached his MR to it as I know he did some fixes in EDS because of which the solution I have works...
[10:36] <zsombi> mzanetti: you see????! I told ya!!! :D
[10:36] <mzanetti> zsombi: but but...
[10:36] <nik90> zsombi: I am guessing those EDS fixes have already landed then in trunk?
[10:36] <mzanetti> that's essential
[10:36] <zsombi> nik90: yeps
[10:37] <zsombi> mzaneti: you're telling me??! yes, those are :)
[10:37] <zsombi> mzanetti: especially 4 one who got used to hve nokias ;)
[10:37] <mzanetti> zsombi: in that case you can never trust that alarm
[10:37] <mzanetti> what happens if the battery drains? no alarm? thats useless
[10:37] <nik90> zsombi: oh btw, your branch alarm-fetch-fix also fixes the issue of editing single-alarms that I asked pat to test.
[10:38] <zsombi> nik90: yeah... there were problems with the alarm fetching, especially with the recurring ones: the alarm date was always the main alarm's one :(
[10:38] <zsombi> nik90: sorry 4 that
[10:39] <nik90> zsombi: so those 2 MPs you got now are *GOLDEN*.
[10:39] <zsombi> mzanetti: and when you recharge yr phone, suddenly all the alarms will kick :D
[10:39] <zsombi> nik90: ahhhh.... feels so good :D
[10:39] <nik90> :D
[10:39] <zsombi> nik90: sorry 4 being late with it, I had some urgent bugs to fix, and was a bit tricky...
[10:40] <zsombi> now, I gotta go back to ComboButton
[10:40] <nik90> zsombi: no no I was busy with AP tests anyway...so couldn't have tested your fixes..the timing is good
[10:41] <nik90> zsombi: ok
[10:41] <zsombi> nik90: are there any flaky tests in clock App?
[10:41] <nik90> mzanetti: btw nice work on the expanding listitems..been eagerly waiting for those for a long time
[10:41] <mzanetti> nik90: are you using it now?
[10:41] <nik90> zsombi: nope...we are 100% confident they are all good.
[10:41] <zsombi> nik90: awesome!
[10:42] <nik90> mzanetti: I am investigating on how to integrate them into my flashback app
[10:42] <mzanetti> nik90: please let me know how it works, if the api is nice to use etc
[10:42] <nik90> mzanetti: definitely
[10:42] <mzanetti> nik90: cool. thanks
[10:42] <zsombi> nik90: one more request: could you pls comment on the two MPs from apps point of view? thx
[10:43] <nik90> zsombi: sure
[10:53] <nik90> zsombi: I created an alarm for 11:50 UTC+1, which it created at the correct time and also rang at the correct time.
[10:54] <nik90> zsombi: however If I move to UTC, then the alarm time changed to 10:50 and also the alarm did not ring at 10:50
[10:56] <nik90> zsombi: also when I create an alarm in 11:58, it gets saved as 10:58 without changing timezones anymore
[11:06] <zsombi> nik90: you save an alarm in UTC format, but your local is not UTC, right?
[11:07] <nik90> zsombi: no I changed my local to UTC from the system settings app and then created an alarm for 10:00 AM. But the indicator and clock app shows it as 09:00 AM
[11:07] <zsombi> nik90: Alarm API ALWAYS saves the date in UTC, it transcodes into UTC (meaning your local 8AM will end up in 8am UTC)
[11:07] <nik90> zsombi: however If I restart the phone after the locale change and then create an alarm, things works as expected.
[11:08] <zsombi> nik90: perhaps this is what charles' branch is solving...
[11:08] <zsombi> nik90: the no-need-to-restart issue...
[11:09] <nik90> zsombi: I think so.
[11:09] <nik90> zsombi: I am anyway reporting everything I test in the MP so we dont lose this. I will also contact charles and confirm the issue
[11:09] <zsombi> nik90: let's wait till he is getting his stuff in
[11:09] <zsombi> nik90: ok
[11:38] <nik90> dpm, popey: We got a code red. Clock, Calculator and weather are not opening on #image 230. Music, Calendar, Shorts are fine.
[11:39] <nik90> dpm,popey: On opening clock, I just get a white screen. This was also mentioned by someone in the landing email as well.
[11:39] <dpm> nik90, any debug output?
[11:39] <nik90> dpm: do I adb shell into the phone and then run clock app to get output?
[11:40]  * nik90 tries now
[11:40] <nik90> dpm -> qmlscene: could not exec '/usr/lib/arm-linux-gnueabihf/qt4/bin/qmlscene': No such file or directory
[11:41] <dpm> Mirv, any ideas why on some apps (clock, calculator, weather) we're trying to load qt4's qmlscene? See the log above after launching clock on image #230 ^^
[11:42] <dpm> I need to run now, I'll be back in a bit
[11:42] <nik90> dpm: actually I get that output while trying to open music app despite it running fine on the phone. How do I run the clock app?
[11:42] <nik90> dpm: ok
[11:44] <Mirv> dpm: if the user does not select Qt version to use, qtchooser falls back to Qt4 for backwards compatibility. in other words, use qmlscene -qt5 file.qml, or export QT_SELECT=qt5 before running qmlscene. note that on the devices QT_SELECT=qt5 should be set globally
[11:45] <Mirv> it's in /etc/environment
[11:45] <Mirv> and nik90 ^ too
[11:45] <nik90> Mirv: how does one launch a core app?
[11:46] <nik90> Mirv: I feel like I am doing it the wrong way
[11:46] <dpm> nik90, http://pastebin.ubuntu.com/7073077/
[11:46] <dpm> I hope that helps
[11:47] <chihchun> hi, my app got rejected due to lint_maintainer_domain
[11:47] <chihchun> where I can change email field? from developer portal ?
[11:47] <Mirv> thanks dpm, I've been wondering about it myself too, how to start apps from command line :)
[11:48] <chihchun> !
[11:48] <chihchun> I got it, it's in manifest.json
[11:52] <nik90> dpm, Mirv: http://paste.ubuntu.com/7073099/
[12:29] <renato> nik90, zsombi, hi
[12:30] <nik90> renato: hi
[12:30] <renato> looks like we have a good progress on the alarms bugs
[12:30] <renato> nik90, anything missing?
[12:30] <nik90> renato: yup :)
[12:31] <nik90> renato: we still have the alarms not updated in the indicator-datetime after we edit and save an alarm
[12:31] <nik90> renato: but I think that is something charles needs to fix
[12:31] <renato> charles, ^^^
[12:32] <nik90> but renato can you fix https://bugs.launchpad.net/ubuntu/+source/qtorganizer5-eds/+bug/1272337 when you have time
[12:32] <ubot2`> Launchpad bug 1272337 in Ubuntu Clock App "EDS reverts alarm status immediately" [High,Triaged]
[12:32] <nik90> renato: it is a hassle to delete an alarm in order to disable it :)
[12:32] <renato> zsombi, knows more about that ^^^
[12:32] <renato> he told me that is a binding loop on SDK component
[12:32] <nik90> renato: ah ok..I was not aware of that
[12:36] <zsombi> renato: about what do I know more?
[12:36] <renato> zsombi, https://bugs.launchpad.net/ubuntu/+source/qtorganizer5-eds/+bug/1272337
[12:36] <ubot2`> Launchpad bug 1272337 in Ubuntu Clock App "EDS reverts alarm status immediately" [High,Triaged]
[12:36] <renato> zsombi, do you remember that we discuss that during the spring in Orlando?
[12:37] <zsombi> renato: aah, yes, that's teh problem of the switch/checkbox in general
[12:37] <zsombi> nik90: ^
[12:37] <nik90> zsombi: anyway we can fix that? an issue as small as that is important to users
[12:39] <zsombi> nik90: need to check the code, how the switch takes the alarm data and how the alarm data is updated
[12:40] <nik90> http://paste.ubuntu.com/7073280/
[12:42] <zsombi> nik90: yeah.. .I remember now... well, the model changes there, therefore the checked will also get changed, and that causes sometimes to re-enable the alarm :(
[12:43] <zsombi> nik90: I have the enabling in the same way in the testapp
[12:43] <nik90> zsombi: yeah I copied that code from your testapp :)
[13:31] <zsombi> nik: so bug #1283859 seems to be fixed with the second alarm fix, right?
[13:31] <ubot2`> Launchpad bug 1283859 in Ubuntu Clock App "Updated recurring alarm values are not reflected in the indicator until phone reboot" [High,Confirmed] https://launchpad.net/bugs/1283859
[13:31] <zsombi> nik90:^^
[13:32] <nik90> zsombi: no it doesnt fix it
[13:32] <zsombi> nik90: ok, so the change is still visible when the phone is rebooted...
[13:33] <zsombi> nik90: then it's not on Alarm's side
[13:33] <nik90> zsombi: actually I didn't reboot the phone to check it. I will need to install again to check that.
[13:33] <nik90> zsombi: I rebooted to check if the timezone issue was good but failed to check the above thing :P
[13:33] <zsombi> nik90: strange... why on earth does it behave differently on the device?
[13:34] <nik90> zsombi: no idea..
[13:35] <zsombi> nik90: so the bug sais the time is correctly updated in the app, but the indicator shows wrong time...
[13:35] <nik90> zsombi: exactly
[13:36] <zsombi> nik90: and the alarm-date-fix doesn't fix that?
[13:36] <nik90> zsombi: it could very well be the indicator-datetime doesn't get the signal from EDS to update it.
[13:36] <nik90> zsombi: nope alarm-date-fix doesn't update the indicator-datetime. The updated times can only be seen in the clock app
[13:38] <zsombi> nik90: but when you create a new alarm with alarm-date-fix installed, the time in teh indicator is correct, right?
[13:39] <nik90> zsombi: yes..but that was always the case though. Even before the alarm-date-fix MP, the indicator showed the same time as the clock app except the timezone issue
[13:40] <zsombi> nik90: ok... ehh... seems I cannot close these MPs before renato and charles confirms that there's nothing from their side...
[13:41] <nik90> zsombi: alrite so I will contact charles about the timezone without restart issue and the indicator-datetime not being updated after editing an alarm.
[13:41] <zsombi> nik90: about this: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/alarm-date-fix/+merge/210181/comments/495436
[13:41] <zsombi> nik90: step 2. smells like the timezone is not updated for the ClockApp
[13:42] <nik90> zsombi: but then the clock time shown in the clock app is updated to the new timezone :)
[13:42] <nik90> zsombi: meaning the time the clock app gives to the alarm should also be updated
[13:43] <zsombi> nik90: that's weird!
[13:43] <zsombi> nik90: I guess the listed alarms are as well outdated then!
[13:43] <zsombi> nik90: because there' sno new fetch happening after you change the TZ
[13:43] <nik90> zsombi: yup
[13:44] <nik90> zsombi: I mentioned that the alarm time shown in the clock app is also not correct
[13:47] <zsombi> nik90: so you create an alarm @11am, and when it gets back to the list it shows 10am
[13:47] <nik90> zsombi: give me a minute, let me install your package and run again
[13:48] <zsombi> nik90: sorry to bother U with this...
[13:49] <nik90> zsombi: no its fine...after all I maintain the clock app :)
[13:49] <zsombi> nik90: if it is so, then it means that EDS (plugin or EDS itself) does not have the TZ updated.
[13:50] <zsombi> nik90: also, could you pls close Clock app and relaunch (no phone reboot) and see if the alarms are updated...
[13:50] <nik90> zsombi: sure
[13:51] <zsombi> nik90: also pls move all your comments to the bugs, so others can see them too
[13:51] <nik90> ok
[13:51] <zsombi> nik90: as it seems that's a global problem we are facing...
[13:55] <nik90> zsombi: what's your timezone name..I want to test something other than utc
[13:55] <nik90> nvr mind..I entered India :)
[13:56] <zsombi> nik90: UTC+2
[13:56] <zsombi> nik90: Helsinki, FI, whatever :D
[13:57] <nik90> okay here are the results
[13:57] <nik90> I changed the timezone from UTC+1 to UTC+5.5 (India)
[13:58] <nik90> when I created an alarm for 10:00 PM, the alarm list shows an alarm set for 03:30 AM!
[13:58] <nik90> while the next alarm shows the alarm at 09:00 AM
[13:58] <nik90> The indicator shows the alarm as 09:00 AM
[13:59] <nik90> Now, I am going to close and reopen the clock app
[13:59] <nik90> When I reopened the clock app, both the next alarm and the alarm list shows the alarm saved as 03:30 AM despite the indicator showing 09:00 AM
[14:00] <nik90> All this while, the clock app was showing the correct system time of UTC+5.5
[14:00] <nik90> zsombi ^^
[14:04] <zsombi> nik90: omg! that's a clusterf*k
[14:06] <nik90> zsombi: I am off to vUDS...but I agree...all that issues disappear when I reboot the phone
[14:06] <zsombi> nik90: log this to the bugs pls!!!
[14:07] <nik90> zsombi: I am going to test this for another 5 times to ensure I am not crazy here
[14:07] <zsombi> nik90: :D
[17:03] <kalikiana> nik90: if you wanna have a look, I produced a code mockup of the three concepts of sorting, transforming values and filtering https://code.launchpad.net/~kalikiana/u1db-qt/transformers/+merge/210457
[17:16] <nerochiaro> boiko: renato: artmello_ : how do you guys launch a click app from the shell on the device ?
[17:19] <boiko> nerochiaro: I did this once or twice, but can't remember right now, let me see
[17:20] <nerochiaro> boiko: could it be "upstart-app-launch desktop_file_name"
[17:21] <boiko> nerochiaro: I thought it was the click app id (i.e. com.ubuntu.calculator), but doesn't seem to work
[17:21] <boiko> sergiusens: ^
[17:21] <sergiusens> nerochiaro, boiko upstart-app-launch com.ubuntu.calculator_calculator_${version}
[17:22] <boiko> sergiusens: why the extra _calculator ?
[17:22] <sergiusens> boiko, package-name_application-name_version
[17:22] <boiko> sergiusens: ah ok, got it
[17:22] <sergiusens> boiko, a package can have multiple applications
[17:22] <nerochiaro> sergiusens: ok thanks, and what's the deal with Jenkins, does it build click packaged ?
[17:23] <nerochiaro> sergiusens: for testing
[17:23] <sergiusens> boiko, not supported yet; but image having com.ubuntu.communications_[dialer|contacts|messaging]_version
[17:24] <sergiusens> nerochiaro, it doesn't; fginther said it would be done by EOM
[17:24] <sergiusens> what are you building?
[17:24] <nerochiaro> sergiusens: gallery, it has been moved to click recently
[17:25] <sergiusens> nerochiaro, that
[17:25] <sergiusens> nerochiaro, that's the complicated one :-/
[17:25] <sergiusens> nerochiaro, all others can be built with click-buddy --arch armhf
[17:25] <sergiusens> nerochiaro, do you have access to jenkins?
[17:25] <nerochiaro> sergiusens: i can trigger rebuilds, if that's what you mean
[17:26] <sergiusens> nerochiaro, ok; so http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click-from-branch/3/ was built from https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-album-navigation/+merge/210178
[17:26] <sergiusens> if you check 'build' it should allow you to input a branch in there
[17:27] <sergiusens> rev 930 fwiw
[17:27] <nerochiaro> wait, where do i see the "build" ?
[17:29] <nerochiaro> sergiusens: ^
[17:29] <sergiusens> nerochiaro, http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click-from-branch/build?delay=0sec
[17:30] <sergiusens> nerochiaro, or the click that was built you mean?
[17:30] <sergiusens> that's http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click-from-branch/lastSuccessfulBuild/artifact/wrapped_click/com.ubuntu.gallery_2.9.1.930_armhf.click
[17:30] <sergiusens> nerochiaro, the last part of the version there is the version number
[17:31] <nerochiaro> sergiusens: ok, let me bookmark all that stuff
[17:31] <sergiusens> nerochiaro, ideally bookmark the click view http://s-jenkins.ubuntu-ci:8080/view/click/?
[17:32] <nerochiaro> sergiusens: ok
[17:33] <nerochiaro> sergiusens: so that gives me the click package that contains the app. what about the tests ? do they still go with the -autopilot.deb build normally by jenkins ?
[17:38] <aquarius> mardy, ping
[17:39] <aquarius> mardy, unping
[17:56] <elopio> nerochiaro: ping. Can you review this for me please?
[17:56] <elopio> https://code.launchpad.net/~elopio/notes-app/dont_click_header/+merge/210349
[17:56] <nik90> dpm: I will be going to the ubuntu component store session..but if there are people needed for the weather session, let me know
[17:57] <dpm> nik90, great, thanks. I think we're good, as m-b-o1 said he could make it to the weather one, but it'd be good to have some core app devs on the session after (core apps review) if you can make it
[17:58] <m-b-o1> dpm nik90: hey ho
[17:59] <nik90> m-b-o1: hi
[18:01] <dpm> m-b-o1, I'm having some difficulties with the hangout, I'll send you the link in a minute
[18:01] <m-b-o1> dpm ok
[18:03] <BobJonkman1> Hi: Will there be an Ubuntu SDKDays event this year? https://wiki.ubuntu.com/UbuntuSDKDays
[18:10] <RogerC> HI Mr B
[19:04] <nik90> ahayzen: join the core apps session?
[19:04] <nik90> iBelieve:  ^^
[19:04] <nik90> appdev1 room
[19:04] <lei_> question: is there be compiz in touch
[19:05] <iBelieve> nik90: thanks, I'll be there in IRC
[19:05] <nik90> iBelieve: awesome
[19:06] <aheras> py
[19:07] <rpadovani> mzanetti, little patch: https://code.launchpad.net/~rpadovani/reminders-app/1289342/+merge/210471
[19:12] <lei_> ubuntu is for bitches
[20:13] <ahayzen> nik90, sorry was out of the flat, i'll watch it later :)
[21:04] <rpadovani> hey popey, are you on trusty?
[21:05] <rpadovani> Because icon 'add' should be on trusty, see bug 1289347
[21:05] <ubot2`> Launchpad bug 1289347 in Ubuntu Reminders app "[desktop] No icon available for "Add notebook", "Add note" and "Add reminder"" [Medium,Confirmed] https://launchpad.net/bugs/1289347
[21:50] <candelibas> Will getUserMedia API support on Ubuntu HTML5 apps?
[21:51] <aquarius> candelibas, I would hope so, yes; if it doesn't, it's a bug. (If it doesn't, you can fall back on the cordova implementation, but kyleN was clear that supporting the w3c standard way to do things is preferred)
[21:52] <aquarius> alex-abreu, ping about u1 and html5 :)
[21:55] <candelibas> Thanks aquarius
[21:58] <aquarius> actually, daker, ping abotut u1 and html5
[21:59] <daker> yo
[21:59] <daker> aquarius: they recommend using Cordova API
[21:59] <daker> AFAIK
[21:59] <aquarius> daker, yo. Were you in the html5 discussion earlier where we talked about building a core app with html5?
[22:00] <aquarius> and I volunteered to put together a U1 files app?
[22:00] <aquarius> or was that just alex-abreu and dbarth?
[22:00] <daker> aquarius: i am rewatching it again now
[22:00] <aquarius> daker, lp:~sil/+junk/U1FilesHTML5 if you want to have a play, anyway :)
[22:01] <daker> they should remove the "dc" command...
[22:01] <aquarius> the pagestack doesn't pop and I don't know why, and you can't download any files because we don't have the download API or the new content hub yet, but the basics are done :)
[22:01] <aquarius> note: won't work on your desktop, unless you have a U1 account in UOA, which nobody does
[22:01] <aquarius> but you do on the phone :)
[22:03] <daker> aquarius: i don't have U1 in the list of UOA list
[22:04] <aquarius> even on the phone?
[22:04] <aquarius> I don't think it's supported to put U1 in UOA on the desktop yet :(
[22:04] <aquarius> it is on the phone because the click store needs it
[22:04] <daker> aquarius: no phone for me now
[22:05] <aquarius> :(
[22:05] <aquarius> can't test it, then, I'm afraid
[22:05] <aquarius> I shall wave it at dbarth when he's back online.
[22:11] <daker> :(
[22:12] <aquarius> well, you can get yourself a u1 token and then hardcode it into the code locally if you want :P
[22:13] <aquarius> grab it out of seahorse and then hardcode it into the result.length==0 check in th webapps-api-ready handler in app.js
[22:40] <daker> ok