[04:05] <akiva-thinkpad> hi all
[07:08] <dholbach> good morning
[08:05] <dholbach> dpm, thanks for following up on the help-app bug
[08:05] <dholbach> I passed it on to IS
[08:05] <dholbach> and thanks for escalating the issue
[08:06] <dpm> dholbach, no worries :)
[08:06] <dpm> thanks for following it through to publication!
[08:06] <dholbach> :)
[08:45] <dpm> dholbach, davidcalle, while reviewing, I did some minor changes on https://developer.ubuntu.com/en/snappy/guides/webdm/ too
[08:45] <dpm> I've been moving the important notes I've seen in places, so that they are in visible boxes
[08:46] <dpm> I'll stop reviewing now, will talk to you in a few mins in the call
[08:46] <dholbach> thanks a lot dpm
[08:46] <dholbach> webdm might not be part of the release on thursday
[08:46] <dholbach> so we could probably deemphasise it somewhat
[08:47] <dholbach> or maybe let's move to #snappy
[08:47] <dpm> ah, good point
[08:47] <dpm> davidcalle, can you join us on #snappy too?
[08:55] <uglyandstupid> hey hey
[08:56] <uglyandstupid> Anyone know if it's already planned to handle dynamic language change for the translated text please ?
[09:47] <nerochiaro> oSoMoN: if google is our default search engine, shouldn't we ship at least an opensearch xml file for it ?
[09:48] <oSoMoN> nerochiaro, we should, although atm custom search engine definitions are searched only in ~/.local/share/webbrowser-app/searchengines/, and we can’t install files there
[09:49] <oSoMoN> nerochiaro, we’ll need a way to install definitions system-wide, and have the code that handles that search for definitions in both places
[09:49] <oSoMoN> nerochiaro, in the meantime, default values for google are hardcoded in config.h.in
[09:49] <nerochiaro> oSoMoN: apps usually provide their default files in /usr/share/ and then allow overriding or adding more via .local/share or something like that
[09:50] <nerochiaro> oSoMoN: we should probably do that for the opensearch files
[09:50] <oSoMoN> yeah, that’s what we should be doing (and what we will be doing, when we get to it)
[09:50] <nerochiaro> oSoMoN: so not part of what i should be doing now ?
[09:50] <oSoMoN> nerochiaro, I don’t think so, that’s out of scope
[09:50] <nerochiaro> oSoMoN: ok
[10:53] <kalikiana> t1mp: review? https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/textDocument/+merge/252798
[11:22] <mhall119> kalikiana: please register for http://summit.ubuntu.com/uos-1505/ so I can promote you to a track lead
[11:40] <kalikiana> aha so now registration is open
[11:40] <kalikiana> will do
[11:41] <kalikiana> mhall119: done
[11:45] <mhall119> thanks kalikiana
[13:13] <SPEck> Hy all
[13:13] <SPEck> CAn combody help me to fix my computer to write app for Ubuntu Touch
[13:33] <Mirv> dpm: is there a sort of guide of what you were doing with dekko? ie entering click chroot, building something into .click in there? I'd be interested.
[13:34] <Mirv> basically lower level usage of SDK but for apps that are not strictly created with the SDK
[13:35] <dpm> Mirv, it should use the standard SDK procedures, at least that's what I did. So here's how it worked (links to documentation to follow)
[13:35] <dpm> 1. Had the SDK already set up with a 15.04 armhf click chroot
[13:36] <dpm> 2. Checked out dekko -> http://pastebin.ubuntu.com/10861446/
[13:36] <Mirv> 1. check, done via SDK :)
[13:36] <dpm> 3. Opened its top CMakeLists.txt file
[13:36] <dpm> 4. When prompted for a kit on Qt Creator, I chose the one I've got assigned to that click chroot in 1. (I've called my kit "Phone")
[13:37] <dpm> 5. Ensure your click chroot has got this dependencies installed:
[13:37] <dpm> - libqt5webkit5
[13:37] <dpm> - qttools5-dev-tools (that's the one we needed to have installed in the host arch )
[13:38] <Mirv> oh, 3. I didn't realize, too obvious
[13:39] <dpm> 6. Then under the Project tab, set this as the build options:  -DUBUNTU_CLICK_MODE=on -DCMAKE_INSTALL_PREFIX=/
[13:40] <dpm> Mirv, actually, I've told you the wrong order, 5. (install chroot deps) should go before 3.
[13:40] <dpm> as otherwise cmake configuration will fail
[13:41] <Mirv> dpm: for my test I seemingly don't need it, but yes I found "Maintain" now. is it that if you install deps there they "stay" in that kit?
[13:41] <dpm> Mirv, exactly
[13:42] <DanChapman> dpm, i've made it alot simpler now http://paste.ubuntu.com/10861469/ :-D
[13:42] <Mirv> dpm: this is so cool. even though this would fail miserably at the end, I had QtC do something with the project I'm testing on.
[13:43] <dpm> Mirv, also if your project's cmake config fails, you don't need to reload the project every time. On the project explorer, you can right-click on the top item in the tree (generally the project name) and choose the option "Run cmake". That'll re-run cmake, as the name says ;)
[13:43] <Mirv> dpm: that 6. sounds like magical ingredient that would be valuable to be somewhere visible, and it probably is too already somwhere?
[13:43] <dpm> Mirv, unfortunately, that's the only place you can do that, I agree that it's a bit hidden
[13:44] <dpm> DanChapman, wohoo! :-)
[13:44] <Mirv> dpm: I mean somewhere in docs, but I agree it'd be cool to have "clickify cmake" button or such
[13:45] <dpm> Mirv, ah, it's in the docs: https://developer.ubuntu.com/en/apps/sdk/tutorials/building-cross-architecture-click-applications/
[13:47] <Mirv> dpm: I don't see UBUNTU_CLICK_MODE or CMAKE_INSTALL_PREFIX guided in there? or is either of them dekko specific?
[13:48] <dpm> Mirv, yes, it's dekko-specific, but DanChapman was talking about adding this to the cmake file, so that you don't have to specify it every time you check dekko out
[13:50] <Mirv> dpm: ah, ok. but you'd probably need the install prefix anyway if you had some other non-Ubuntuphone CMake project you'd want to try to "port"?
[13:51] <DanChapman> Mirv, one thing i will note. And i've never seen documentatin for is the magin UBUNTU_PROJECT_TYPE and UBUNTU_MANIFEST_PATH cmake variables. You can't build clicks or run on device without them
[13:51] <dpm> Mirv, the idea is that you put it on the cmake file so that it's predefined, but you can always override it if you specify it as -D on the build
[13:51] <DanChapman> s/magin/magic
[13:54] <Mirv> DanChapman: I see, thanks a lot! dekko seems to be a good source of info :)
[13:55] <dpm> Mirv, other apps that you can try for your tests are lp:reminders-app and lp:ubuntu-clock-app, they've also got good cmake setups that can be used as examples
[13:55] <Mirv> I started https://wiki.ubuntu.com/Touch/Apps/Porting for my notes
[13:58] <Mirv> I would have started looking at this earlier but click chroots are simply not working on my vivid machine, so I'm now using 14.04 virtual machine
[15:43] <_honning_> Hi all, i am developing an app for Ubuntu Phone. But I am having trouble preventing the screen from dimming/locking while doing a simple animation on html5.
[15:44] <_honning_> i was wondering if anybody has been able to turn off  the screen dimming/lock on a html5 app or in a qml app?
[15:44] <nik90> _honning_: curious but how long does the animation run for? since the screen starts dimming only after a minute I guess
[15:44] <nik90> _honning_: apps (qml and html5) dont have permission to prevent screen dimming (yet) unless they are playing a video
[15:45] <ogra_> and there is no way to stop the dimming from an app
[15:45] <_honning_> yes, it runs for 8 minutes
[15:45] <_honning_> so the screen lock turns on after 1 minute if i dont touch the screen
[15:45] <_honning_> nike98: ok, thanks for the information
[15:46] <_honning_> i was hoping something like in android: getWindow().addFlags(WindowManager.LayoutParams.FLAG_KEEP_SCREEN_ON);
[15:46] <_honning_> existed but i havent found it....
[15:46] <ogra_> no, it doesnt
[15:46] <_honning_> could i run a video with just the background color as a hack?
[15:47] <nik90> _honning_: right now the ubuntu touch platform rules are more strict than android and as such doesn't allow apps to keep screen on or keep polling in the background
[15:47] <ogra_> you would have to embed it and hook it up to the media-hub ...
[15:47]  * ogra_ has never used HTML5 for apps ... not sure the integration goes that deep actually
[15:49] <_honning_> nik90 and ogra: ok, thanks very much for the information, i will try to see what i can get working
[15:49] <nik90> _honning_: yw
[15:49] <mcphail> nik90: just looking at your post about UCS. I like the idea. Have you made progress? Could this be managed as a simple git repo?
[15:52] <nik90> mcphail: hi..we (myself and stuart) are intending ucs to be more like npm, pip etc where installing something is as easy "ucs install component-name"
[15:52] <nik90> mcphail: just a few days back, stuart added the community channel where *anyone* can upload their component to the store without any sort of review process and maintain it themselves.
[15:55] <mcphail> nik90: you have a working prototype?
[15:55] <nik90> mcphail: yeah for quite a while now. You can find the necessary information at http://ubuntu-component-store.readthedocs.org/
[15:56] <mcphail> nik90: excellent. I'll check it out
[15:56] <nik90> mcphail: you will need to first install ucs in your system and then you can help test uploading a component to the store
[15:56] <nik90> mcphail: let us know how it goes and if anything seems confusing, we can improve those parts.
[15:58] <mcphail> nik90: will do. Thanks!
[16:06]  * nik90 watches the community q&a
[16:21] <mcphail> nik90: do you have coding style guidelines for the UCS (tabs v spaces, camelCase or underscores etc)?
[16:22] <nik90> mcphail: for curated components or community components?
[16:23] <mcphail> nik90: either. Presumably community components should aspire to curated status?
[16:23] <nik90> mcphail: curated components should preferably stick to a common coding style guidelines but I haven't come to decide on that yet. We were first concentrating on getting the infrastructure up and ready.
[16:23] <mcphail> nik90: so the "reformat qml" option in the SDK would be acceptable?
[16:24] <nik90> mcphail: yes that is fine
[16:24]  * mcphail hates camelCase
[16:26] <nik90> mcphail: basically components in the curated store are intended to be candidates for inclusion in the ubuntu-sdk itself..that's our goal..and the ucs curated store sort of is a temporary holding place to show the SDK devs that this is a good component which is liked by the community.
[16:27] <nik90> mcphail: so some components that are just meant to make life easier like a blurred background header which doesnt make sense to be in the SDK is better of in the community store imo.
[16:27] <nik90> mcphail: but yet components in both the curated and community store should strive to provide a good experience to app devs by providing api documentation, tests etc
[17:42] <om26er> t1mp, Hi!
[17:43] <om26er> t1mp, have the header changed recently ?
[18:01] <t1mp> om26er: yes
[18:01] <t1mp> om26er: a lot of changes. What are you interested in?
[18:02] <om26er> t1mp, ah, good. I love them :)
[18:02] <om26er> t1mp, I was a testing a silo, just wanted to make sure it was not regressing something
[18:02] <t1mp> om26er: ah, you are talking about the updated visuals? Yes those changes landed today.
[18:02] <t1mp> om26er: there will be more :)
[18:03] <om26er> t1mp, do you have designs for the improvements somewhere ? or is that tracked in bug reports ?
[18:05] <t1mp> om26er: https://docs.google.com/a/canonical.com/presentation/d/1wZ09SVZPwwJOccG4Rqu5JaHDuWw051oSKjf0uJHUyO8/edit#slide=id.g8d903971d_010
[18:50] <nik90> t1mp: are those new header visuals part of 1.2?
[18:50]  * nik90 hopes they are ... pls pls pls
[19:32] <SturmFlut> Does anybody use the SDK on an Ubuntu 15.04 desktop? It seems quite broken for me, from incorrect font sizes to crashing tools.
[19:44] <nik90> SturmFlut: I have a development 15.04 laptop that seems to be fine with the latest updates.
[19:44] <nik90> SturmFlut: when did these issues start for you?
[19:47] <SturmFlut> nik90: They started immediately after upgrading to 15.04 a couple of days ago. When starting the SDK I always immediately get a crash report from the click tool. The main UI is fine, but all the Qt file dialogs have way too large fonts. I just created a new "QML with C++ plugin" project and qmlpluginscan crashes on every run.
[19:48] <nik90> SturmFlut: I have noticed the crash report from the click tool, but tbh I occasionally do get that on my main 14.04 machine as well
[19:48] <SturmFlut> nik90: I already tried deleting all the configuration files, to no avail.
[19:48]  * nik90 checks the Qt file dialogs
[19:49] <nik90> hmm it looks normal to me
[19:50] <SturmFlut> nik90: http://i.imgur.com/OZdID0j.png
[19:51] <nik90> oh..that's bad
[19:55] <SturmFlut> nik90: Haha, it's not just the Qt file dialogs, but also some buttons and popups
[19:55] <SturmFlut> At one point a popup fills nearly all of my FullHD screen
[19:56] <nik90> SturmFlut: may be somehow during the upgrade the Qt theme display ratio broke?
[19:57] <SturmFlut> nik90: Yes, something like that. But it looks like all other Qt applications, e.g. qbittorrent, are not affected. Just Qt Creator.
[20:11] <SturmFlut> Argh, not again
[20:11] <SturmFlut> sturmflut@fire:~$ mount | grep schroot | wc -l
[20:11] <SturmFlut> 56
[20:19] <rickspencer3> does anyone else accidentally close the whole emulator sometimes when they are developing?
[20:20] <nik90> rickspencer3: yeah I have done that a couple of times...nowadays I develop using the phone instead
[20:20] <rickspencer3> I guess you never accidentally throw away your phone :)
[20:21] <nik90> hehe no..although I do get distracted and start playing with other apps during my testing :P
[20:37] <mcphail> I've created a type "AutoRangePicker.qml" as per http://paste.ubuntu.com/10863152/ . When I add it to a Row it clamps to the left rather than being laid out correctly. What am I doing wrong?
[20:39] <rickspencer3> does anyone have a good icon for "rename"?
[20:49] <nik90> mcphail: the picker clamps to the left? or the parent item?
[20:50] <mcphail> nik90: actually not sure, tbh. I have a row with Picker, Picker, Picker then AutoRangePicker and it overlays the first Picker...
[20:51] <nik90> mcphail: change item to rectangle with color "lightgreen" or something to see what's happening
[20:51] <nik90> and try anchoring the picker to the bounds of its parent..anchors.fill: parent
[20:57] <mcphail> nik90: context (for what it's worth: only experimenting) at http://paste.ubuntu.com/10863320/ . Adding anchors.fill: parent only breaks the row and gets the console grumbling...
[21:29] <mcphail> nik90: hmm - if I add "width: picker.width height: picker.height" it works. Oh well
[21:30] <nik90> mcphail: hmm yes..otherwise items has 0 width and height..which is why they were overlapping one other
[21:30] <nik90> mcphail: tht's why I usually test with rectangle first before switching to item
[21:31] <mcphail> nik90: yes, that helped. Thanks!
[21:32] <nik90> yw
[23:13] <aquarius> I'm trying to build an app (Beru, as it happens) for the emulator, in Ubuntu SDK. The build fails with error "error: poppler/qt5/poppler-qt5.h: No such file or directory". I assumed this meant that the appropriate library wasn't in the chroot that the build uses, but I've "Manage"d that chroot and apt-get install'ed the package and it still isn't working. What else might I need to do?
[23:15] <aquarius> In particular, /usr/include/poppler/qt5/poppler-qt5.h exists in the chroot.
[23:15] <aquarius> I think I'm changing the correct chroot, but how might I find out if I'm wrong?
[23:17] <aquarius> (note: in Ubuntu SDK, under Build Environment, PATH is set to /var/lib/schroot/chroots/click-ubuntu-sdk-14.10-i386... and /var/lib/schroot/chroots/click-ubuntu-sdk-14.10-i386/usr/include/poppler/qt5/poppler-qt5.h exists, so I'm pretty sure that's right.
[23:18] <nik90> aquarius: hey, do you want to host a session in UOS May 5th-7th about UCS with regards to the new curated and community channels?
[23:19] <aquarius> nik90, I should really, shouldn't I? Sure, why not, let me go and propose a session.
[23:19] <aquarius> however, in return you have to help me with my Dummies Guide To CMake question above :)
[23:20] <nik90> aquarius: lol
[23:22] <nik90> aquarius: considering that you have installed poppler-qt5 in the chroot, I am failing to see why it is failing to build.
[23:22] <aquarius> nik90, me too
[23:22] <aquarius> I mean, I'm not brilliant at this stuff, but that really feels like it ought to work :)
[23:23] <nik90> aquarius: I have a hunch..
[23:23] <popey> you building an armhf binary?
[23:23] <popey> in an armhf chroot? aquarius ^?
[23:23] <nik90> above the green play button, where you choose the kit stuff, see if there is another configuration you can run
[23:24] <nik90> also try what popey said..may be poppler-qt5 build error has to do with i386 and requires additional packages
[23:24] <popey> http://paste.ubuntu.com/10863817/
[23:24] <popey> thats what I have in my chroot
[23:25] <popey> note libpoppler-qt5-1:armhf
[23:25] <nik90> hmm true
[23:25] <nik90> aquarius: ^^
[23:25] <aquarius> popey, ah, this is an i386 chroot, or for the emulator
[23:26] <aquarius> nik90, http://summit.ubuntu.com/uos-1505/meeting/22439/ubuntu-component-store/ -- it hasn't shown up in the schedule yet, presumably because it needs to be approved
[23:26] <popey> you're building an i386 binary in an i386 chroot for the i386 emulator, right?
[23:26] <nik90> aquarius: yup, time to test if I am the UOS app lead
[23:26] <popey> aquarius: approved
[23:26] <popey> oops
[23:26] <aquarius> popey, I certainly *believe* that that's what I'm doing :)
[23:27] <popey> qtdeclarative5-poppler1.0:i386
[23:27] <popey> do you have that?
[23:27] <aquarius> ah, wait, hang on
[23:27] <aquarius> do I have to install :i386 versions of the packages?
[23:27] <popey> not if it's an i386 chroot
[23:27] <aquarius> I'm in an i386 chroot! does it not know that?
[23:27] <popey> it will do that by default
[23:27] <aquarius> oh, good, OK :)
[23:27] <popey> ignore that bit
[23:27] <popey> just install qtdeclarative5-poppler1.0
[23:28] <aquarius> I have
[23:28] <aquarius> but...
[23:28] <popey> (mine is a 14.10 chroot, you may have a newer poppler)
[23:28] <nik90> aquarius: I see your session. You got any date and time preference?
[23:29] <aquarius> nik90, not tuesday evening UK time
[23:29] <aquarius> other than that, rock and roll.
[23:29] <aquarius> popey, yep, got that
[23:29] <nik90> aquarius: at the moment no session has been scheduled..so all slots free :)
[23:29] <popey> aquarius: lemme try, what we building?
[23:29] <aquarius> http://pastebin.ubuntu.com/10863833/
[23:29] <aquarius> popey, beru
[23:30] <popey> link?
[23:30] <aquarius> popey, I checked it out of github (https://github.com/rschroll/beru), opened it in Ubuntu SDK (by choosing its cmakefile.txt), chose my emulator build target (which I know works), and... got this error.
[23:30] <popey> lemme try
[23:31] <popey> what version chroot?
[23:31] <aquarius> annoyingly I can't build it for the desktop because it now depends on a newer version of the SDK than 14.04 has :(
[23:31] <aquarius> otherwise I wouldn't bother with all this emulator fannying about :)
[23:31] <nik90> aquarius: I scheduled it for wednesday 18:00 UTC
[23:32] <aquarius> nice one nik90
[23:32] <aquarius> I have added the ical for UOS to my calendar, so I shouldn't miss anything
[23:32] <nik90> popey: btw I doubt we need a dedicated clock app session. No idea what to present/talk about there
[23:32] <aquarius> I assume google calendar re-polls it every now and again :)
[23:33] <nik90> aquarius: it should
[23:33] <popey> well, i added one for each core app
[23:33] <nik90> aquarius: either way when I host it, I will bug you to join it :P
[23:33]  * aquarius laughs
[23:34] <aquarius> nik90, feel free to edit the session description if you think it should be different
[23:36]  * nik90 is annoyed that people keep rating clock 1-2 star after complaining about missing timer/stopwatch
[23:36] <nik90> aquarius: sure..will go through it with a fresh mind tomorrow
[23:40] <popey> hmm
[23:41] <popey> aquarius: fails same way here
[23:43] <popey> ok, docviewer fails in the same way in the same chroot
[23:54] <popey> aquarius: ooh
[23:58] <popey> bah