[03:30] <msquarme> Hello
[07:46] <ybon> we need to set 1.1 as apparmor policy version from now on, is that right?
[08:31] <dholbach> good morning
[08:53] <justCarakas> goodmornign to you 2
[09:36] <netcurli> Mirv: hey. I have a question about an upstream QT bug. Are there plans to backport the fix for https://bugreports.qt-project.org/browse/QTBUG-36874
[09:38] <JamesTait> Good morning all; happy Biodiesel Day! :-D
[09:40] <Mirv> netcurli: no-one has suggested that at least so far. LP bug against qtdeclarative-opensource-src would be useful to keep it on radar if it's important
[09:41] <netcurli> ok
[09:59] <netcurli> Mirv: bug ä1294019
[09:59] <netcurli> #1294019
[10:01] <Mirv> netcurli: thanks!
[10:27] <dpm> zbenjamin, I've just started testing your new cmake plugin, very nice to just open a project and have cmake run automatically :)
[10:27] <zbenjamin> dpm: yeah, thats how it should be imho ;)
[10:28] <dpm> indeed :)
[10:28] <nik90> zbenjamin, dpm: Is this for all projects (including JS+QML) as discussed in the vUDS?
[10:29] <dpm> zbenjamin, I'm testing this with the Reminders app. So the next feature to test is cross-compilation. I guess I do this via the Build > build in chroot menu entry?
[10:29] <zbenjamin> nik90: no, this are the changes that i needed so i can build what we talked about in the UDS
[10:29] <dpm> nik90, afaik, this is for cmake projects only
[10:29] <nik90> zbenjamin: ok
[10:30] <zbenjamin> dpm: yes, but the build in chroot entry makes some assumptions that the buildfiles will create the same structure as our template does. I hope i can make that more generic in the future, so prepare for failure ;)
[10:30] <dpm> yeah, just got the failure :)
[10:31] <zbenjamin> dpm: most likely it will bitch about the desktop file maybe
[10:31] <dpm> zbenjamin, what are those assumptions, on a high level?
[10:31] <dpm> let me paste the output
[10:31] <dpm> it'd be good to get Reminders to conform to those, so that it can be built with Qt Creator
[10:32] <zbenjamin> dpm: the desktop file currently has to be in the root directory of the click package
[10:32] <dpm> zbenjamin, it seems it failed even before that: http://pastebin.ubuntu.com/7113324/
[10:33] <dpm> that's the output of after opening Reminders (thus getting cmake run) and then choosing Build > build in chrooot
[10:33] <dpm> actually, let me upgrade the system before I continue
[10:34] <dpm> there seems to be an SDK update in the PPA I need to install
[10:36] <zbenjamin> dpm: that looks like a error in your CMakeLists.txt
[10:36] <zbenjamin> dpm: CMake Error at CMakeLists.txt:32 (STRING):
[10:36] <zbenjamin>   string sub-command REPLACE requires at least four arguments.
[10:37] <zbenjamin> ah it cannot query qmake
[10:37] <zbenjamin> dpm: you have to hardcode that, there is no qmake in the chroots
[10:37] <zbenjamin> atm
[10:37] <sergiusens> dpm, don't use qmake to figure out a module path for the clicks; make them go in the upstart read import path
[10:38] <zbenjamin> dpm: currently we do that in the templates http://pastebin.com/6ggeVhdP
[10:38] <sergiusens> lib/$arch_triplet/[module]
[10:39] <zbenjamin> sergiusens: since when is that there? can i just replace that in our templates and it will work always?
[10:40] <sergiusens> zbenjamin, since ted added it about 2+ months ago for fat packages (was announced on the app dev mail list)
[10:40] <dpm> zbenjamin, sergiusens, ah, sorry, I was trying with an older version of Reminders. The actual output with the latest SDK and latest lp:reminders-app is http://pastebin.ubuntu.com/7113359/
[10:40] <sergiusens> zbenjamin, I'm already using that fwiw in the clicks today
[10:40] <sergiusens> zbenjamin, same as lib/$arch_triplet/bin for the bin path
[10:40] <zbenjamin> dpm: yeah the build deps need to be installed manually
[10:40] <sergiusens> dpm, yeah, reminders is using the paths I just mentioned
[10:42] <dpm> zbenjamin, how do you mean installed manually? If you mean in the system, I've got them installed already. Reminders builds fine with plain cmake, but it seems there might be an issue with the paths to those dependencies when building with Qt Creator. Do I need to specify them differently?
[10:43] <zbenjamin> dpm:  in the click chroot, open the qtcreator options and click on the maintain button
[10:43] <zbenjamin> there you can install the packages
[10:43] <sergiusens> this is the hack I have until session support shows up...  click-buddy --arch armhf --extra-deps "libboost-dev:armhf libssl-dev:armhf" --maint-mode
[10:44] <zbenjamin> dpm: remember you are building inside a chroot, no deps that are available on your host are also available in the chroot
[10:44] <sergiusens> those are the extra deps for reminders
[10:44] <dpm> zbenjamin, ah, I see. But what do you mean exactly by "in the click chroot, open the qtcreator options". Is there a menu item to install those deps?
[10:45] <zbenjamin> dpm: no , you need to do apt-get install.   In Qtcreator click Tool->Options->Ubuntu->Click there you should see a list of all your click targets
[10:46] <zbenjamin> dpm: press the maintain button and install libboost-dev:armhf libssl-dev:armhf
[10:46] <zbenjamin> sergiusens: maybe we need something like build-dependencies for click
[10:46] <dpm> sergiusens, thanks
[10:47] <dpm> zbenjamin, ah, that's clear now, thanks
[10:47] <sergiusens> zbenjamin, it's a bit complicated; since the theory says that you are only supposed to use the deps provided by the click chroot
[10:48] <sergiusens> all other deps are casually working
[10:48] <sergiusens> only two projects that require extra deps are reminders and the gallery from what I've seen
[10:49] <zbenjamin> sergiusens: yeah i know ;)
[10:53] <zbenjamin> dpm: anyhow i'm planning to be more generic in the future, so i will use the manifest file to lookup the desktop file for example. Chances are good that this will fix lots of problems
[10:54] <dpm> zbenjamin, good to know, thanks. I've updated the chroot and now I'm manually installing the dependencies. Next step, try the build again :)
[10:57] <dpm> zbenjamin, sergiusens it seems the chroot build failed again, with a couple of errors. I'm not sure which one is the one causing it to stop, but looks like the one on line 26? http://pastebin.ubuntu.com/7113421/
[10:58] <zbenjamin> dpm: now you hit the current bug in click
[10:58] <zbenjamin> dpm: we are working on a fix for that, but until then you have to remove the directory named after your click target in the builddir
[10:59] <kalikiana> nik90: ping6 (about sorting query)
[10:59] <zbenjamin> dpm: actually not
[10:59] <zbenjamin> dpm: sorry that another problem .... i would suggest to wait for the next plugin update, it should be there soon
[11:00] <sergiusens> dpm, I can't really comment on that issue; but it seems zbenjamin has it covered
[11:01] <zbenjamin> otherwise you have to edit the file /usr/share/qtcreator/ubuntu/scripts/qtc_chroot_cmake to make it look like this: http://pastebin.ubuntu.com/7112658/
[11:01] <dpm> zbenjamin, no worries, thanks for your help. So will that also take care of the 'Failed to find "GLESv2" in "" with CMAKE_CXX_LIBRARY_ARCHITECTURE' error, or is this just a warning that can be ignored?
[11:01] <zbenjamin> dpm: that is the problem actually :)
[11:01] <dpm> aha :)
[11:02] <zbenjamin> dpm: look at my paste, that will make it build for you automatically
[11:02] <zbenjamin> dpm: temporary hack until the problems with cmake in the new click chroot version are sorted out
[11:04] <bzoltan1> dpm: zbenjamin: the fix is on its way ... we need a click fix and a hack around in the cmake command.
[11:05] <dpm> zbenjamin, yep, that seems to work, it's building now. Another quick question: I'm not sure if I'm remembering correctly, but I thought Qt Creator's menus worked with the global menu, but now they seem to appear outside of the global menu. Is this a known bug, or is it me just talking rubbish and there was never support for the global menu anyway?
[11:05] <bzoltan1> dpm: both are ready... I am doing the final testing and then will find a sponsor to land them
[11:05] <bzoltan1> dpm:  there is support for global menu, you are missing a package ... gimme a sec to look it up
[11:07] <dpm> ok, thanks.
[11:07] <dpm> yes, it seemed to go away a couple of upgrades ago
[11:57] <dpm> bzoltan1, any news on that package for global menu?
[11:58] <bzoltan1> dpm: ohh... I was dragged off by on ther problem... give me a sec more please
[11:58] <dpm> bzoltan1, no worries, it's nothing urgent or anything
[12:01] <bzoltan1> dpm: it should be the appmenu-qt5
[12:02] <dpm> bzoltan1, it seems I've got it installed already, but Qt Creator's menus don't appear in the global menu
[12:02] <nik90> dpm: I had the issue of the global menu not working when I upgraded to Qt 5.2. However after restarting it came back :) .. That said, I don't think you need the SDK PPA for 14.04
[12:02] <dpm> nik90, I've been bitten by that "you don't need the SDK PPA on 14.04" before :)
[12:02] <bzoltan1> nik90: I have removed that PPA from my environment last week
[12:03] <nik90> bzoltan1: yup me too
[12:03] <nik90> dpm: lol I can relate to that
[12:03] <bzoltan1> dpm:  the PPA has little use as Trusty has all the new stuff
[12:03] <dpm> :-)
[12:03] <nik90> dpm: but I figured for the Qt 5.2, I should have no PPAs for the SDK and the core apps
[12:03] <nik90> bzoltan1: do we need the phablet-teams PPA for 14.04?
[12:04] <dpm> sergiusens might be able to better answer that question on the phablet-team's PPA ^
[12:04] <bzoltan1> nik90:  I have absolutely no PPA configured
[12:05] <dpm> nik90, bzoltan1, ok, then I'll bite the bullet and I'll remove the SDK PPA, I'll blame you guys if something breaks :P
[12:05] <dpm> even if it's unrelated to the SDK :)
[12:05]  * nik90 runs away :P
[12:05]  * bzoltan1 hides behind zbenjamin
[12:05] <nik90> lol
[12:06] <nik90> dpm: btw I assume you had something like http://i.imgur.com/isuL3Zq.png
[12:06] <bzoltan1> zbenjamin is the kingfu artist in our team :D
[12:06]  * zbenjamin runs in circles
[12:06] <zbenjamin> ;)
[12:06] <zbenjamin> lol
[12:06] <dpm> nik90, exactly
[12:07] <nik90> dpm: yup that was me 4 days ago. the restart fixed it.
[12:07] <dpm> nik90, restart of the system or of Qt Creator?
[12:07] <nik90> dpm: system
[12:07] <nik90> dpm: actually cannot exactly remember...since it was late night past 12
[12:08] <dpm> no worries, purging the SDK PPA atm
[12:10] <bzoltan1> dpm: remember to run apt-get install -f after the ppa-purge
[12:12] <dpm> bzoltan1, without arguments? It doesn't seem to do anything
[12:12] <bzoltan1> dpm: then you are fine
[12:13] <dpm> ok, thanks
[12:15] <dpm> bzoltan1, the compact widgets, the new header and the bottom edge... is that all still scheduled to land before 14.04?
[12:15] <bzoltan1> dpm: yes
[12:15] <jdstrand> ybon: re 1.1> when specifying a ubuntu-sdk-14.04* framework, yes.
[12:16] <dpm> bzoltan1, cool. What advice should be give to core app developers in terms of using all that new stuff? Should we start porting the core apps to use them? Any caveats to be aware of?
[12:16] <jdstrand> tools can start to use the new aa-clickquery/click-apparmor API though
[12:16] <jdstrand> speaking of which...
[12:16] <jdstrand> bzoltan1: fyi re bug #1293586
[12:16] <ubot2> Launchpad bug 1293586 in qtcreator-plugin-ubuntu (Ubuntu) "qtcreator should use the click-apparmor query API to obtain the policy version" [Undecided,New] https://launchpad.net/bugs/1293586
[12:17] <jdstrand> bzoltan1: (in case you didn't see it already)
[12:19] <bzoltan1> jdstrand: it is on my plate right now ... we wait for click 0.4.19 to land, then we land a new QtC supporting 14.04 framework and fixed cmake build
[12:19] <jdstrand> ok cool
[12:20] <bzoltan1> jdstrand: then we will fix the freamework support ... we have a branch for it already
[12:20] <jdstrand> nice
[12:20] <bzoltan1> jdstrand: kind of spidernet dependency stuff :)
[12:20] <jdstrand> yes, indeed. I felt that on friday myself :)
[12:23] <kalikiana> nik90: ping6 (wanna have a look at https://docs.google.com/a/canonical.com/document/d/1B0yHmPr5yOHri3zZLtRba7eYhTR_K374zZAdED7xgy8/edit)
[12:24] <nik90> kalikiana: what's it about? the u1db filter code mockups?
[12:24] <nik90> kalikiana: also I need permissions to view it. Will send request
[12:25] <kalikiana> nik90: this is a design doc for sorting which would be generic qml but cover u1db.query hence I'd like your feedback
[12:25] <kalikiana> ah sorry, I'll grant you
[12:27] <kalikiana> nik90: try now
[12:27] <nik90> kalikiana: that works
[12:28] <kalikiana> cool
[12:28] <nik90> kalikiana: will review it soon and provide feedback in a few hours.. Need to go out soon
[12:29] <kalikiana> no worries
[14:38] <rpadovani> hey mzanetti, I added some ActivityIndicator, what do you think?
[14:38] <rpadovani> https://code.launchpad.net/~rpadovani/reminders-app/18Mar14/+merge/211545
[14:39] <alaak> Hi. I am trying to develop an app for ubuntu touch but when I start the app with QML Scene I get "unity::action::ActionManager::ActionManager(QObject*): 	Could not determine application identifier. HUD will not work properly. 	Provide your application identifier in $APP_ID environment variable."
[14:39] <alaak> Can someone tell my what the application identifier is and where to set it? Do I truely have to define an environement variable?
[14:40] <alaak> This was not necessary for the example application.
[14:47] <mzanetti> rpadovani: quite busy atm. will check it out a bit later
[14:48] <rpadovani> np, have a good day :-)
[14:49] <daker> rpadovani: seems you have merge conflicts
[14:49] <rpadovani> daker, mhh, new autopilot tests, thanks, I fix them
[14:51] <nik90> alaak: that's not an issue
[14:52] <nik90> alaak: the reason you get that is because it requires the new HUD which is currently on the phone
[14:52] <rpadovani> daker, fixed, thanks
[14:52] <nik90> alaak: although in the the MainView, did you specify the applicationName ?
[14:53] <alaak> Just fixed it. It was in the applicationName. There was a small spelling mistake, though I do not believe that I edited this field in any way. Thanks for the help anyway.
[14:54] <nik90> alaak: no prob
[14:57] <dpm> mzanetti, hey, here's a picture featuring your app switching feature :) http://www.v3.co.uk/v3-uk/v3-co-uk-labs-blog/2333221/ubuntu-mobile-hands-on-review
[14:57] <mzanetti> dpm: nice :) thanks
[14:59] <nik90> dpm: it is a little bit annoying that those other people who just tried it on MWC have the cool stuff like the new Unity dash, scopes and app switcher while people on the proposed pocket still dont have it yet :D
[15:01] <dpm> nik90, indeed, I'm really looking forward to everything landing. But believe me, you want a more stable yet not that flashy version as in the current channels rather than the MWC image at this point :)
[15:01] <nik90> dpm: I know..its just the impatient side of me complaining :P
[15:01]  * dpm hugs nik90 :)
[15:06]  * dpm watches balloons fight with Jenkins on the calendar MPs :)
[15:06] <balloons> hey dpm, landed a bunch of stuff for reminders yesterday. long story short, introspection and launching now works and is in trunk
[15:07] <balloons> tests should be able to be written
[15:07] <dpm> balloons, I saw that, nice work!
[15:07] <dpm> balloons, what are the next steps? Do you need more bugs filed for tests, or are the current ones enough for the first iteration to put it in the image?
[15:07] <balloons> the diffs and amount of unmerged mp's was getting so large
[15:07] <balloons> needed to land some of it
[15:08] <dpm> that's absolutely fine, especially if it's for the sake of better QA!
[15:08] <balloons> on the calendar stuff, it's rather odd. I'm just going to start on the cleanup work and see if that fixes us
[15:12] <dpm> balloons, ok, thanks. So on Reminders, what do you think the way forward for AP tests is? ^^
[15:13] <balloons> at this point Carla should be able to fix-up her tests to run again with the changes to the app. Next, we'll incorporate the mocking work I did
[15:13] <balloons> with that we should have a working testsuite
[15:14] <balloons> dpm, for sake of my sanity if you have it handy, I could use the details on the mocked account we intend to use. I did the prototype using my own accoun
[15:14] <balloons> a fresh mail would be lovely
[15:15] <ondra> dpm: ping
[15:18] <dpm> balloons, sure, on it
[15:19] <dpm> hi ondra
[15:21] <dpm> balloons, e-mail with credentials sent
[16:05] <alaak> Is it possible to get the usual Qt Creator F1 Help in Ubuntu SDK? I only get "No Documentation" even if I select a core QML element (non Ubuntu Touch specific).
[16:34] <boiko> elopio: hey, do you have some time now to look into the messaging-app test failure?
[16:58] <elopio> boiko: in five minute?
[16:58] <elopio> minutes
[16:58] <boiko> elopio: sure, thanks
[17:01] <justCarakas> is it me or is it rather calm arount the appshowdown ?
[17:01] <justCarakas> *around
[17:02] <elopio> boiko: sorry, actually I need 15 minutes. BBS
[17:13] <boiko> elopio: ping me when you are free to look into that, no worries
[18:14] <elopio_> boiko: I'm back.
[18:14] <elopio_> my quassel server is crazy.
[18:17] <boiko> elopio: so, let's fix this
[18:19] <elopio_> boiko: the problem is that autopilot is getting an element, but by the time we are trying to click it, the element has changed and autopilot has a stale reference.
[18:20] <elopio_> my un-educated guess is that the list of messages is created, autopilot gets the reference here, then the list is sorted, so what autopilot has is no longer useful.
[18:20] <elopio_> boiko: but I don't know much about this. Is that possible?
[18:25] <boiko> elopio_: might be that, yes, we do use a proxy model to get new items sorted
[18:25] <boiko> elopio_: but actually the entries that were already in the storage should arrive already sorted
[18:26] <elopio_> boiko: I have no idea how to debug in order to check what's the object that autopilot is initially getting. But if we have a flag that turns into true when the list is ready sorted and redered, we could just wait for that to happen.
[18:27] <boiko> elopio_: that's hard to implement I think, cause the sorting is done behind the scenes by QSortFilterProxyModel, let me see if there is something interesting there
[18:32] <boiko> elopio_: maybe we should just wait a couple seconds before getting the delegates?
[18:34] <elopio_> boiko: that's the workaround I did. Wait 2 seconds, but it still failed. It's flaky, we will never know how many seconds we should wait.
[18:35] <boiko> elopio_: indeed
[18:37] <boiko> elopio_: do you still have the link to the failed tests log? I'm not finding it here
[18:40] <elopio_> boiko: I'm trying to run the tests on my desktop, but I get ofono-setup failed to create ofono account!
[18:40] <elopio_> do you know what I'm missing?
[18:40] <elopio_> boiko: one second to find the latest failed log
[18:41] <elopio_> it was on friday, so I have to dig a little.
[18:41] <boiko> elopio_: do you have telepathy-ofono installed there?
[18:41] <boiko> elopio_: if you don't have it handy, I can look here, no problems
[18:43] <elopio_> boiko: http://ci.ubuntu.com/smokeng/trusty/touch/mako/238:20140314.1:20140304/7158/messaging_app/897403/
[18:44] <boiko> elopio_: thanks
[18:44] <elopio_> boiko: yes, telepathy-ofono is installed
[18:44] <boiko> elopio_: can you run sh -x ofono-setup?
[18:45] <elopio_> boiko: sh: 0: Can't open ofono-setup
[18:45] <boiko> elopio_: sh -x /usr/bin/ofono-setup
[18:46] <elopio_> boiko: ofono/ofono/account0 initialized
[18:46] <boiko> elopio_: so now it worked
[18:48] <elopio_> boiko: but I run the test and it says:
[18:48] <elopio_> ofono/ofono/account0 initialized
[18:48] <elopio_> ofono-setup failed to create ofono account!
[18:48] <elopio_> mc-tool list doesn't return anything, that's what the test is checking.
[18:48] <elopio_> I don't know what mc-tool is
[18:48] <boiko> elopio: ahh, that's when running the tests, ok, different thing then
[18:48] <boiko> salem_: ^
[18:49] <boiko> salem_: have you seen that? a failure to create ofono account when running the tests
[18:49] <salem_> boiko, elopio hm, never seen this, but I know that mission control fails under qemu-armhf
[18:49] <salem_> elopio, is this a pbuilder?
[18:50] <elopio_> salem_: no, my real desktop with latest trusty, amd64
[18:54] <elopio_> wohoo, quassel is back.
[19:13] <elopio> boiko: my phone refuses to boot even after manually flashing it :/
[19:13] <elopio> have you found something interesting?
[19:14] <boiko> elopio: so, I was trying to reliably get the delegates but still nothing,
[19:15] <elopio> boiko: do you think it's because of the sort proxy?
[19:15] <boiko> elopio: not sure actually, shouldn't be I think
[19:15] <elopio> boiko: what else could make the object change after autopilot selects it?
[19:16] <elopio> I can pass questions to the autopilot devs when they arrive, but I'm not sure what to ask :)
[19:18] <boiko> elopio: good question, I don't know what is going on either
[19:21] <boiko> elopio: so, for testing purposes, I tried removing the sleep you added, and I get a different error, now the long press on the delegate (to enable selecting) doesn't seem to be long enough,
[19:21] <boiko> elopio: it is not entering the selection mode
[19:21] <elopio> boiko: how many seconds should we wait to enter selection mode>
[19:21] <elopio> ?
[19:23] <boiko> elopio: I think it is starting the long press before the listview settles, but anyway, with your sleep in there it gives more than enough time for the listview to be created and prepared
[19:33] <boiko> elopio: now for the actual failure there, I still don't know what we could do
[19:39] <elopio> boiko: it seems I'll have to install android to get my phone to work again. Once I have it, I can talk to the autopilot devs to see what info we can collect, or how to properly work it around.
[19:39] <elopio> if you find some useful information from the qml side, let me know. We can talk again tomorrow.
[19:40] <boiko> elopio: yep, I will continue looking into that
[21:46] <iBelieve> snwh: hey, any chance you could do a pull request or just give me the svg for the Project Dashboard icon sometime today or tomorrow? I'm hoping to release version 0.1 tomorrow evening, so it would be nice to have the icon for it.
[21:47] <snwh> iBelieve, i totally forgot to do thata
[21:56] <snwh> iBelieve, https://github.com/iBeliever/project-dashboard/pull/57
[21:56] <iBelieve> snwh: thanks a lot!
[21:57] <iBelieve> snwh: now I get to have fun and use my app to merge it :)
[22:29] <snwh> iBelieve, the 256x256 version https://dl.dropboxusercontent.com/u/7027392/project-dashboard.png
[22:29] <iBelieve> snwh: cool, thanks
[22:30] <snwh> i dunno why the app store version isn't the same as the app one
[22:30] <snwh> or at least the same dimensions
[22:31] <popey> oh man, you and all the rest of us too
[22:31] <popey> beuno: do we have a bug for "why the hell are the icons not the same dimensions"?
[22:31] <popey> we talk about it often enough it seems like someone should have this on their radar?
[22:37] <boiko> elopio: hey, I think I found what might be causing the problem
[22:38] <elopio> boiko: tell me more...
[22:38] <boiko> elopio: so, the HistoryEventModel updates que database query every time a property changes
[22:38] <boiko> elopio: so during component setup it updates the model contents a couple times
[22:39] <elopio> boiko: sounds like a good explanation.
[22:39] <elopio> boiko: any way to tell when it's done updating the model?
[22:39] <boiko> elopio: http://paste.ubuntu.com/7116752/
[22:40] <boiko> elopio: I think this would work (as the Component.onCompleted is only executed after the properties are bound)
[22:40] <elopio> boiko: looks pretty good :D You are awesome.
[22:40] <elopio> boiko: I would put it inside the open_thread method, so nobody forgets about that wait.
[22:41] <boiko> elopio: indeed that's a good idea, I just need to check how to use assertThat() from there
[22:41] <elopio> boiko: it's nicer. You do messages_page.loaded.wait_for(True)
[22:41] <boiko> elopio: awesome!
[22:42] <elopio> boiko: can you give it a try removing the sleep?
[22:42] <boiko> elopio: sure, let me see
[22:42] <elopio> I have my phone in androind, now figuring out how to return to ubuntu.
[22:44] <boiko> elopio: it still fails to do the long press there (I think it is starting the longpress too soon)
[22:45] <elopio> boiko: well, but that's improvement :D
[22:45] <boiko> elopio: yep
[22:46] <elopio> now we need to figure out where to wait for the bubble to be ready to receive input.
[22:49] <balloons> ping nik90 ahayzen
[22:49] <ahayzen> balloons, pong
[22:49] <balloons> ahayzen, :-) can you help me with some qml?!
[22:49] <ahayzen> balloons, heh maybe, whts up?
[22:49] <balloons> I need to move a dialog to be centered higher on the screen
[22:50] <ahayzen> balloons, never tried tht before...
[22:50] <balloons> ahayzen, do you understand anchors?
[22:50] <ahayzen> balloons, yeah
[22:50] <balloons> ahayzen, perfect. So I'd like to anchor it somewhere else
[22:50] <balloons> let me show you the snippet
[22:51] <balloons> http://paste.ubuntu.com/7116806/
[22:51] <balloons> so that works, but I'd like to move it without resorting to making a big margin on the bottom :-)
[22:51] <ahayzen> hmm
[22:52] <ahayzen> balloons, let me have a little play about
[22:54] <ahayzen> balloons, try putting for example anchors.topMargin: units.gu(-50)
[22:54] <balloons> k sec
[22:54] <balloons> ohh that looks cool
[22:55] <balloons> that works nicer, I'll use it
[22:56] <balloons> ty ahayzen !
[22:56] <ahayzen> balloons, np :)
[23:01] <balloons> qml is scary :p
[23:23] <popey> snwh: you still about?
[23:23] <snwh> popey, yep
[23:24] <popey> do you happen to have a 256x256 icon for sudoku?
[23:24] <popey> for the store
[23:24]  * balloons waves
[23:24] <balloons> https://code.launchpad.net/~snwh/sudoku-app/updated-icon
[23:25] <balloons> the icon is 512x480
[23:26] <snwh> well 1/2 that
[23:26] <popey> convert $1 -resize "256x256^" -gravity center -crop 256x256+0+0 +repage icon_$1
[23:26] <popey> do that ☻
[23:26] <popey> replacing $1 with the filename
[23:26] <popey> that'll crop it and keep the nice bits in the middle
[23:26] <snwh> actually it's 240x225
[23:27] <snwh> i have a 256x256 on hand
[23:28] <popey> can you throw it into balloons's virtual hands please?
[23:28] <snwh> (perhaps the store should start using the same dimensions)
[23:28] <popey> yes, yes it should.
[23:28]  * popey glares at beuno again
[23:28] <balloons> haha
[23:28] <balloons> I have a 256x256 cropped per popey..
[23:28] <balloons> I'll await your rendered version
[23:28] <popey> make sure it's not upside down or something
[23:28] <balloons> looks fine
[23:28] <popey> I am not an expert with convert
[23:29] <snwh> https://dl.dropboxusercontent.com/u/7027392/SudokuGameIcon.png
[23:29] <popey> nice!
[23:29] <snwh> i have it render to a square as well for this reason
[23:29] <balloons> ohh yea that looks nicer
[23:30] <balloons> in the store
[23:34] <popey> thanks snwh
[23:34] <snwh> not a problem