[08:05] <Saviq> guys, can someone please take care of https://code.launchpad.net/~saviq/unity8/clean-build-scripts-coding/+merge/173847
[08:53] <nic-doffay> Saviq, quick question have you ever had an issue with QML objects being instantiated recursively?
[08:54] <Saviq> nic-doffay, not that I can remember
[08:54] <nic-doffay> Saviq is there any way I can get a detailed stacktrace to figure this out?
[08:57] <Saviq> nic-doffay, use the Qt debugging session in QtCreator - it'll let you break in JS / inspect objects and such
[08:58] <nic-doffay> Saviq, helpful thanks·
[09:36]  * greyback bbiab
[09:38] <nic-doffay> Saviq, trying to import Ubuntu.Components 0.1 but it's claiming ambiguity. Any ideas?
[09:38] <Saviq> nic-doffay, what did you do to get to that state?
[09:39] <nic-doffay> other .qml files in examples/ubuntu-ui-toolkit-gallery in the ubuntu-ui-toolkit import it without issue.
[09:39] <nic-doffay> I'm creating a new gallery test for the themed optionSelector.
[09:40] <Saviq> nic-doffay, not sure, if the others work fine, there's nothing I can think of that'd make yours fail
[10:01] <dpm> happy birthday Saviq and Saviq_ ;)
[10:31] <greyback> Saviq: clean-build-scripts-coding approved
[10:33] <nic-doffay> Anyone have any tips on sorting out weird QML ambiguous import issues?
[10:38] <greyback> nic-doffay: set the environment variable QML_IMPORT_TRACE, it will print debug info on where imported plugins are sought for and located
[10:38] <greyback> s/it/qml/
[10:38] <pete-woods> guys, I *think* I'm having trouble with user identity on the phone
[10:38] <pete-woods> the apps are running as the user phablet, I think
[10:39] <pete-woods> but the greeter thinks the login user is called "single"
[10:39] <pete-woods> this means that the infographic data gets filed under a different username
[10:40] <pete-woods> should I be detecting the username different in the infographic input API?
[10:40] <pete-woods> or should the mock lightdm backend have the username match the real user?
[10:40] <pete-woods> *differently
[10:43] <nic-doffay> greyback, thanks that helps a lot!
[10:47] <tvoss_> Saviq, ping
[10:50] <nic-doffay> greyback, setting the env var before running ./gallery.sh. Not seeing any additional output...
[10:55] <greyback> nic-doffay: What gallery is that? uitk?
[10:55] <nic-doffay> greyback, that's the one.
[10:56] <nic-doffay> I'll pastebin you the error, it's confusing.
[10:56] <greyback> works for me: QML_IMPORT_TRACE=1 ./gallery.sh
[10:58] <nic-doffay> greyback, yep but I'm not getting any extra info for whatever reason on that issue, I see the other imports...
[10:59] <greyback> nic-doffay: what do you want to learn? What's going wrong?
[10:59] <nic-doffay> greyback, check this out: https://pastebin.canonical.com/94379/
[10:59] <nic-doffay> All I'm doing in importing Ubuntu.Components
[10:59] <nic-doffay> In the qml file.
[11:00] <nic-doffay> Basically exactly like every other example in the gallery as far as I can tell.
[11:01] <greyback> nic-doffay: smells like a uitk bug. Lemme see
[11:02] <greyback> nic-doffay: I'm not reproducing it here however. You using uitk trunk? Have you a value set for QML_IMPORT_PATH in your shell?
[11:03] <greyback> is almost as if the same directory is in the list of import directories twice
[11:04] <nic-doffay> greyback, it's in my OptionSelector branch.
[11:04] <greyback> nic-doffay: link?
[11:04] <nic-doffay> greyback, one sec let me push.
[11:06] <nic-doffay> greyback, lp:~nicolas-doffay/+junk/option-selectors
[11:07] <nic-doffay> If you run the gallery and select OptionSelector tab you'll see what I mean.
[11:08] <nic-doffay> Basically I moved the OptionSelector from the ListItems to Components.
[11:08] <Cimi> Saviq_, https://code.launchpad.net/~unity-team/unity8/unity8.colour_palette/+merge/174678
[11:08] <nic-doffay> Since there will be four variations of it.
[11:09] <greyback> nic-doffay: well reproduced. Am digging
[11:09] <nic-doffay> greyback, ta.
[11:10] <nic-doffay> greyback, I've only added it to components, this is what's throwing me off the ambiguous output, unless I've missed something.
[11:11] <greyback> nic-doffay: you are importing Ubuntu.Components in modules/Ubuntu/Components/OptionSelector.qml
[11:11] <greyback> but that's defining Ubuntu.Components, so is circular dependency
[11:14] <nic-doffay> greyback, where should I be importing Ubuntu.Components then?
[11:16] <greyback> nic-doffay: use it only outside the modules/Ubuntu/Components directory. If you're inside that directory, use "import ." to import the qml files in that directory instead
[11:17] <greyback> nic-doffay: "import ." is a silly suggestion - it's done automatically.
[11:17] <nic-doffay> greyback, that's what I assumed.
[11:18] <nic-doffay> greyback, so surely importing qtquick would be enough?
[11:19] <nic-doffay> greyback, without importing Ubuntu.Components OptionSelector isn't found.
[11:19] <nic-doffay> Even though it's in the Components dir.
[11:20] <greyback> nic-doffay: this does it for me: http://pastebin.ubuntu.com/5877125/
[11:20] <greyback> nic-doffay: did you add the component to the qmldir file?
[11:21] <nic-doffay> greyback, yeah
[11:21] <nic-doffay> in the components qmldir
[11:21] <greyback> nic-doffay: well then that patch above seems to fix it for me, reasonably well anyway
[11:21] <greyback> you only needed QtQuick, and to also inclde the ListItems directory as a namespace (ListITem)
[11:22] <nic-doffay> greyback, ah got it.
[11:22] <greyback> cool
[11:22] <nic-doffay> greyback, forgot that I moved it out the dir and had to explicitly import the items.
[11:22] <nic-doffay> ta for the help!
[11:23] <greyback> np
[11:27] <tvoss_> Saviq, ping
[11:45] <Saviq_> tvoss_, pong
[11:45] <Saviq_> thanks dpm :)
[11:56] <Saviq> dednick, https://code.launchpad.net/~saviq/unity8/drop-indicator-recommends/+merge/174534 btw
[11:58] <dednick> Saviq: do we install recommends on phone? should we not recommend indicator-server in that case?
[12:00] <arsson> So is there any how to use unity8 an actual session?
[12:00] <Saviq> dednick, no, it's taken care of by the seed
[12:00] <dednick> Saviq: ok
[12:00] <Saviq> arsson, what do you mean by "an actual session"?
[12:01] <Saviq> arsson, we only support android's surface flinger at the moment, Mir support is happening as we speak, at which point you will be able to get the unity8 experience from the phone/tablet on your desktop
[12:01] <Saviq> arsson, only with Qt apps for the start, other toolkits coming later to the party
[12:02] <arsson> Savig: i mean that i can choose in lightdm unity8 session and it could be usable
[12:04] <Saviq> arsson, not yet
[12:04] <arsson> ok
[12:04] <Saviq> arsson, should be there by the end of the month
[12:05] <arsson> where can i find info when it's possible?
[12:07] <Saviq> ooh a doodle just for me :D
[12:18] <arsson> cool
[13:00] <dandrader> I'm getting a long pause and this error by the end of a ./build: http://paste.ubuntu.com/5877350/
[13:01] <dandrader> has anyone seem this as well?
[13:02] <dandrader> might be from the qmlplugindump tool...
[13:04] <dandrader> Although it puzzles me why are we trying to start a service during a build....
[13:12] <Saviq> dandrader, interesting... but I imagine yes, the plugin dump tool is probably recognized as an application by the hud
[13:12] <Saviq> s/the hud/bamf/
[13:12] <Saviq> dandrader, or actually...
[13:13] <Saviq> dandrader, the plugin itself is probably instantiated, and is waiting for the hud to show up on the bus
[13:13] <Saviq> that's probably the more reasonable explanation
[13:13] <Saviq> dandrader, OTOH wouldn't that block in CI?
[13:14] <dandrader> Saviq, no, it hangs for a while and then timesout
[13:15] <dandrader> Saviq, there's  might be something wrong in my setup. apt-get autoremove removed qmenumodel-qml
[13:15] <dandrader> Saviq, but it is used
[13:15] <dandrader> Saviq, by Components/VolumeControl.qml at least
[13:16] <Saviq> dandrader, yeah, it's needed, but nothing depends on it
[13:16] <dandrader> Saviq, so I wonder why unity8-build-deps haven't brought it
[13:16] <Saviq> dandrader, it's a runtime dep
[13:16] <Saviq> dandrader, so somehow it got marked as auto-installed
[13:17] <Saviq> dandrader, and now got removed after whatever it was installed with got away
[13:17] <Saviq> dandrader, ./build -s will sort you out again
[13:17] <dandrader> Saviq, I think it happened during the indicators-client switch
[13:17] <Saviq> dandrader, it's possible indeed
[13:18] <dandrader> the shuffling of packages my have led to some weird state during my apt-get dist-updrage this morning
[13:18] <Saviq> dandrader, as for the hud timeout, HudClient::HudClient() calls hud_client_query_new("") which is probably blocking
[13:19] <Saviq> and times out after 30s waiting for the service
[13:20] <Saviq> dandrader, so if qmlplugindump actually instantiates the registered types - that's probably our problem
[13:20] <dandrader> hmm, I also get this block-and-timeout when I ./run
[13:20] <Saviq> dandrader, yeah, your hud doesn't work
[13:21] <Saviq> dandrader, actually I think I know why it might not timeout on CI - it probably just fails straight away, 'cause there's no hud .service file
[13:21] <dandrader> Saviq, is that expected or am I missing some runtime dependency?
[13:21] <Saviq> dandrader, no, not expected
[13:21] <Saviq> dandrader, `apt-cache policy hud` ?
[13:22] <dandrader> Saviq, http://paste.ubuntu.com/5877427/
[13:22] <Saviq> dandrader, mine's 13.10.1+13.10.20130703-0ubuntu1 still
[13:22]  * Saviq upgrades
[13:23] <Saviq> yikes! 338 packages to upgrade?
[13:25] <dandrader> :D
[13:25] <Saviq> let's see what breaks
[13:25] <dandrader> "expect some bumps along the road"
[13:26] <Saviq> dandrader, `status hud` btw
[13:26] <dandrader> Saviq, is this hud the one used also by unity 7 or is it a unity8-only thing?
[13:27] <dandrader> status hud -> "hud stop/waiting"
[13:27] <Saviq> dandrader, it's the same
[13:27] <Saviq> dandrader, `start hud`
[13:28] <Saviq> dandrader, and see `status hud` and check out ~/.cache/upstart/hud.log
[13:28] <Saviq> for any obvious run failures
[13:28] <dandrader> Saviq, hmm, right. the hud shows up in my unity 7 but if I type anything its "waiting" icon stays there forever
[13:29] <Saviq> dandrader, yeah, mine isn't really working either
[13:29] <dandrader> ah, it got auto-started now that I tried to use it
[13:29] <dandrader> but still not working
[13:29]  * dandrader checks log
[13:30] <dandrader> it has just a bunch of warnings complaining about some missing bamf interfaces in dbus
[13:30] <dandrader> Saviq, ^
[13:41] <Cimi> Saviq, so for the wallpaper, what shall we do?
[13:41] <Cimi> Saviq, connect the property with the system settings?
[13:42] <Saviq> Cimi, yes, the usual for now
[13:42] <Cimi> ok
[13:42] <Cimi> Saviq, who is leading the system setting app?
[13:42] <Saviq> Cimi, seb128
[13:46] <greyback> mterry: QT_QPA_PLATFORM=ubuntumirserver
[13:47]  * Saviq reboots, wish me luck
[13:48] <greyback> mterry: mir_demo_server& then mir_demo_client_accelerated
[13:49] <greyback> mterry: ubuntu-touch-session  should be version 	1:0.57-0~75+77~saucy1
[13:57] <mterry> greyback, I just ended up pushing it from my computer to the device.  No change once installed
[13:57] <greyback> mterry: did you reboot after installing it?
[13:58] <mterry> greyback, no; duh
[13:58] <Trevinho> dandrader: the api has not changed.. Strange (also if I deprecated few things I'd like to get rid of soon)
[14:06] <greyback> mterry: any good?
[14:07] <pete-woods> mterry: lightdm mock question - would it be a lot of work (or crazy) to change the name of the fake user "single" to match up with the real user being used ("phablet")
[14:07] <pete-woods> mterry: it seems to be causing the infographics data to be filed under the wrong user
[14:08] <mterry> greyback, hmm, sorry, had network problems apparently.  Let me resend messages:
[14:08] <mterry> (after rebooting device)
 greyback, OK.  server && client_accelerated works.  Thanks.  So Mir itself is capable.  Running unity8, I see that Ubuntu.Application can't be found, like it's not setting the right QML path for it
 greyback, manually setting that, I get a segfault after some warnings about not being able to claim a dbus name, oddly
[14:09] <mterry> pete-woods, hm? causing the infographics data to be filed under the wrong user when actually running on device?
[14:09] <greyback> mterry: yep, as U.A not available yet, need to run unity8 in test mode. That is one of the things the run script did, set the correct paths.
[14:11] <mterry> greyback, except it didn't.  it didn't set the QML path to the right place to pick up Ubuntu.Application
[14:11] <mterry> It used /usr/share/unity8/plugins
[14:11] <mterry> vs /usr/lib/arm-linux-gnueabihf/qt5/imports
[14:11] <mterry> greyback, why run unity8 in test mode?  U.A is available, eh?
[14:12] <greyback> mterry: U.A. is not available, it uses hybris which we don't want. I'm writing the new one
[14:13] <pete-woods> mterry: yeah, it's going under the "phablet" user, as that's what the apps are running as
[14:13] <greyback> mterry: so try pointing it to  /usr/share/unity8/plugins/mocks
[14:13] <greyback> just to get it going
[14:14] <mterry> pete-woods, ah!  I see.  Yeah, change the demo plugin to use 'phablet', makes sense.  Don't change the other plugins though, as those are used for tests
[14:15] <pete-woods> mterry: cool. that's why I wanted to check - wasn't sure which bits should change
[14:16] <mterry> greyback, (I believe that's /usr/lib/arm-linux-gnueabihf/unity8/qml/mocks these days)
[14:17] <mterry> greyback, huh, OK!  Using the mock, I get a unity8 image on the screen, but it's super tiny (quarter size or so in bottom left) oddly
[14:20] <greyback> mterry: ok, you need to set GRID_UNIT_PX=18, then try again
[14:20] <greyback> odd as those vars are set in my env
[14:20] <mterry> greyback, yup, OK.  Nice
[14:20] <mterry> greyback, hm.  Do you know from whence they are set?
[14:22] <greyback> mterry: the grid unit in /etc/ubuntu-touch-session.d/<codename>.conf
[14:22] <greyback> not sure about the QPA though
[14:22] <greyback> /etc/environment
[14:23] <mterry> greyback, hm, troubling that I don't have them set.  I wonder what else is messed up
[14:23] <greyback> mterry: indeed. I use SSH all the time now, you can launch mir from it now
[14:23] <greyback> so no need for adb shell
[14:27] <greyback> mterry: could you do me a favor and pastebin me the output of "dpkg -l" from your phone? I want to check the versions of your egl libs to compare with mine
[14:28] <mterry> greyback, http://pastebin.ubuntu.com/5877623/
[14:30] <greyback> mterry: many thanks
[14:46] <dandrader> Saviq, so, are you getting that Hud timeout after dist-upgrading and rebooting
[14:46] <dandrader> ?
[14:53] <didrocks> mhr3: do you know/have a link to what translates from LT_VERSION to .so.<current-age>.?.? and set the right soname?
[14:53] <didrocks> mhr3: I can't find the macro making that…
[14:53] <mhr3> didrocks, iirc it's done manually
[14:54] <didrocks> mhr3: you don't seem to do that like for libunity9 "-version-info $LIBPROTOCOL_LT_VERSION"
[14:54] <didrocks> mhr3: but no trace of CURRENT-AGE
[14:56] <mhr3> didrocks, then it's ld itself
[14:56] <didrocks> mhr3: ok
[14:57] <mhr3> didrocks, or well, libtool
[15:00] <didrocks> mhr3: seems to be libtool: http://www.unbound.net/pipermail/unbound-users/2012-January/002190.html
[15:02] <mhr3> makes sense
[15:04] <seb128> mhr3, hey, I've a question for you
[15:04] <mhr3> seb128, the answer is maybe
[15:04] <seb128> good answer!
[15:04] <seb128> mhr3, looking at /usr/share/unity/scopes/photos.scope
[15:05] <seb128> mhr3, SearchHint=Search photos
[15:05] <mhr3> right
[15:06] <seb128> mhr3, is that what is displayed in the dash?
[15:06] <seb128> mhr3, if so where is string marked as translatable? e.g in what gettext domain should it be and how is it added it there (I guess it's not atm which is what makes me look at it)
[15:06] <seb128> data/master-scopes/photos.scope.in.in:_SearchHint=Search photos
[15:06] <seb128> in fact
[15:06]  * seb128 wonders why it's not in the pot
[15:06] <mhr3> seb128, yea, that's where it's marked for translation
[15:07] <seb128> for some reason intltool-update --pot doesn't list it
[15:07] <mhr3> and the domain is what's defined in the scope file
[15:07] <mhr3> seb128, hmm... not sure why
[15:07] <seb128> [type: gettext/ini]data/home.scope.in.in
[15:07] <seb128> I've a feeling the type is wrong
[15:07] <Saviq> dandrader, no, it passed fine (although the unity7 hud doesn't work still)
[15:08] <mhr3> seb128, oh, the files aren't listed in POTFILES.in
[15:08] <mhr3> that's why
[15:08] <seb128> mhr3, oh, right
[15:08] <seb128> mhr3, can you fix that? ;-)
[15:08] <Saviq> paulliu, btw, .../tests/plugins/Unity/previewbindingstest.cpp:0: Note: No relevant classes found. No output generated.
[15:08] <seb128> mhr3, do you want a bug report about it?
[15:09] <mhr3> seb128, no need, fixing
[15:09] <Saviq> paulliu, there's an unnecessary #include for the .moc
[15:09] <Saviq> dandrader, yeah, it passes through just fine
[15:09] <dandrader> :(
[15:09] <seb128> mhr3, thanks
[15:09] <seb128> mhr3, don't forget to prefix them [type: gettext/ini] or that will not work
[15:10] <seb128> mhr3, I just confirmed it works with that though ;-)
[15:11] <paulliu> Saviq: ok
[15:12] <mhr3> seb128, https://code.launchpad.net/~mhr3/unity-scope-home/update-potfiles/+merge/174787
[15:12] <mzanetti> dandrader: Saviq: sitting in a Mouse/touch session. What exactly is our reason to convert mouse->touch?
[15:12] <dandrader> mzanetti, I thought you were on holidays?
[15:12] <mzanetti> dandrader: no. QCS
[15:12] <paulliu> Saviq: I'll fix it.
[15:13] <dandrader> QCS?
[15:13] <mzanetti> Qt Contributors Summit
[15:14] <dandrader> mzanetti, DirectionalDragArea handles only touch events
[15:14] <mzanetti> dandrader: the qt guys think about merging touch/mouse in upcoming releases
[15:15] <mzanetti> so that might be good for us
[15:16] <mzanetti> dandrader: so is it only an implementation detail of DDA or is there a technical reason we can only use touch events in there?
[15:16] <seb128> mhr3, thanks, approved
[15:16] <dandrader> mzanetti, gesture recognition will fail if a second touch point appears
[15:17] <dandrader> mzanetti, you wouldn't have this info using mouse events
[15:17] <mzanetti> dandrader: ah ok. perfect.
[15:17] <mzanetti> thanks
[15:18] <dandrader> mzanetti, and it also enables those scenarios where you can manipulates multiples things simultaneously
[15:18] <dandrader> s/s//
[15:18] <Saviq> mzanetti, yeah +1 on merging touch with mouse I think
[15:18] <mzanetti> the question came up what we do with hovering etc
[15:18] <mzanetti> I guess thats broken right now for us
[15:19] <Saviq> mzanetti, yeah, we don't get that with touch
[15:20] <dandrader> if I recall correctly android's input stack is like that (touch and mouse are "merged")
[15:22] <Saviq> dednick, did you see #ubuntu-unity? seems password entry in network indicator is broken
[15:26] <dandrader> Saviq, rebooted my desktop. now Hud doesn't hang anymore
[15:26] <Saviq> dandrader, cool
[15:28] <dandrader> the old adage: when something inexplicable is happening, try rebooting
[15:31] <Saviq> dandrader, http://www.youtube.com/watch?v=nn2FB1P_Mn8
[15:33] <dandrader> :)
[16:25] <pete-woods> folks: are some of the unity tests unstable at the moment?
[16:26] <pete-woods> I just got a fail on a test I don't think I should have affected: https://code.launchpad.net/~pete-woods/unity8/change-user-single-to-phablet/+merge/174792
[16:27] <pete-woods> the test is something about ListViewWIthPageHeaderTestSection
[16:34] <dednick> Saviq: sorry. been out for a bit. taking a look now
[16:39] <greyback> pete-woods: have you merged trunk recently? If not commit 92 might help
[16:40] <pete-woods> greyback: I branched from commit 107, but thanks for the suggestion
[16:40] <pete-woods> it's really an utterly trivial change
[16:41] <pete-woods> mterry: have you seen the error in the MR you approved for me just a short while ago before?
[16:42] <nic-doffay> Saviq, ping
[16:44] <paultag> Anyone see https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1051921 ? Seems to be an easy fix …
[16:44] <Saviq> nic-doffay, pong
[16:44] <nic-doffay> Saviq, UbuntuShape option looks awesome btw!
[16:45] <nic-doffay> One question though regarding changing an Image source property.
[16:45] <Saviq> nic-doffay, cool
[16:45] <nic-doffay> At the moment I've done it using logic, should I be using state changes instead?
[16:45] <greyback> pete-woods: kick it again and cross fingers?
[16:45] <nic-doffay> Not sure what the best QML way to do it is.
[16:45] <pete-woods> greyback: okay, trying that! :)
[16:46] <nic-doffay> Saviq, it's just the simple change between tick and chevron but it will get a bit more complicated when I colour it with a shader for the various themes.
[16:46] <nic-doffay> Obviously want minimal clutter.
[16:46] <nic-doffay> Can you change an image's source with a state?
[16:46] <greyback> nic-doffay: yes
[16:47] <nic-doffay> greyback, PropertyChange { source: } ?
[16:47] <greyback> nic-doffay: that's it
[16:47] <nic-doffay> PropertyChanges sorry
[16:47] <greyback> nic-doffay: there's no hard fast rule, but if you've several properties to change at once, using States helps a lot
[16:48] <nic-doffay> greyback, in this case it's only one.
[16:48] <greyback> nic-doffay: only 1 property to change? Or only 1 State?
[16:49] <Saviq> nic-doffay, wouldn't just "source: someProperty ? chevron : tick" suffice?
[16:50] <greyback> nic-doffay: I'm a fan of States, but I only use it if I have (say) >3 properties with the trinary operator (property)?yes:no :
[16:50] <Saviq> nic-doffay, and re: colourizing it, you talked with the SDK guys about that?
[16:50] <greyback> nic-doffay: fewer, I wouldn't bother
[16:50] <nic-doffay> Saviq, yeah I have.
[16:50] <Saviq> nic-doffay, k
[16:50] <nic-doffay> they agree with my approach.
[16:50] <nic-doffay> fewer assets the better.
[16:51] <nic-doffay> I always try stick by that.
[16:52] <nic-doffay> Saviq, regarding the source: someProperty it would work.
[16:52] <nic-doffay> But it gets a bit complicated with the expansion thing.
[16:52] <Saviq> nic-doffay, your call, realy
[16:52] <Saviq> ly
[17:01]  * greyback eod
[17:02] <Cimi> who can review the theming branch?
[17:02] <Cimi> seb128, ping :)
[17:03] <nic-doffay> Saviq, it's pretty close to completion now. Fancy taking a preliminary look before I put it up for merging?
[17:03] <seb128> Cimi, hey, don't look at me for theming!
[17:04] <Saviq> nic-doffay, not today, but yeah, would gladly see it at work
[17:04] <nic-doffay> Saviq, no rush.
[17:04] <Saviq> nic-doffay, the real review will have to happen by SDK guys anyway
[17:04] <nic-doffay> Saviq, yep.
[17:04] <nic-doffay> Still need to chat to them about documenting it well.
[17:05] <nic-doffay> I really like the look of the ubuntu shape one though!
[17:05] <nic-doffay> doubt people will use the ListView version ^_^
[17:06] <Saviq> nic-doffay, depends on where it'll be ;)
[17:06] <Saviq> nic-doffay, if standalone - probably, if in a list of other ListItems, probably not :)
[17:06] <nic-doffay> Saviq, good point haha
[17:14] <Cimi> seb128, I just need for the background
[17:16] <seb128> Cimi, what do you need?
[17:16] <Cimi> seb128, we'd like to have the system settings app control the background of unity
[17:17] <seb128> Cimi, right, that's done
[17:17] <Cimi> seb128, does it already work??
[17:17] <Cimi> what am I missing :)
[17:17] <seb128> Cimi, just make unity read org.gnome.desktop.background picture-uri
[17:17] <seb128> in gsettings
[17:17] <seb128> Cimi, dunno about unity
[17:17] <seb128> Cimi, you should read that gsettings key ;-)
[17:23] <Cimi> indeed
[17:33] <Cimi> dednick, hey dude
[17:33] <Cimi> dednick, do we have example code reading from dconf?
[17:34] <Cimi> maybe unity 2d...
[17:34] <Saviq> Cimi, nope
[17:34] <Saviq> Cimi, qsettings-qt
[17:34] <Saviq> erm
[17:34] <Cimi> ok
[17:34] <Saviq> gsettings-qt
[17:35] <Saviq> Cimi, but talk to seb about this, sync with the settings app
[17:36] <Cimi> ok
[17:36] <Cimi> Saviq, they already set it
[17:37] <Cimi> Saviq, all we need is to look for this dconf
[17:37] <Saviq> Cimi, not dconf
[17:37] <Saviq> Cimi, that's an impl detail
[17:37] <Saviq> Cimi, in $settings_backend
[17:37] <Cimi> ah ok
[17:37] <Cimi> Saviq, so you want the settings app to change the property?
[17:38] <Saviq> Cimi, if you mean the setting value, yes
[17:38] <Cimi> Saviq, maybe they could change both
[17:38] <Saviq> Cimi, and we should just read it - most probably through gsettings-qt
[17:38] <Cimi> Saviq, like both changing the setting for unity
[17:38] <Cimi> ah ok
[17:38] <Cimi> gnome will still use dconf
[17:39] <Saviq> Cimi, no, gnome uses gsettings ;)
[17:39] <Saviq> Cimi, with a dconf backend, sure, but not directly dconf
[17:39] <Cimi> Saviq, exactly
[17:40] <Saviq> Cimi, yes, and we'll be using the same
[17:40] <Saviq> Cimi, gsettings-qt is a Qt wrapper around gsettings
[17:42] <Cimi> I'll have a look during my flight
[17:50] <seb128> Cimi, Saviq:
[17:50] <seb128> https://code.launchpad.net/~laney/ubuntu-system-settings/background-gsettings/+merge/171995
[17:50] <seb128> that's a simple example
[17:51] <Cimi> seb128, good
[17:51] <Cimi> I'll look into it
[17:51] <Saviq> seb128, awesome, did you guys consider a per-form-factor setting? like an overlay for different ffs, for example?
[17:54] <seb128> Saviq, not that I know of, we just followed the current design and the wallpaper didn't seem something too specific to the screen size
[17:54] <seb128> but yeah, that's worth keeping in mind
[17:55] <Saviq> seb128, yeah, it's a pretty generic topic
[17:55] <Saviq> seb128, and probably a per-setting one
[17:56] <Saviq> seb128, i.e. there might be different default values for a setting depending on form factor, but then if you change them, does it apply to both? or just the one you've changed it in?
[17:57] <Saviq> and if you then change it after having switched to a different ff, does it "trickle" back to the other one?
[17:57] <seb128> Saviq, thanks for raising the topic, I'm going to put that on the agenda for our meeting this week ;-)
[17:58] <Saviq> seb128, cheers :)
[17:58] <seb128> on that note diner time
[17:58] <seb128> have a good evening everyone
[17:58] <seb128> bbl
[21:53] <veebers> ugh, does anyone else get this error (I get it when using bzr qlog): bzr: ERROR: Failed to verify GPG signature data with error "Invalid crypto engine"