[08:53] <Saviq> morning
[08:54] <Saviq> tsdgeos, question: now that we have delegateCreationBegin/End, do we actually gain much by filtering the actual model instead of just clipping it?
[08:54] <Saviq> "it" being the view
[08:57] <tsdgeos> Saviq: you save having to do the math of how tall two rows are
[08:57] <tsdgeos> and also delegateCreationBegin/End still do buffering outside the delegateCreationBegin/End area
[08:57] <tsdgeos> so you'd end up with a row more
[08:58] <Saviq> tsdgeos, but I do have do to the math for how tall the full view is going to be ;)
[08:58] <tsdgeos> but for the VerticalJournal we'll need clip
[08:58] <tsdgeos> since they want "half" items there
[08:58] <Saviq> tsdgeos, and then do the proxying with the LimitProxy
[08:59] <tsdgeos> yeah haven't thought about it but it's a possibility yeah
[08:59] <Saviq> tsdgeos, yeah, for VJournal we'll need to clip - and we'd need to calculate how many items to show anyway, which would be pretty tricky, too
[08:59] <Saviq> tsdgeos, if we wanted to filter, that is
[09:00] <tsdgeos> trueth
[09:00] <tsdgeos> Saviq: can we get a test for making sure no like is longer than 120 chars? that'd way i'd hate the rule and not the messenger
[09:00] <tsdgeos> s/like/line
[09:00] <Saviq> tsdgeos, you mean dandrader? ;D
[09:02] <tsdgeos> i mean the messenger :)
[09:04] <Saviq> tsdgeos, I'm not sure - we could, of course, but did we ever actually agree to impose that limit...
[09:06] <Saviq> tsdgeos, would you have time to review https://code.launchpad.net/~unity-team/unity8/unity-scope-tool/+merge/199831 ?
[09:09] <tsdgeos> Saviq: sure
[09:10] <Saviq> tsdgeos, thanks
[09:23] <Saviq> tsdgeos, does the fact that PathView is always looped feel weird to you, too? do you know if there's any reason (like it being difficult otherwise) to not allow disabling it via a property or something?
[09:27] <tsdgeos> Saviq: yeah i see it's a bit weird, but haven't looked at it in detail so no idea if it'd be hard to fix or not
[09:28] <Saviq> tsdgeos, ok thanks
[09:28]  * Saviq just looked at Carousel.qml and longed for using a PathView there ;P
[09:29] <tsdgeos> yeah :D
[10:01] <Saviq> tsdgeos, is GenericName required at all?
[10:01] <tsdgeos> Saviq: nope
[10:01] <tsdgeos> http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html
[10:01] <Saviq> tsdgeos, dropping, it doesn't make sense
[10:02] <Saviq> tsdgeos, done
[10:04] <tsdgeos> Saviq: do we care for i18n of the unity-scope-tool ?
[10:04] <Saviq> tsdgeos, hmm we should - domain not set, is it?
[10:05] <Saviq> tsdgeos, or no i18n at all is there...
[10:05] <tsdgeos> Saviq: we are not calling i18n at all no
[10:06] <tsdgeos> that's what i was asking
[10:06] <tsdgeos> should we
[10:06] <tsdgeos> and if we should
[10:06] <tsdgeos> should we extract to the same .pot or to a different one
[10:06] <tsdgeos> my vote is for yes and different
[10:06] <Saviq> tsdgeos, yeah, that's what I was thinking, which means we need a separate qml dir for it
[10:06] <tsdgeos> but that's just me, i can understand if we say "dev tool, learn english"
[10:07] <Saviq> tsdgeos, I think let's go for english now, as it's not trivial to have a separate .po*
[10:07] <Saviq> and wouldn't like to "pollute" the unity8 domain
[10:09] <Saviq> and we can always add it later
[10:14] <tsdgeos> ok
[10:14] <tsdgeos> the time test fails here btw
[10:14] <tsdgeos> is it locale dependent?
[10:14] <tsdgeos>    Actual   (formatter.timeString()): 03-01-2014 11:05
[10:14] <tsdgeos>    Expected (time.toString("dd-MM-yyyy hh:mmAP")): 03-01-2014 11:05AM
[10:16] <Saviq> tsdgeos, yes it is
[10:16] <Saviq> tsdgeos, should pass under LANG=en_US.UTF-8
[10:17] <tsdgeos> can we force that in the make test step?
[10:17] <Saviq> tsdgeos, we should, yes
[10:22] <Cimi> when should (if it) input fall through? https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1257312
[10:23] <Saviq> Cimi, never
[10:23] <Saviq> Cimi, the bubble should be input-opaque, basically
[10:23] <tsdgeos> Saviq: i'd go with http://paste.ubuntu.com/6683685/ but if you don't agree that's fine :D
[10:24] <Cimi> Saviq, and on desktop?
[10:25] <Saviq> Cimi, we don't really support that use case yet (it doesn't blur / go transparent)
[10:25] <Saviq> tsdgeos, that's copy/paste ;)
[10:25] <Saviq> tsdgeos, from main.cpp
[10:25] <Saviq> tsdgeos, but yeah, let's
[10:26] <Saviq> tsdgeos, fixed
[10:27] <tsdgeos> Saviq: i'm getting lots of "<Unknown File>: SyntaxError: Unexpected token u"
[10:28] <tsdgeos> when running the tool
[10:28] <tsdgeos> any idea where that comes from
[10:28] <tsdgeos> ?
[10:28] <Saviq> tsdgeos, JSON parsing
[10:30] <tsdgeos> so which json is wrong?
[10:30] <Saviq> tsdgeos, none should be wrong, maybe the overridden one?
[10:31] <tsdgeos> do i have a too old unity-scopes-shell?
[10:31] <Saviq> tsdgeos, possibly
[10:31] <Saviq> tsdgeos, try running under UNITY_FORCE_NEW_SCOPES=1
[10:32] <mhr3> i was getting that error too
[10:32] <mhr3> always wondered where is it from :)
[10:32] <tsdgeos> it gets very unhappy then
[10:32] <Cimi> https://code.launchpad.net/~cimi/unity8/fix-1257312/+merge/200385
[10:32] <tsdgeos> Saviq: http://paste.ubuntu.com/6683708/
[10:32] <Saviq> tsdgeos, yeah, you don't have any scope
[10:33] <Saviq> tsdgeos, you need the onlinemusic scope from ppa:ubuntu-unity/demo-stuff
[10:33] <Saviq> tsdgeos, sorry about missing that detail :)
[10:33] <mhr3> you can also use the awesome --scope-dir param
[10:34] <Saviq> mhr3, assuming you build it somewhere locally, that is?
[10:34] <mhr3> right
[10:34] <mhr3> a built checkout of lp:unity-scopes-api would do
[10:35] <Saviq> mhr3, is "overrideCategoryJson" available anywhere already?
[10:35] <Saviq> mhr3, as in, in a package?
[10:35] <tsdgeos> Saviq: mhr3: so i need ppa:ubuntu-unity/demo-stuff or lp:unity-scopes-api or both?
[10:35] <mhr3> Saviq, you approved it yesterday, so should be in demo-stuff
[10:35] <Saviq> tsdgeos, just the ppa should be enough, /me checks
[10:36] <mhr3> yep, ppa only should suffice
[10:36] <Saviq> somehow I didn't get the package :/
[10:36] <tsdgeos> is ppa:ubuntu-unity/demo-stuf the correct name?
[10:37] <tsdgeos> add-apt-repository complaiined
[10:37] <mhr3> Saviq, oh, i did some renames, it's now considered older than what was there
[10:37] <mhr3> Saviq, so just force reinstall
[10:37] <Saviq> mhr3, yup, see that
[10:37] <Saviq> tsdgeos, +f
[10:37] <Saviq> tsdgeos, but unity-team
[10:37] <tsdgeos> i had the f there
[10:37] <tsdgeos> :D
[10:37] <Saviq> tsdgeos, ppa:unity-team/demo-stuff, sorry
[10:38] <tsdgeos> that worked
[10:38] <tsdgeos> hmmmm
[10:38] <tsdgeos> Saviq: apt-get tells me i already had unity-scope-onlinemusic installed
[10:39] <mhr3> tsdgeos, the new one?
[10:39] <Saviq> tsdgeos, yes, different version
[10:39] <tsdgeos> so how do i install the new one?
[10:40] <mhr3> tsdgeos, apt-cache policy unity-scope-onlinemusic?
[10:41] <Saviq> tsdgeos, 0.1+14.04.20131129.1~bzr59-0ubuntu1~ubuntu14.04.1 is there in the ppa, is higher version than in archive
[10:41] <tsdgeos> i guess i needed an apt-get update...
[10:41] <tsdgeos> :D
[10:41] <mhr3> lol
[10:41] <Saviq> tsdgeos, that helps, yes
[10:41] <Saviq> mhr3, why do we need the popup for overriding the category?
[10:42] <mhr3> Saviq, cause i wanted "apply" button :)
[10:42] <Saviq> mhr3, we can have the apply button without the popup ;)
[10:42] <mhr3> Saviq, also, you get more real estate :)
[10:42] <Saviq> mhr3, yeah, but then should we maybe drop the one from the side bar altogether
[10:43] <Saviq> mhr3, as it's confusing
[10:43] <mhr3> Saviq, maybe, i considered that a view-only
[10:43] <Saviq> mhr3, should've made it so ;D
[10:43] <mhr3> though couldn't find editable property
[10:43] <mhr3> not that i looked for it too much
[10:44] <Saviq> mhr3, activeFocusOnPress: false should work
[10:45] <Saviq> mhr3, or well... file:///usr/share/ubuntu-ui-toolkit/doc/html/qml-ubuntu-components0-textarea.html#readOnly-prop
[10:45] <mhr3> yea, i imagined that it'll be very accurate naming :P
[10:47] <Saviq> uh, still displays the cursor
[10:50] <tsdgeos> Saviq: that didn't help at all
[10:50] <tsdgeos> Saviq: http://paste.ubuntu.com/6683774/
[10:51] <Saviq> tsdgeos, `status scope-registry`?
[10:51] <mhr3> Saviq, btw why are the card titles so broken? the antialiasing seems to be majorly broken
[10:51] <mhr3> tsdgeos, `restart scope-registry`
[10:52] <Saviq> mhr3, because it's not using cards, but the old UI
[10:52] <Saviq> mhr3, merge into new-scopes and try there?
[10:52] <mhr3> Saviq, nope, it's using cards for me
[10:52] <mhr3> it's just terrible on the white background
[10:53] <mhr3> oh wait
[10:53] <mhr3> no you're right
[10:53] <mhr3> wrong branch
[10:54] <tsdgeos> Saviq: ok, the restart worked
[10:54] <mhr3> Saviq, still bad on category titles though
[10:54] <Saviq> mhr3, yeah, probably a shadow or some such
[10:56] <Saviq> mhr3,             style: Text.Raised
[10:56] <Saviq>             styleColor: "black"
[10:57] <Saviq> tsdgeos, mhr3, bug #1265766
[10:57] <Saviq> please confirm
[10:58] <mhr3> done, thx
[10:59] <Saviq> tsdgeos, you still won't be able to override the categories
[10:59] <tsdgeos> tbh i don't think that's a bug
[10:59] <Saviq> tsdgeos, not unless you rebase onto lp:~unity-team/unity8/new-scopes
[10:59] <tsdgeos> if you don't want to get the focus, disable it :D
[11:00] <Saviq> tsdgeos, should default to false if read only, IMO
[11:03] <mhr3> Saviq, i guess the "black" should be a global const
[11:03] <mhr3> it's on too many places
[11:03] <Saviq> mhr3, true
[11:03] <Saviq> mhr3, should be part of the palette
[11:04] <mhr3> didn't know there's such a thing, but sure :)
[11:05] <Saviq> mhr3, file:///usr/share/ubuntu-ui-toolkit/doc/html/qml-ubuntu-components-themes0-palettevalues.html
[11:05] <Saviq> mhr3, used like so file:///usr/share/ubuntu-ui-toolkit/doc/html/qml-ubuntu-components-themes0-palette.html
[11:06]  * Saviq finds it funny that he can link to a file on his own file drive ;)
[11:06] <Saviq> s/file/hard/
[11:06] <mhr3> Saviq, though shell palette and apps palette should be different, no?
[11:06] <Saviq> mhr3, it is
[11:07] <Saviq> mhr3, they're per-theme
[11:07] <mhr3> ah, ok
[11:08] <mhr3> heh, i noticed just now that these were file:/// urls
[11:08] <tsdgeos> the repeater thing for the textarea is a bit weird
[11:08] <mhr3> weird, but works :)
[11:09] <mhr3> and it wasn't easy to get it into that state :P
[11:14] <Saviq> mhr3, h4x0red you ;D
[11:15] <mhr3> Saviq, grrr, i knew unity8 is just a trojan!
[11:15] <Saviq> mhr3, it's unity7 that spies on us all the time!
[11:20] <mhr3> ah, so you're saying we just took it further? :)
[11:20] <mhr3> more "features" :)
[11:20] <tsdgeos> Saviq: mhr3: ok, added a final comment and my approval, if you want i can top approve too
[11:20] <Saviq> tsdgeos, thanks!
[11:22] <Saviq> tsdgeos, mhr3, +1 on Q_INVOKABLE data() instead of the repeater
[11:24] <mhr3> i'd prefer QVariantMap get(int index) then
[11:31] <Saviq> mhr3, that's something that we try not to do
[11:31] <Saviq> mhr3, to not encourage getting the whole dataset unnecessarily
[11:32] <Saviq> Cimi, you should've re-submitted Mirco's merge proposal, not do a new one
[11:32] <Saviq> Cimi, /me does
[11:34] <Saviq> Cimi, and next time please just branch from the branch in question and commit on top of it, to not lose the history
[11:49] <mhr3> Saviq, but it's just one row of the dataset
[11:49] <Saviq> mhr3, that's still more than just one role
[11:50] <mhr3> one role is ENOTENOUGH :P
[11:50] <Cimi> Saviq, I redid the branch
[11:50] <Saviq> Cimi, thanks
[11:50] <Cimi> Saviq, I did not use his
[11:50] <Saviq> Cimi, yes I know, that's what I said - you should have used his, merge trunk, do your changes
[11:50] <Cimi> Saviq, there were conflicts
[11:50] <Saviq> Cimi, so that his commit is still there in the history
[11:51] <Saviq> Cimi, not important, just in general we should try and maintain the history
[12:13] <Cimi> Saviq, https://code.launchpad.net/~unity-team/unity8/carousel-shader/+merge/196942 ?
[12:13] <Saviq> Cimi, animation still missing?
[12:14] <Cimi> oh ok
[12:36] <tsdgeos> dandrader|lunch: i think i've addressed all your concerns
[12:36] <tsdgeos> dandrader|lunch: can you please recheck?
[14:04] <Saviq> mhr3, back to data() vs. get() etc., maybe it'd be enough if picked the value from the option selector?
[14:04] <Saviq>  mhr3, by adding a property on the selector delegates?
[14:04] <Saviq>  or properties, for that matter
[14:06] <Saviq> mhr3, if the selector doesn't give you access to the selected item, just go 'onSelectedChanged: categorySelector.selectedItem = categoryDelegate' or so
[14:07] <Zhenech> what's to do to get a package from "proposed" to "release" in trusty?
[14:14] <tsdgeos> Zhenech: i'd say probably #ubuntu-devel is a better channel to ask that question
[14:14] <Zhenech> ups, i thoght this is actually -motu
[14:33] <tsdgeos> Saviq: standup?
[14:33] <tsdgeos> Cimi: ↑
[14:33] <Saviq> tsdgeos, rigt
[14:38] <Saviq> mhr3, tsdgeos I just pushed a simplified "get data from the model" approach to the scope tool
[14:40] <tsdgeos> cool
[14:40] <tsdgeos> let me see
[14:46] <mhr3> Saviq, aaah, clever
[14:47] <Saviq> mhr3, ;)
[14:47] <Saviq> mhr3, offtopic, got a SA power adapter?
[14:48] <Saviq> if not, it's about time
[14:48] <mhr3> Saviq, that reminds me, what SA power adapters look like?
[14:48] <Saviq> nothing universal will work
[14:48] <Saviq> mhr3, https://www.google.com/search?q=south+africa+plug&client=ubuntu&hs=A0m&channel=fs&tbm=isch&source=iu&imgil=ROKN542cw-aGfM%253A%253Bhttps%253A%252F%252Fencrypted-tbn1.gstatic.com%252Fimages%253Fq%253Dtbn%253AANd9GcQrjgzIyU1wIrARhw2YsoPCvNW8ktNhNOVJfn_MfQvpFxUuxkf4%253B346%253B346%253Bho-Yz_gQZBODQM%253Bhttp%25253A%25252F%25252Fwww.power-cord.org%25252Fsouth-africa-plug.html&sa=X&ei=rs3GUsW4O-m04ASQ0IGIBQ&ved=0CDIQ9QEwAg&biw=1219&bih=781#facrc=_&i
[14:48] <Saviq> mgdii=_&imgrc=ROKN542cw-aGfM%3A%3Bho-Yz_gQZBODQM%3Bhttp%253A%252F%252Fwww.power-cord.org%252Fuploadfile%252Fsouth-africa-sabs-israel-power-cords-n02-1439.jpg%3Bhttp%253A%252F%252Fwww.power-cord.org%252Fsouth-africa-plug.html%3B346%3B346
[14:48] <Saviq> yikes..
[14:48] <mhr3> eh
[14:48] <Saviq> mhr3, it's a huge 3-prong one
[14:48] <mhr3> Saviq, think dednick will have one, will try to borrow from him
[14:48] <Saviq> mhr3, right, makes sense
[15:09] <mardy> larsu: hi! Do you have a minute for a question about indicator-messages?
[15:11] <tsdgeos> Saviq: that looks more reasonable :-)
[15:11] <tsdgeos> mhr3: Saviq: so want me to top-approve?
[15:11] <mhr3> tsdgeos, fine by me
[15:12] <mardy> tedg: or do you (see 4 lines above ^)?
[15:14] <mardy> charles: or you ^ :-)
[15:15] <tedg> mardy, What's up?
[15:16] <mardy> tedg: I'm having a look at bug 1130084
[15:16] <mardy> tedg: I'm trying to understand how things work
[15:17] <mardy> tedg: so, it seems that indicator-messages fires a DBus signal (StatusChanged), but there's no one listening to it
[15:17] <tedg> mardy, For the most part we just try to reflect what telepathy has as it's state.
[15:17] <tedg> mardy, It seems to me that telepathy should be saving that state and restoring it.
[15:17] <mardy> tedg: because telepathy-indicator.desktop has X-GNOME-Autostart-Delay=15
[15:18] <mardy> tedg: is there a way for telepathy-indicator to get the current status from messages-indicator? I tried inspecting the latter with d-feet, but I couldn't find any DBus properties
[15:20] <tedg> mardy, It could just look at the status of the action.  But, really, indicator-messages shouldn't be driving the state.  It should be representing the state that telepathy has.
[15:21] <tedg> mardy, So telepathy-indicator should look to telepathy to find out what the state is.  And request and update based on that.
[15:21] <mardy> tedg: ah, then I understood it the other way round
[15:23] <tedg> mardy, For debugging you can get the state with: $ gdbus call --session --dest com.canonical.indicator.messages --object-path /com/canonical/indicator/messages --method org.gtk.Actions.Describe status
[15:23] <mardy> tedg: so, when the user changes the presence status from the indicator, a signal is emitted, and any presence-capable app should try to match that status and save it in its config?
[15:24] <tedg> mardy, Correct, we don't require a save, but that makes sense to me.
[15:25] <mardy> tedg: I see... I'll try to fix telepathy-indicator then.
[15:25] <mardy> tedg: and do you know the reason of that 15 seconds delay? Isn't that a bit too much? (or is msecs?)
[15:25] <tedg> mardy, Why not fix telepathy?
[15:26] <tedg> Seems this should be a mission-control feature more than a bridge feature.
[15:26] <tedg> mardy, Not sure, I'm guessing it was a boot optimization thing.  kenvandine might know.
[15:27] <mardy> tedg: I don't think so, mission-control probably doesn't even start by default.
[15:27] <tedg> mardy, We should really switching it an upstart job that is "start on started indicator-messages"
[15:27] <kenvandine> it was for boot speed
[15:27] <kenvandine> we delayed a bunch of things like that
[15:27] <kenvandine> to let stuff settle more
[15:28] <mardy> tedg: I disagree; mission-control doesn't save its presence status, and starting it by default would be annoying for people who don't use it
[15:28] <tedg> mardy, Hmm, seems you're right.  IMHO, kinda silly, but eh, okay.
[15:28] <tedg> mardy, It shuts down if there are no accounts.  So really it'd just check to see if it's configured and die.
[15:28] <tedg> mardy, I don't think that'd be too annoying.
[15:29] <mardy> tedg: I'd actually like if instead of reacting to a StatusChanged signal these bridges could register itself as DBus activatable, and indicator messages invoke a method on them when needed
[15:30] <tedg> mardy, If they're connected they need to be running, so I'm not sure dbus activatable is the right choice.
[15:30] <tedg> mardy, For instance you wouldn't want to start up XChat just to see if it wanted to change the status.
[15:30] <tedg> mardy, When it's only a bridge, that makes sense.  But I'd rather have bridge be the minority case.
[15:30] <mardy> tedg: exactly, I would like them *not* to be running by default, but started on demand, if needed
[15:31] <tedg> mardy, How would we know if they're needed?
[15:32] <mardy> tedg: we always invoke SetStatus(...) on them, when the user changes the status from the menu; if they are running, they'll react to it (and maybe quit if the status is "offline"), if they aren't they'll be started
[15:32] <mardy> tedg: compare it to the current situation, where the *need* to be running
[15:33] <mardy> all the time
[15:33] <mardy> s/the/they/
[15:33] <tedg> mardy, If they're connected to an IM network, they need to be running to keep the socket to the network open.
[15:33] <mardy> tedg: yes. But if the status is "offline", it would be nice if they quit
[15:34] <tedg> mardy, And you want us to restart everything possible if you set to "Available" ?
[15:34] <mardy> tedg: D-Bus doesn't restart already running services
[15:35] <tedg> mardy, I mean, I have IM clients installed that I'm not using.  They shouldn't start.
[15:36] <mardy> tedg: mmm... I'm starting to see your point
[15:36] <mardy> tedg: I was assuming that this indicator-messages was written especially for things like telepathy, but now I realize that maybe telepathy is the weird one. Right?
[15:36] <tedg> Interestingly someone could set up an upstart job to start when it sees the DBus signal.
[15:37] <tedg> I think that telepathy kinda is.  Though, frankly it's our biggest user.
[15:37] <mardy> tedg: I'm thinking about the telepathy-indicator bridge; my point is that if the status is "offline", it should not be running
[15:38] <tedg> And perhaps that's the special case.  We should start only those special cases when going to an active status.
[15:39] <mardy> tedg: what about this: we keep everything as it is, but we add a way for presence-aware apps to register themselves, and get their SetStatus() DBus method called at the same time as StatusChanged is emitted
[15:39] <tedg> I wonder if the real solution here is just to bless telepathy is the ruler of everything status, and tell others to integrate there.
[15:40] <mardy> tedg: and we make telepathy be one (the only one?) of the implementors of this interface
[15:40] <tedg> I'd say that we destroy the interface and call telepathy directly.
[15:41] <mardy> tedg: +1
[15:42] <tedg> I think that I need to think about the implications there a bit... but, it doesn't seem crazy right now :-)
[15:43] <mardy> tedg: on the practical side, I think I can quickly fix bug 1130084 in telepathy-indicator, without much effort; for the rest, maybe I can file a wishlist bug, and let's see who gets the time to do it?
[15:49] <tedg> mardy, Makes sense.  I think charles is the one scheduled to open up indicator-messages next.
[15:49] <tedg> Though that's for greeter work.
[15:51] <mardy> tedg: OK, thanks
[15:51] <kenvandine> mardy, how do you plan to store the last presence?
[15:52] <kenvandine> it's annoyed me for ages, i had considered storing that in gsettings but someone convinced me not to
[15:52] <mardy> kenvandine: not sure. Just an .ini file, unless telepathy-indicator is already using other stuff (DConf?)
[15:52]  * kenvandine wonders if accountsservice has anything for that
[15:52] <Saviq> kenvandine, sure, you can story any property you want in accountsservice
[15:52] <kenvandine> i really want a global presence
[15:53] <mardy> kenvandine: if telepathy-indicator is the one who stores the settings and reads it, I think it can be a file private to it
[15:53] <kenvandine> we weren't really using accountsservice when i was looking into this
[15:53] <tedg> I think that you want to store the user selected status, not generally the status in GSettings.
[15:54] <tedg> The reason is that you don't want to store when the screensaver sets you to away.
[15:54] <kenvandine> good point
[15:54] <tedg> Where in account service you'd want to have the current status.
[15:55] <kenvandine> what does gnome-shell and kde do?
[17:09] <Cimi> Saviq, re-run carousel shader, but I only see mocks on the desktop, no icons or so... what change?
[18:26] <elopio> Hello, anybody around for a review?
[18:26] <elopio> https://code.launchpad.net/~elopio/unity8/open_scope/+merge/200426
[18:33] <elopio> Cimi: ping? ^
[19:42] <larsu> mardy: sorry I was out before. Are you still around?
[19:43] <mardy> larsu: hi! No problem, I already solved the issue with tedg
[19:43] <larsu> mardy: awesome :) And happy new year!
[19:44] <mardy> larsu: thanks, same to you!