[00:17] <bjv> anyone familiar with the nature of coupling between ASOP v4.2 vs v4.3 or v4.4 and the ubuntu touch core platform/lxc container?
[00:18] <bjv> figured I might try my hand at porting touch to Nexus 5/hammerhead this weekend
[00:20] <bjv> since i didnt see an entry on https://wiki.ubuntu.com/Touch/Devices#Work_in_progress , and I have a Nexus 5/hammerhead sitting on my bench
[00:21] <bjv> the state of core platform compatability with AOSP v4.3 must be pretty terrible
[00:22] <bjv> I saw the old mailing list post that 2013 nexus7 is pending core compatibility with 4.3,
[00:26] <bjv> was a surprised that no wiki page had been created I suppose without a cm 10.1 branch the image build cant really get very far
[00:50] <popey> bjv: none of us have looked at the nexus 5 yet
[00:56] <bjv> popey: has the team looked yet at Touch with cm10.2 (milestone 1) on razorg/razor?
[00:57] <popey> bjv: no, internally we're only looking at gnex, n4, n7, n10 2012 editions
[00:58] <popey> we review this periodically, but not touched any newer devices yet
[00:58] <popey> i think janimo` may have done some work to make it easier to base off AOSP rather than CM, but I don't know the details.
[00:59] <popey> you'll have a better chance of speaking to someone here in the US morning / EU afternoon
[00:59] <popey> or use the phone mailing list
[01:54] <den4ik> after i have built an image how do i install it?
[02:10] <alesage> where would a d-bus denial be logged, e.g. attempting to send a signal?
[02:55] <endi> hey all
[02:56] <endi> just flashed 14.04 and when I try to connect to a WiFi network the keyboard doesn't respond. anyone able to point me to some documentation or how tos?
[02:56] <endi> I'd like to perhaps push a network config to the phone
[02:57] <popey> you can push network config to the phone with "phablet-network" script
[03:02] <den4ik> my branch not booting :(
[03:02] <den4ik> brunch
[04:23] <Home_> I recently installed the stable build of phablet to my nexus 7 2012, but I'm having a lot of trouble with the interface. I am wondering if anyone is  familar with it and can help me out
[05:16] <robru> Mirv, hey. are you working on unity stack?
[05:17] <Mirv> robru: yes
[05:17] <robru> Mirv, some hours ago i landed a fix for unity-lens-applications which was blocked by a manual distro upload
[05:18] <Mirv> robru: ok, cool. I'm interested in libunity now, and I was hacking cu2d to get it to test phase (which it now does) without aborting build.
[05:18] <Mirv> robru: since it seems it's blocking ~everything since unity depends on it and the chain continues from there
[05:18] <Mirv> I'll be testing it manually on phone and my own laptop too, but it doesn't hurt to get automatic test results too
[05:18] <robru> Mirv, i'm just a bit confused because http://10.97.0.1:8080/job/cu2d-unity-head-1.1prepare-unity-lens-applications/525/artifact/prepare_unity-lens-applications.xml this is from a few minutes ago and it doesn't seem to have noticed the fix i landed 3hrs ago
[05:19] <Mirv> robru: I'm not building anything, so it might be a false alarm therefore. it's skipping the prepare jobs in reality.
[05:20] <Mirv> it wouldn't give that message with your current trunk fix
[05:20] <robru> Mirv, oh, ok. well i don't want to cancel your job but if you get a chance please run the prepare step at some point and confirm that's fixed ;-)
[05:20] <Mirv> robru: ok, will do eventually, now trying these - and it seems the intel machine had a crash already :S
[05:20] <robru> bah
[05:21] <Mirv> nvidia still continuing, let's see
[05:21] <Mirv> robru: did you do the unity release a few hours ago?
[05:21] <robru> Mirv, yeah. sil asked me to get the updated unity-autopilot out.
[05:22] <Mirv> robru: yep, it's good. I see you aborted the build phase since it hanged at checking nux/compiz, but I cu2d-skip:d those myself
[05:22] <Mirv> robru: it's just that now I found out libunity is also required
[05:22] <Mirv> that should be the really final piece I believe
[05:22] <robru> Mirv, yeah, when i first looked at it it seemed the build phase had been running for many hours, so i aborted it
[05:22] <Mirv> robru: it's because sil removed compiz and nux PPA (on purpose)
[05:23] <Mirv> robru: but you can use the cu2d-skip from cupstream2distro/manual
[05:23] <robru> ah
[08:11] <tvoss_> michi, ping
[08:21] <rrix> Evening everyone; I'm trying to install the saucy preview on my mako device, but I'm getting a panic early in the boot process after doing a fresh reflash of Google's mako image followed by installing manually via fastboot directions lined out at https://wiki.ubuntu.com/Touch/Install#Manual_Download_.26_Installation
[08:21] <rrix> I can adb in to it, but there's not a lot mounted and I'm not too sure of how these file systems are laid out so that I can actually debug what's going on here
[08:21] <rrix> Any insights or pointings in the right direction on how to see what I messed up?
[08:24] <Mirv> rrix: what's the problem using phablet-flash ubuntu-system -b ?
[08:25] <rrix> [root@hobbes Downloads]# cat /etc/system-release
[08:25] <rrix> Fedora release 19 (Schrödinger’s Cat)
[08:25] <rrix> :)
[08:25] <rrix> actually it looks like it's just a python thing
[08:25] <rrix> let's see how hard it is to get working
[08:25] <Mirv> rrix: ah, I see. hmm, I obviously asked it as I don't know the low-level much.
[08:25] <rrix> No worries
[08:25] <Mirv> rrix: yep, it's just a python thing. you know how to unpack a deb?
[08:26]  * rrix isn't in too much of a rush to make this work, this isn't my main device any more so I can get away with breaking it for a few days
[08:26] <rrix> Mirv: I'm just pulling phablet-tools from https://code.launchpad.net/~phablet-team/phablet-tools/trunk
[08:26] <rrix> waiting for bzr to intsall
[08:26] <Mirv> rrix: that too, other way would be wget 'https://launchpad.net/ubuntu/+archive/primary/+files/phablet-tools_1.0%2B14.04.20131030.2-0ubuntu1_all.deb', file-roller *.deb etc
[08:27] <Mirv> the dependencies mentioned by the binary package are: android-tools-adb (>= 4.2.2), android-tools-fastboot (>= 4.2.2), bzr, curl, python-configobj, python-lzma, python-launchpadlib, python-requests, python-xdg, rsync, wget, python (>= 2.7), python (<< 2.8), python:any (>= 2.7.1-0ubuntu2)
[08:27] <Mirv> so I guess mostly really just adb + python for using the phablet-flash command
[08:28] <rrix> Yeah, makes sense
[08:28] <rrix> it looks like it's just a wrapper around adb to make it less likely to shoot yourself in the foot (hi)
[08:32] <Mirv> yes, I've found it relatively easy to shoot around with adb
[08:33] <Mirv> (having no android background before half a year)
[08:39] <sil2100> veebers: ping! :)
[08:39] <veebers> sil2100: pong
[08:39] <sil2100> veebers: I see the OSK-fix branch is still work-in-progress - is it really still worked on, or can we get someone to review?
[08:40] <veebers> sil2100: it's still WIP because I'm still experiencing crashes/failures (i.e. input not being recognised) :-\
[08:41] <sil2100> Ouch, ok! Just give us a sign once it's ready :)
[08:42] <Myrtti> is there any quick shortcut to change the keyboard layout?
[08:43] <veebers> sil2100: will do
[08:54] <rrix> hmm, this is taking significantly longer than the fastboot method, so that's a good sign
[08:54] <rrix> i think :P
[09:10] <rrix> yeah this works
[09:10] <rrix> okay good night
[09:47] <ogra_> asac, so given that trusty image #10 has better results than saucy #100 and #101 can we finally switch the devel and devel-proposed channels to trusty (to not be out of sync with the rest of the distro and documented behavior)
[09:53] <didrocks> didn't we say that we wait for a month before switching?
[09:53] <didrocks> (I'm happy with switching now though)
[09:53] <didrocks> but would be nice we draw a plan and stick to it :)
[10:03] <JamesTait> Good morning all; and though I hesitate to say it, happy Men Make Dinner Day! :-D
[10:04] <Mirv> JamesTait: phew, luckily it says only "National" on the home page, which seems to mean US, and not International
[10:05] <JamesTait> Mirv, feel free to play along, just for fun. ;)
[10:05] <Mirv> JamesTait: yeah, it's a good idea anyway ;)
[10:07] <Myrtti> I sense a tinned soup in my future
[10:08] <ogra_> didrocks, i would love to stop being out of sync with the rest of the distro (many people upload to "devel" instead of "trusty" already) and also get the naming confusion fixed, we should have switched on day one IMHO, it is "devel" after all ... not "stable"
[10:08] <didrocks> ogra_: oh, for devel, would make totally sense right
[10:09] <didrocks> I was thinking you talked about stable
[10:09] <didrocks> as well
[10:09] <ogra_> stable points to saucy anyway
[10:09] <didrocks> ogra_: did we test that switching will upgrade user?
[10:09] <ogra_> and will stay that way until trusty gets released
[10:09] <didrocks> and they won't need a -b 0 like trick?
[10:09] <ogra_> no idea, stgraber will have to tell us about that :)
[10:10] <ogra_> that shouldnt prevent us from pointing the channel to the right thing though :)
[10:10] <didrocks> heh, indeed :)
[10:24] <t1mp> how can I see which version of UITK was used for these tests? http://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/13:20131105.1:20131031.1/4910/ubuntu-ui-toolkit-autopilot/
[10:36] <sil2100> t1mp: I guess one way (not entirely straightforward) is to check the actual console log and seeing which version of UITK-autopilot is installed
[10:36] <sil2100> t1mp: like here https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-ubuntu-ui-toolkit-autopilot/13/consoleFull
[10:36] <sil2100> ubuntu-ui-toolkit-autopilot_0.1.46+14.04.20131105.1-0ubuntu1_all.deb
[10:36] <sil2100> ...I guess?
[10:56] <Mirv> t1mp: image #14 will have the 20131106 ui-toolkit release, and that's the thing to watch
[10:56] <Mirv> Myrtti: om nom
[11:00] <davmor2> Morning all
[11:06] <mandel_> didrocks, ping
[11:06] <didrocks> mandel_: pong
[11:06] <mandel_> didrocks, hello! I'd like to talk to you about some small changed that we are going to do that would be nice to have in the image
[11:06] <mandel_> didrocks, it fixes some annoying (at least for me bugs)
[11:07] <mandel_> didrocks, I'm adding support to get the updater to download the updates in order, I don't know if you have noticed that they download at random
[11:07] <mandel_> didrocks, also, if you are installing and app, close the preview and go back to it I'm going to show that is being downloaded, something that was not happening
[11:08] <mandel_> didrocks, and provide better feedback during the installation (adding 'Checking checsum' and 'Installing' to the progress bar
[11:08] <mandel_> is there anything I need to coordinate with you?
[11:08] <didrocks> mandel_: excellent! there is no breakage between components or do some needs to land in sync?
[11:09] <mandel_> didrocks, we need to land in sync several of them, that is why I wanted to talk with you
[11:10] <mandel_> didrocks, there is a fix to land for unity, other for the updater and the u-d-m
[11:10] <mandel_> AFAIK
[11:11] <mandel_> didrocks, I can coordinate with the others and get the revnos of the projects for you, for example
[11:11] <didrocks> mandel_: can we decouple the transaction, meaning if we publish new unity with older u-d-l and updater?
[11:12] <didrocks> or new u-d-m with older unity and updater, for instance?
[11:12] <mandel_> didrocks, we can do, new u-d-m (it is just adding a few new signals), then new click-scope, then updater and unity
[11:12] <mandel_> didrocks, that would be in 3 steps, updater and unity would be to go after u-d-m
[11:12] <mandel_> and click-scope
[11:13] <didrocks> mandel_: I'll love that we process this way, can you file all those infos (ensuring that everything is merged to trunk) with the exact name of the component in the landing ask?
[11:13] <didrocks> mandel_: TBH, as we finish the autopilot 1.4 transition, that will maybe just land early next week
[11:13] <mandel_> didrocks, sure :)
[11:13] <didrocks> mandel_: thanks a lot! please file and ping me so that we can check together if I have any question :
[11:13] <didrocks> :)
[11:14] <mandel_> didrocks, will do
[11:23] <Amnesia> question, how can I escape from the settings windows:)?
[11:23] <ogra_> swipe from the left
[11:23] <ogra_> (all the way to the right)
[11:24] <Amnesia> ah gotcha
[11:24] <Amnesia> that was kinda buggy:P
[11:24] <ogra_> then hold your thumb on the tumbnail until the close button appears
[11:24] <ogra_> ... and close it :)
[11:25] <Amnesia> ty^^
[11:25] <ogra_> (flicking to the home screen and back makes the close buttons on other open apps disappear again)
[11:26] <Amnesia> how far would you say the ubuntu-touch project is?
[11:27] <ogra_> usable on a daily basis
[11:27]  * ogra_ thinks ubuntu touch 1.0 is better than android 1.0 was :) 
[11:27] <ogra_> it still has a lot rough edges indeed
[11:27] <ogra_> i.e. i wouldnt recommend it for your mom before 14.04 is realased
[11:29] <Amnesia> :)
[11:29] <Amnesia> hm, well, I only need my tablet for reading books:P
[11:29] <Amnesia> but cyanogenmod is a pita too nowadays..
[11:35] <veebers> sil2100: ping
[11:36] <t1mp> sil2100, Mirv ok thanks. Just checking that a recent version is used
[11:38] <asac> ogra_: did we promote t #10?
[11:38] <ogra_> asac, yes ... inot trusty
[11:38] <ogra_> *into
[11:39] <asac> sure, then lets go for it
[11:39] <asac> ogra_: what do we need to do?
[11:39] <sil2100> veebers: pong!
[11:39] <ogra_> ok, i'll talk to stgraber later today
[11:39] <asac> ogra_: guessw wait for stgraber?
[11:40] <ogra_> asac, no, idea, thats stgraber-land :)
[11:40] <veebers> sil2100: hey, I've changed that branch to 'needs review'
[11:40] <asac> ogra_: so what is not clear to me is how the devel #100 useres will get upgraded to the new devel #10 build
[11:40] <veebers> sil2100: err, and by "that branch" I mean the ubuntu-keyboard one, link coming in a moment
[11:40] <ogra_> asac, worst case by calling system-image-cli -b0
[11:40] <asac> ogra_: well, they should auto update
[11:40] <asac> ogra_: we will have the same problem with the stable switch to T
[11:40] <ogra_> asac, if thats the case we need to work out a mechanism for the next time
[11:40] <asac> unless we release more than 100 images before :)
[11:40] <asac> hehe
[11:40] <ogra_> right
[11:41] <veebers> sil2100: I was able to finally get multiple full run-throughs without anything crashing: https://code.launchpad.net/~veebers/ubuntu-keyboard/fix_issues_with_ubuntu-keyboard-tests/+merge/194275
[11:41] <sil2100> ;)
[11:41] <sil2100> veebers: awesome!
[11:41] <asac> ogra_: so i was pointing out this problem to stgraber before we did the release etc.
[11:41] <asac> ogra_: he didn sound very worried, so i feel there must be a way
[11:41] <sil2100> veebers: super big thanks, let's get this reviewed - I'll try running it myself as well I guess
[11:41] <ogra_> asac, i think for the first time using system-image-cli is fine, we just need to fix it for the next time to be fully automatic
[11:41] <asac> who knows
[11:41] <veebers> sil2100: sounds good. Let me know how it goes and I can cover it in my morning
[11:41] <ogra_> in case thats actually needed ...
[11:42] <asac> i would prefer that we artificually bump our T build ID by 100
[11:42] <asac> and then switch
[11:42] <ogra_> but that will get messy over time
[11:42] <asac> if thatrs what it takes
[11:42] <asac> not sure why
[11:42] <sil2100> veebers: ACK, I'll e-mail you if I have any results
[11:42] <asac> we have lots of numbers available :)
[11:42] <veebers> sil2100: did you want me to hang around while it's reviewed?
[11:42] <asac> build 1 billion will be fun
[11:42] <veebers> oh or you can email me :-)
[11:42] <ogra_> i would assume we might have 100-200 builds per release ... at some point the number wont fit the UI anymore
[11:42] <asac> aaanyway. lets wait for him and then decide
[11:42] <ogra_> yeah
[11:42] <sil2100> veebers: I think it's already pretty late at your place, right?
[11:43] <veebers> sil2100: aye, it is
[11:43] <veebers> sil2100: but if you need me in 10 minutes, that saves waiting a whole day
[11:44] <sil2100> veebers: then I guess it's the right time to go and rest ;) I guess that even if we have any problems with this branch, it's not a big blocker as we're not running ubuntu-keyboard tests for images automatically anyway
[11:44] <sil2100> veebers: for now
[11:44] <sil2100> veebers: so at least we won't be completely stalled till tomorrow :)
[11:44] <veebers> sil2100: oh, ok sounds good. off to bed then :-)
[11:45] <sil2100> veebers: goodnight!
[12:07] <Wellark_> didrocks, pitti: bandaid MR for #1248880 approved.
[12:08] <jdstrand> cjwatson: hi! if I do 'pkcon install-local <click>' is 'pkcon remove <pkgname> <pkgvers>' expected to work now?
[12:08] <didrocks> Wellark_: excellent!
[12:09] <didrocks> Wellark_: so, you can't reproduce the issue on your phone with that one?
[12:10] <Wellark> didrocks: based on my quick testing the problem went away
[12:11] <didrocks> excellent
[12:11] <jdstrand> cjwatson: click list tells me it is installed, but both 'pkcon remove <pkgname> <pkgvers>' and 'pkcon remove <pkgname>' fail with:
[12:11] <jdstrand> Command failed: This tool could not find the installed package: could not find com.example.am-i-confined
[12:11] <didrocks> sil2100: once it's merged, mind handling network-indicator?
[12:11] <Wellark> didrocks: but, as stated in the MR this is just a bandaid and the "proper" fix needs big refactoring
[12:11] <didrocks> sil2100: see the bug report for the reproducer
[12:11] <didrocks> Wellark: I'm fine with that knowing where we went from ;)
[12:11] <Wellark> indeed.
[12:12] <sil2100> didrocks: ok, for now I'm testing the OSK
[12:13] <didrocks> Wellark: confirmed to works for me as well :)
[12:16] <Wellark> didrocks: great! I just want to point out Lars did all the heavy lifting on this one, so he should get the praise :)
[12:16] <didrocks> doing so on #ubuntu-desktop already ;)
[12:17] <Wellark> didrocks: we have to many irc channels :)
[12:18] <yarre> Does Touch email app support eas yet? (activesync)
[12:51] <hkker> o/, i was wondering if ubuntu touch is at this point that if i was to purchase a galaxy nexus could i use ubuntu daily? like for calling, messaging and wiki?'
[12:51] <hkker> or is is still unpredictable
[12:52] <Amnesia> hm, is there anyone over here who's ever ran arm linux on a tablet?
[13:03] <hkker> nvm found it on wiki, too bad it doesn't support mobile network yet :/, but one question remains -  how much does ubuntu effect the batery on galaxy nexus ? i mean like how many hours when idle and how many hours of call time it can cope with?'
[13:42] <lapor> hello
[13:42] <lapor> I'm back :)
[13:42] <lapor> a question
[13:43] <lapor> couple of days ago I was trying to change chennel for ubuntu touch to upgrade
[13:44] <lapor> in the end I managed to upgrade it to 14.04(r10)
[13:44] <lapor> but now it doesn't want to upgrade ower the wifi
[13:44] <lapor> any idea how to upgrade it to the latest iso image
[13:45] <lapor> to build 20131107
[13:45] <ogra_> lapor, check what channel you are on with system-image-cli -i
[13:46] <ogra_> lapor, looks like thats the trusty channel, which only gets blessed images ... since #10 we didnt release any
[13:47] <lapor> ou, ok
[13:47] <t1mp> did http://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/14:20131107:20131031.1/4933/ finish testing, or are missing tests still being added as they get completed?
[13:47] <lapor> then I'll have to wait :)
[13:48] <ogra_> t1mp, the dashboard syncs based on a cron entry ... that tests run elsewhere ... so they might have run already, but are not presented
[13:48] <lapor> channel is trusty
[13:49] <lapor> and I'll have to wait
[13:49] <ogra_> lapor, right, as i thought ... if you want bleeding edge you can switch to trusty-proposed, but that might have breakage up to points where you cant upgrade anymore in the worst cases
[13:50] <lapor> fno problem
[13:50] <lapor> I can wait
[13:50] <t1mp> ogra_: ok, thanks
[13:50] <lapor> I just thought that there are some problems with updating the device
[13:51] <ogra_> http://reports.qa.ubuntu.com/smokeng/trusty/touch/ shows the test results btw, anything with a fail rate around what #10 has there will be released into the trusty channel ...
[13:52] <lapor> so mako 10 was around 96%
[13:52] <lapor> we can expect that every image that is 96% or more will get to us?
[13:53] <ogra_> well mako 10 had 13 failures ... if the failures in a later image are around the same amount and not in critical components the image is moved
[13:54] <lapor> ogra thanks
[13:54] <asac> rsalveti: !! :)
[13:54] <lapor> I'll bookmark this page and will check it up daily
[13:59] <didrocks> oSoMoN: hey, the webbrowser-app failure on http://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/14:20131107:20131031.1/4933/ is the one your fixed?
[14:00] <oSoMoN> didrocks, yes, fixed in trunk with revision 401
[14:00] <didrocks> oSoMoN: excellent!
[14:00] <didrocks> oSoMoN: please don't merge anything there until we ship it (probably in few hours)
[14:01] <oSoMoN> didrocks, got it
[14:11] <davmor2> ogra_: the dailer/phone calls would be tied into phone-app correct?
[14:12] <ogra_> davmor2, i think it is actually called dialer-app
[14:12] <davmor2> ogra_: yes I was wondering if it's name changed when it all got split out
[14:13] <davmor2> ogra_: thanks
[14:13] <ogra_> yup
[14:14] <yarre> Does Touch email app support eas yet? (activesync)
[14:21] <ogra_> yarre, there is no touch email app yet :) ... there is a gmail webapp though
[14:24] <davmor2> seb128: on image 14 setting→date time is blank is this a wip or a bug?
[14:26] <popey> davmor2: bug here too
[14:26] <popey> s/bug/blank/
[14:26] <davmor2> I'll add a bug then :)
[14:27] <seb128> davmor2, ui-toolkit regression
[14:28] <davmor2> seb128: right that'll be the same thing for the solitare games, game chooser then I guess
[14:28] <seb128> davmor2, guess so
[14:28] <davmor2> seb128: do you know if there is a bug for it, if not I can put one together
[14:28] <seb128> davmor2, https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1248646
[14:28] <davmor2> seb128: thanks
[14:29] <seb128> yw
[14:30] <Test__> hello
[14:38] <Mirv> seb128: I just let t1mp know (if he didn't) that it's a "non-greenness" regression so a fix for that should go into ui-toolkit
[14:39] <Mirv> seb128: oh well, technically it's not on dashboard if it's only settings, but a regression nevertheless
[14:39] <seb128> Mirv, yeah, everybody agreed yesterday to restore compat
[14:39] <Mirv> seb128: alright
[14:40] <Mirv> the sdk team was apparently discussing if the MP should be split in smaller pieces, though
[14:47] <Mirv> in general I guess that means ui-toolkit remains frozen for other than regression / AP fixes
[14:51] <seb128> kenvandine, charles, Laney, tedg: want to do a settings meeting this week or should we just saw each other/didn't do much since and should we skip this one?
[14:52] <Laney> skipping would be ok with me
[14:52] <kenvandine> i'd say skip, we have a good idea of what needs doing right now
[14:53] <seb128> ok
[14:53] <seb128> kenvandine, charles, Laney, tedg, mardy: no settings meeting this week
[14:54] <charles> seb128, k
[14:54] <mhall119> rsalveti: happy birthday!
[14:54] <tedg> K
[14:54] <rsalveti> mhall119: thanks :D
[14:56] <stgraber> asac: the client tracks the alias change, so moving the alias from devel => saucy to devel => trusty will trigger a full update automatically
[14:56] <stgraber> ogra_: I'm around now
[14:57] <ogra_> stgraber, so we would like to switch the devel alias over to trusty
[14:57] <stgraber> ogra_: ok, all of them? (devel, devel-customized, devel-proposed, devel-proposed-customized)
[14:57] <asac> stgraber: ok so you get one FULL update.. .sounds reasonable
[14:58] <asac> guess is the best way to do it given that we want to be flexible moving aliases back and forth :)
[14:58] <asac> stgraber: can we move an alias also backwards :)?
[14:58] <ogra_> stgraber, yeah, for consistency
[14:58] <asac> stgraber: like moving stable to trusty ... and then in a month back to saucy just because we want to have fun?
[14:58] <stgraber> asac: yep, we can, the client doesn't know whether an alias is higher than another, it'll just do a full update whenever that changes, so we can totally move them back from trusty to saucy
[14:58] <asac> nice
[14:59] <asac> i like that property ... even though its unlikely to happen
[14:59] <stgraber> ogra_: ok, let me do that now, should just take a minute
[14:59] <ogra_> asac, not talking about breaking all the instaleld apps by tearing out the toolkit under them indeed :)
[14:59] <asac> ogra_: our platform should have proper toolkit versioning
[14:59] <ogra_> stgraber, awesome !
[14:59] <asac> ogra_: so yeah, it might break apps that require toolkit v2
[14:59] <asac> but our platform should explicitely disable them (instead of having buggy apps )
[15:00] <asac> e.g. grey them out
[15:00] <ogra_> asac, it does, but if i install a click package for the 14.04 toolkit and you move my system image back to saucy my apps wont work
[15:00] <asac> ogra_: its also important for me to switch channels while keeping my apps
[15:00] <asac> ogra_: thats a separate problem. shouldnt't happen
[15:00] <ogra_> but that will only work forward
[15:00] <asac> we must be very strict about our API ... and we will be in in the future
[15:00] <ogra_> backward will make your apps either not show up or not start or something
[15:01] <ogra_> so we should never consider such a backwards move
[15:01] <ogra_> even if it is theoretically possible
[15:01] <ogra_> it will make users cry
[15:01] <asac> we should :)
[15:01] <asac> we definitely must even
[15:01] <asac> we want to go backwards from time to time
[15:01] <ogra_> but better not in ABI versioning
[15:02] <stgraber> ogra_, asac: all done
[15:02] <ogra_> i personally would be pretty surprised if half of my apps vanish with a system update
[15:02] <asac> ogra_: that we also want to support
[15:02] <ogra_> how ?
[15:02] <asac> ogra_: we wont force you to downgrade... but our platform must support it so we can backout bogus image roll outs etc.
[15:02] <asac> ogra_: its easy
[15:03] <ogra_> if my app is written for toolkit 2 and the system rolls back to 1 my app wont be able to work
[15:03] <asac> just requires our teams that maintain an API to apply highest standards to stability
[15:03] <ogra_> so it will be hidden or uninstalled or whatever
[15:03] <asac> right
[15:03] <asac> it will be greyed out
[15:03] <ogra_> that will still not give you ABI2 functions in ABI 1
[15:03] <ogra_> right
[15:03] <asac> explaining that your OS is not new enough
[15:03] <asac> if thats the case we have done it cleanlyu
[15:03] <ogra_> and since i updated i as a user wont understand why
[15:04] <ogra_> thats something to do under lab conditions, but surely nothing to do out there in the wild to our users
[15:04] <asac> ogra_: well. i would love to have a switch in my settings allowing me to select the channel i want... and also go from devel to stable etc.
[15:05] <asac> our device should just behave correctly in that case
[15:05] <ogra_> sure, for devs who know what it could cause thats fine
[15:05] <asac> apps nicely greyed out with an explain that it needs a newer Ubuntu Phone OS
[15:05] <asac> etc.
[15:05] <ogra_> but the minority of our users will be devs at some point
[15:05] <ogra_> (hopefully)
[15:05] <asac> ogra_: so the fact that we surely dont want to move our mainstream users back forcefully doesnt mean that we should check that our platform etc. supports it perfectly
[15:05] <asac> hehe
[15:05] <ogra_> if you go back and forth yourself thats fine
[15:06] <ogra_> but if the devel or stable channels change underneath endusers so that their apps dont work thats not
[15:06] <asac> ogra_: right. but then there might be this super unlikely corner case where we move our stable users to Xurary
[15:06] <asac> and during our staged roll out notice that the world explodes
[15:06] <asac> so we move them back to Werty
[15:06] <asac> but yes, normally going back is something you as a user do explicitely
[15:06] <ogra_> that means our staged rollout doesnt work
[15:07] <cjwatson> tmoenicke: Could you top-approve https://code.launchpad.net/~cjwatson/ubuntu-keyboard/python-any/+merge/194310 ?  I've addressed the reason ps-jenkins failed
[15:07] <cjwatson> (i.e. set a commit message)
[15:15] <ogra_> wow, image 14 degraded quite a bit
[15:19] <asac> ricmm: MIR on N7 looking solid?
[15:19] <ogra_> tsk
[15:19] <ogra_> can only have one ... fast or solid
[15:19] <ogra_> :P
[16:02] <boiko> pitti: hey, where did you find those magic numbers of phonesim?
[16:04] <pitti> boiko: in /usr/share/phonesim/default.xml
[16:04] <boiko> pitti: ah nice! thanks
[16:07] <popey> sergiusens: https://bugs.launchpad.net/music-app/+bug/1248997
[16:07] <popey> trying to figure out where the .desktop file is getting mangled
[16:08] <popey> sergiusens: looks like the click package you sent me has it pre-mangled before click installs it on the phone
[16:08] <popey> sergiusens: i just unpacked com.ubuntu.music_1.1.237_armhf.click with ar -x, and see the mangled version
[16:19] <sergiusens> popey, let me check that
[16:20] <ogra_> slangasek, FYI, i added you as essential to https://blueprints.launchpad.net/ubuntu/+spec/core-1311-early-boot-animation
[16:21] <slangasek> ogra_: ack
[16:23] <Guest87261> Ubuntu touch on Nokia 808 possible?
[16:23] <sergiusens> popey, I found the error; wondering how it happened now
[16:35] <sergiusens> popey, I wonder how that error ever happened, can't see it locally
[16:39] <popey> odd
[16:39] <popey> your click package is intact?
[16:42] <cjwatson> ogra_: just as a point of information, we don't "reinstall or update" click packages after a system update; we do run hooks which occasionally takes a small amount of time, although I suspect not enough to be worth progress-barring
[16:43] <ogra_> cjwatson, oh, referring to the spec ? well, i just tried to make up an example
[16:44] <cjwatson> right, I just wanted to avoid this leaking into things people ask me about for months to come :)
[16:44] <ogra_> heh, ok, i'll drop that
[17:14] <cwayne> asac: ping :)
[17:33] <user82> has anyone talked to skype yet, about ubuntu touch?
[17:40] <t1mp> did AP 1.4 land? I.e., can we commit stuff to UITK trunk again?
[17:40] <a_muva_> I need to report a bug. where can I do that? When someone calls me with restricted number, phone does not ring. The call is being transfered to voice mail.
[17:40] <t1mp> ogra_: image 14 degraded? for maguro the tests went from 90.7% to 91.1%
[17:41] <t1mp> ogra_: for mako it went down 1% (
[17:41] <t1mp> :(
[17:42] <a_muva_> skype? I think someone should talk to Jitsi.
[17:42] <a_muva_> Debian sid has Jitsi in it repos.
[17:51] <cjwatson> a_muva_: it's only not in Ubuntu yet because it fails to build - https://launchpad.net/ubuntu/+source/jitsi/2.3.4687.9786-1
[17:52] <cjwatson> And "amd64 i386" isn't desperately promising for the phone
[17:52] <cjwatson> that failure's probably just a busted link line, not too hard for somebody to fix if they care
[17:58] <a_muva_> cjwatson: I can download theirs deb, and everything works on ubuntu or debian
[17:59] <cjwatson> a_muva_: Sure, but in order for it to be in Ubuntu it has to be buildable in Ubuntu.
[17:59] <cjwatson> Which, thankfully, probably isn't that hard to fix if you're motivated to do so.
[18:18] <robru> t1mp, ping. any ETA on those ui-toolkit patches landing?
[18:22] <kenvandine> mhall119, did you ever publish those content hub docs?
[18:24] <robru> davmor2, hey. I reported one of your tracebacks upstream and they're asking you to downgrade a package and reproduce the failure. can you help with that? https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1248310
[18:25] <mhall119> kenvandine: not yet, but I have the ability to update the API website now, so I can
[18:26] <kenvandine> mhall119, cool
[18:26] <davmor2> robru: I probably can but not today I'll add a task for tomorrow if that's okay
[18:26] <robru> davmor2, no worries
[18:27] <mhall119> kenvandine: doxygen? :(
[18:28] <mhall119> ah, nvm, I see the separate qdocs for QML now
[18:32] <ogra_> t1mp, we are measuring against the last released image ... which was #10
[18:34] <mhall119> kenvandine: "ContentItem - FIXME add documentation" :/
[18:34] <kenvandine> yeah... it isn't complete yet :)
[18:45] <sergiusens> popey, can you look into getting someone to look at this https://code.launchpad.net/~vthompson/music-app/fix-shuffle-test/+merge/193722
[18:50] <popey> sergiusens: sure
[19:05] <mhall119> kenvandine: http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Content/ look good to you?
[19:07] <kenvandine> mhall119, mostly, the introduction/overview is linked at the bottom
[19:07] <kenvandine> what can we do to make that more prominent?
[19:08] <mhall119> we can put pages above elements
[19:09] <mhall119> but we'd have to do it for all sections, not just Ubuntu.Content
[19:09] <mhall119> which might be okay
[19:10] <kenvandine> i was just browsing around, that is consistent
[19:10] <kenvandine> i'd say it should be on top
[19:13] <mhall119> kenvandine: well that'll take a new release deployment, so it'll have to wait
[19:13] <kenvandine> mhall119, sure, not urgent
[19:14] <mhall119> kenvandine: is the content-hub what system settings uses to select a background image?
[19:14] <kenvandine> mhall119, yes
[19:14] <kenvandine> and address book uses it to select  contact phot
[19:14] <kenvandine> +o
[19:16] <mhall119> kenvandine: does it support more than just pictures?
[19:16] <kenvandine> so far documents, videos and pictures
[19:16] <mhall119> but not music?
[19:16] <kenvandine> oh, music not videos :)
[19:17] <mhall119> ok
[19:17] <kenvandine> but we don't have apps for those that implement the import/export handler
[19:20] <mhall119> kenvandine: the music-app should be able to export music, how hard would that be to add?
[19:25] <tmoenicke> cjwatson: its merged already, thx
[19:27] <kenvandine> mhall119, not hard
[19:27] <kenvandine> mhall119, but... the hub doesn't support export initated transfers yet
[19:31] <nik90> kenvandine: would this content hub be extended to other content types? For instance a recipe app being a content store for recipes etc?
[19:31] <nik90> kenvandine: or would we be sticking to standard file types such as document, music, videos, photos/
[19:33] <nik90> mhall119: I noticed a bug
[19:33] <nik90> mhall119: in the page http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Content/
[19:34] <nik90> mhall119: if you click on the overview link in the sidebar, instead of going to the qml overview, it goes the web overview
[19:34] <nik90> despite the overview link be presented under the QML header
[19:36] <mhall119> nik90: yeah, because it's a separate site from the rest of developer.u.c we have to keep the side-nav in sync, and when it's out of sync (like it is now) it won't work as expected (like it does on that link) :(
[19:36] <mhall119> I'll work up a fix
[19:36] <nik90> ah
[19:36] <nik90> no worries, just letting u know
[19:37] <kenvandine> nik90, right now the plan is for a set of defined types
[19:38] <kenvandine> nik90, but you could perhaps export it as a document
[19:38] <kenvandine> plain text or something
[19:38] <nik90> kenvandine: can any app become the content store? For instance right now the gallery app is the photos owner, can I have my app be the photos owner?
[19:38] <kenvandine> yes
[19:38] <kenvandine> well... not the system default one
[19:38] <kenvandine> but
[19:39] <kenvandine> your app will own it's own photos
[19:39] <kenvandine> and your app could implement an ImportExportHandler
[19:39] <kenvandine> and register with the hub as a handler
[19:39] <nik90> ah okay
[19:39] <kenvandine> then apps could select photos from your app
[19:39] <kenvandine> nik90, there are two paths to choose where to select content from
[19:39] <nik90> so when the user searches for photos, it could potentially show my app and the gallery app as photo sources
[19:39] <kenvandine> choose the default for type
[19:40] <kenvandine> or select from a list of apps that implement it
[19:40] <kenvandine> yes
[19:40] <nik90> nice that makes sense
[19:40] <kenvandine> and that works today
[19:40] <kenvandine> you just need to implement the handler
[19:40] <kenvandine> and use the click hook
[19:40] <nik90> I am making a movies app, so hopefully I can register that as a source for videos
[19:40] <kenvandine> great
[19:41] <kenvandine> for 14.04 the hub will be much more complete, we implemented just enough to support the use cases for setting background image and contact photo
[19:42] <kenvandine> i'm working on the opposite direction now, where you could say i want to send this content to another app
[19:42] <kenvandine> like the browser could open an image downloaded from the web in gallery-app
[19:42] <kenvandine> or a pdf in the document view
[19:42] <kenvandine> +er
[19:43] <kenvandine> mhall119, i guess i have motivation to fix those FIXMEs now :)
[19:44] <kenvandine> nik90, i would love to have someone else take the QML bindings for a spin... I'd appreciate feedback :)
[19:47] <mhall119> kenvandine: yeah, you'll need to let me know when there's new docs though, it doesn't update automagically
[19:48] <kenvandine> mhall119, will do
[19:51] <nik90> kenvandine: will do
[19:52] <kenvandine> nik90, and example of an app that implements and ExportHandler (other apps can request content from it) https://code.launchpad.net/~ken-vandine/+junk/hub-exporter
[19:52] <kenvandine> and an import handler https://code.launchpad.net/~ken-vandine/+junk/hub-importer
[19:53] <nik90> awesome
[19:53] <timppa> terminal app seems to have major issues with keyboard not showing on r15
[19:56] <mhall119> kenvandine: having those as examples in the API docs would be nice :)
[19:56] <kenvandine> for the most part they are
[19:56] <kenvandine> :)
[19:56] <kenvandine> but those include the bits for click packaging
[19:57] <kenvandine> much of that code is copied from the docstrings
[20:17] <kenvandine> seb128, mind reviewing a branch for me?
[20:17] <kenvandine> https://code.launchpad.net/~ken-vandine/content-hub/qdoc_fixmes/+merge/194412
[20:17] <kenvandine> seb128, ^^
[20:18] <seb128> kenvandine, that's after work hours, I'm going to have to ask for beers at the next team meeting for that ... ;-)
[20:18] <kenvandine> haha :)
[20:18] <kenvandine> i can do that
[20:18] <kenvandine> or wait until tomorrow :)
[20:18] <kenvandine> mhall119, that'll get rid of those FIXMEs
[20:18] <seb128> kenvandine, what do you drop FIXME without adding the documentation?
[20:19] <kenvandine> i did add it where it was needed
[20:19] <kenvandine> those dropped ones are \internal
[20:20] <seb128> kenvandine, how come you added an \internal for ContentItem::name() and not the other ones?
[20:20] <kenvandine> because i'm not convinced that should be public
[20:20] <kenvandine> it isn't used internally
[20:20] <kenvandine> and not even in the c++ API
[20:21] <seb128> kenvandine, ok, fair enough, approved then ;-)
[20:21] <kenvandine> so it's existences is really ignored
[20:21] <kenvandine> great, thanks
[20:21] <seb128> yw
[20:21] <seb128> no going to miss those easy beers ;-)
[20:21] <kenvandine> :)
[20:30] <jdstrand> hmm, is there a problem with 'adb devices' on grouper with trusty now?
[20:31] <jdstrand> I boot it, it gets to the greeter and then 'adb devices' doesn't show anything
[20:31] <jdstrand> adb devices works fine if I plug in my mako
[20:31] <cwayne> ok ogra_ I got my n5 where's the ubuntu port :P
[20:35] <mhall119> kenvandine: is qtdeclarative5-ubuntu-content0.1 part of ubuntu-sdk?
[20:35] <kenvandine> no
[20:35] <mhall119> if not, it should be, same with Friends and OnlineAccounts
[20:35] <kenvandine> agreed
[20:36] <mhall119> Mirv: ^^ can you add those to the ubuntu-sdk package?
[20:38] <mandel_> sergiusens, ping
[20:39] <sergiusens> mandel_, pong
[20:39] <mandel_> sergiusens, quick question, what is the command to ssh into a ubuntu touch device?
[20:41] <sergiusens> mandel_, to start the server? or ssh in?
[20:42] <sergiusens> mandel_, adb shell start ssh and ssh phablet@[IP] respectively
[20:42] <mandel_> sergiusens, thx!
[20:45] <seb128> kenvandine, btw, I can't status approve your mr so you need to do it
[20:47] <cwayne> sergiusens: ping
[20:48] <nik90> kenvandine: I ran your hub_importer on mako. I can select the pictures in the gallery, however on clicking "pick" it returns to the hub_importer and then the screen goes blank and then it quits.
[20:48] <nik90> kenvandine: another issue was that on running it on the desktop, I get errors
[20:48] <nik90> I did install the required packages
[20:49] <sergiusens> cwayne, pong
[20:49] <kenvandine> nik90,  did you install both of them as click packages?
[20:49] <cwayne> sergiusens: hey, did you want to setup a time today or tomorrow re: ufacts?  or were the docs sufficient?
[20:51] <kenvandine> nik90, oh... right you only need the importer
[20:51] <kenvandine> and that should select from gallery-app
[20:51]  * kenvandine tests that again
[20:51] <sergiusens> cwayne, I think we are good, I created a blueprint to discuss stuff that you can subscribe to
[20:52] <sergiusens> cwayne, let me process a bit more and I might ping you back earlier though if you don't mind
[20:52] <cwayne> sergiusens: sounds good to me
[20:52] <cwayne> sergiusens: don't mind at all! happy to help :)
[20:54] <kenvandine> nik90, interesting... doesn't even launch on my mako
[20:55] <kenvandine> creating surface at (0, 58) with size (768, 1222) with title 'Window 1'creating surface at (0, 58) with size (768, 1222) w
[20:55] <kenvandine> ith title 'Window 1'This plugin does not support propagateSizeHints()
[20:55] <kenvandine> QUbuntuWindow::setGeometry (this=0xbbeb8)Detectable autorepeat not supported.
[20:55] <nik90> kenvandine: I launched it through qtcreator
[20:55] <kenvandine> it needs to be installed as a click
[20:55] <kenvandine> for the apparmor stuff
[20:56] <nik90> kenvandine: when you launch it through qtcreator it is not confined, so it still works
[20:56] <nik90> the app redirected me to the gallary and I picked images
[20:56] <nik90> its just that when it returned back to the app, I saw the images I picked
[20:56] <nik90> but a second later the app turned black for no reason
[20:57] <kenvandine> ah.... yeah that is the app manager
[20:57] <kenvandine> it switches back with upstart-app-launch
[20:57] <kenvandine> not sure that would work for an app that is started from qtcreator
[20:58] <nik90> ah
[20:58] <nik90> is there a easy way to create a click package and test on phone?
[20:59] <kenvandine> yeah
[20:59] <kenvandine> click build .
[20:59] <kenvandine> from your checkout
[20:59] <kenvandine> then push it to the phone
[20:59] <kenvandine> sudo click install  --user=$USER com.ubuntu.developer.ken-vandine.hub-importer_0.1_all.click
[20:59] <kenvandine> on the phone
[20:59] <nik90> kenvandine: okay
[21:00] <nik90> but I do think that this process of testing content-hub should be easier
[21:00] <kenvandine> although that provides weird results for me
[21:00] <nik90> otherwise it is a hassle to test code frequently
[21:00] <cwayne> kenvandine: i think it's preferred to do pkcon install-local
[21:00] <sergiusens> kenvandine, prefer pkcon install-local
[21:00] <kenvandine> yeah
[21:00] <kenvandine> cwayne, or that :)
[21:00] <cwayne> instead of click install + click register
[21:00] <kenvandine> pkcon install-local file.click?
[21:00] <sergiusens> so it's a _2
[21:00] <sergiusens> +2
[21:00] <jdstrand> fyi, for posterity, I needed to poweroff the nexus 7 (hold power and volume down, then cycle through to Power Off). after that, I booted it and it showed up with 'adb devices'
[21:00] <cwayne> kenvandine: yep
[21:00] <sergiusens> as the phablet user
[21:00] <kenvandine> coll...
[21:01] <kenvandine> cool even
[21:01] <nik90> too fast for me to process :P
[21:01] <kenvandine> i wrote the first iteration of pkcon many years ago :)
[21:01] <kenvandine> when i was a PackageKit developer :)
[21:01] <cwayne> sergiusens: that seems like a useful thing to be in phablet-tools..
[21:02] <sergiusens> cwayne, yeah; there's a carla sella who i don't know how is called on irc that wrote a small script for testing/building
[21:02] <sergiusens> cwayne, http://paste.ubuntu.com/6353571/
[21:02] <kenvandine> nik90, the hard part is the hub triggers application switching through the app manager
[21:02] <kenvandine> so taking you back to the originating app
[21:03] <kenvandine> it does that with the APP_ID
[21:03] <cwayne> sergiusens: ah, thanks
[21:04] <nik90> kenvandine: there is an option in the build menu to install click package on device. It automatically created the click and installed it on my phone :)
[21:04] <kenvandine> oh, great :)
[21:04] <nik90> now it works properly
[21:04] <kenvandine> i hadn't noticed that :)
[21:04] <cwayne> i never trusted it :) good to hear it actually works though
[21:04]  * sergiusens doesn't use qtcreator
[21:04] <nik90> cwayne: hehe..it was pretty quick
[21:05] <nik90> now I wonder if I do it again, will it replace the existing click install
[21:05] <kenvandine> i'll happily use pkcon, for nostalgia :)
[21:05] <nik90> this way I could test it every few minutes
[21:05] <kenvandine> nik90, i suspect it would
[21:05] <cwayne> nik90: it will
[21:05] <nik90> kenvandine: btw is the finalize import button necessary?
[21:05] <nik90> it is greyed out when I returned to the hub importer
[21:06] <cwayne> sergiusens: hey, do you have a link to that blueprint you mentioned?
[21:06] <nik90> cwayne: awesome
[21:06] <kenvandine> nik90, no, it was for testing purposes
[21:06] <kenvandine> if you don't provide a ContentStore in the transfer request, it'll copy the data to a temporary app specific location
[21:07] <kenvandine> finalize cleans up that cache
[21:07] <kenvandine> if you don't do it, it'll get cleaned up later
[21:07] <nik90> ah okay
[21:08] <sergiusens> cwayne, yeah, one sec
[21:08] <kenvandine> it has to do that because your app doesn't have access to the data from the other app
[21:09] <kenvandine> so if you specify your own ContentStore, the resulting items will persist in your store
[21:09] <kenvandine> if you don't it goes to an app specific HubIncoming
[21:09] <sergiusens> cwayne, https://blueprints.launchpad.net/ubuntu/+spec/core-1311-touch-hardware-validation-framework
[21:09] <kenvandine> which isn't persistent
[21:09] <sergiusens> cwayne, not much in there yet
[21:09] <cwayne> sergiusens: perfect, thanks
[21:10] <kenvandine> nik90, what image build do you have?
[21:10] <kenvandine> i can't get it to start with 15
[21:10] <nik90> kenvandine: trusty r11
[21:15] <firelmnt> i'd like to build u-touch but which manifest is the right for editing repo?
[21:16] <nik90> kenvandine: I notice that http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Content.ContentType/ doesnt list videos. Can you add that when you are free.
[21:16] <kenvandine> i will
[21:16] <kenvandine> i need to add a few
[21:16] <nik90> thnx
[21:39] <nik90> kenvandine: hey do you have a few minutes to explain hub-exporter? I understand some parts.
[21:40] <szymon_w> hi! How to add delete confirmation to ListItem when onItemRemoved function is used in ubuntu SDK ? ( this confirmation is used in core apps like contacts-app messaging-app etc. )
[21:40] <nik90> szymon_w: let me look it up..5 secs
[21:41] <kenvandine> nik90, it gets installed as an app that can be a source for images
[21:41] <kenvandine> like gallery-app is
[21:41] <kenvandine> it defaults to just a single image though
[21:41] <nik90> szymon_w: so in the list item, you add a property removable: true
[21:41] <kenvandine> hard coded rather
[21:41] <kenvandine> so it's an installed peer
[21:41] <nik90> szymon_w: and then confirmRemoval: true
[21:41] <kenvandine> you could them make the importer request it as a peer instead of the defaultPeerForType
[21:42] <nik90> kenvandine: what does this line var result = resultComponent.createObject(root); do?
[21:43] <nik90> szymon_w: http://paste.ubuntu.com/6378653/ is a code sample from the clock app
[21:43] <szymon_w> nik90, works like harm :) thx!
[21:43] <nik90> szymon_w: pretty sure you mean charm :)
[21:44] <nik90> meant*
[21:44] <szymon_w> nik90, I was missing confirmRemoval .
[21:44] <nik90> szymon_w: yup
[21:44] <szymon_w> nik90, forgive me spelling ;) we all know what I meant :D
[21:44] <nik90> szymon_w: although it will show a gray trash icon against your green background for your ushopper app
[21:45] <nik90> szymon_w: I have already reported a bug against the theming of the confirm removal icon
[21:45] <nik90> hope that gets fixed
[21:45] <nik90> grey*
[21:45] <szymon_w> nik90, I noticed...
[21:45] <kenvandine> nik90, ok, so that is how you create a ContentItem instance
[21:45] <szymon_w> nik90, that's awesome!
[21:46] <kenvandine> i don't really know why that isn't easier
[21:46] <szymon_w> nik90, thanks for your help again ;)
[21:46] <kenvandine> the constructor prevents you from just declaring one
[21:46] <nik90> szymon_w: np
[21:46] <nik90> kenvandine: ah okay
[21:46] <kenvandine> not saying it is intuitive :)
[21:46] <nik90> hehe
[21:46] <kenvandine> i wonder if there is a good reason for that
[21:47] <kenvandine> that is part of what gusch did
[21:47] <kenvandine> the transfer can't be declared, and that makes sense to me
[21:47] <kenvandine> since it is an object that is shared between 3 processes
[21:47] <kenvandine> and the hub brokers it
[21:47] <kenvandine> so you have to request it from the hub
[21:47] <nik90> kenvandine: one more question
[21:47] <i-want-ubuntu-on> Hey, has Ubuntu for tablets been released yet? News outlets are giving me conflicting information.
[21:48] <nik90> kenvandine: so only when I press the export button will the image be available to other apps is it?
[21:48] <kenvandine> yes
[21:48] <kenvandine> the exporting app has to say it's finished adding items to the transfer
[21:48] <nik90> kenvandine: okay. I can technically make it to export items on every app launch?
[21:48] <kenvandine> then the importing app gets the signal and can collect the items
[21:48] <kenvandine> sure
[21:49] <kenvandine> just get the transfer object, add items to it and "charge" it
[21:49] <kenvandine> generally there would be some picking UI, for selecting items and a button to call charge
[21:50] <nik90> kenvandine: I wouldnt have to create the UI for selecting content to import when called by other app?
[21:50] <kenvandine> charging the transfer then tells the hub it's ready to be collected, and marshals the data
[21:50] <nik90> kenvandine: like the one shown by the gallery app?
[21:50] <kenvandine> gallery-app provides that picking UI
[21:50] <kenvandine> so it sees there is a transfer request
[21:51] <kenvandine> and switches to picking mode
[21:51] <nik90> oh
[21:51] <kenvandine> so the exporting app provides the UI for picking
[21:51] <kenvandine> we'll probably have some generalized components you could just use
[21:52] <nik90> kenvandine: ah that's why you created the connection with the onExportRequested signal
[21:52] <kenvandine> but usually your app will already have a presentation UI... just need to tweak it
[21:52] <kenvandine> yeah
[21:52] <nik90> when that signal is triggered by the other app I go to pick mode
[21:52] <kenvandine> yup
[21:53] <nik90> nice, this is easy. I will look to make a sample app around this for others
[21:53] <kenvandine> great!
[21:53] <kenvandine> glad you think it's easy :)
[21:53] <nik90> :)
[21:53] <kenvandine> some things don't really translate well to declarative
[21:53] <kenvandine> like the transfer has to be requested from the hub
[21:54] <kenvandine> i can't make that simpler
[21:54] <kenvandine> but i might be able to make the ContentItem simpler
[21:55] <nik90> yeah it is a bit strange to see the variable ContentHub or ContentTransfer appear out of nowhere
[21:55] <nik90> but that's just getting used to it
[21:55] <den4ik> who have built crespo image successfully?
[21:55] <kenvandine> yeah, those both have to work that way
[21:55] <kenvandine> but ContentPeer and ContentItem might be able to be simplified
[21:55] <kenvandine> i'll think about that a bit
[21:56] <nik90> okay