[06:35] <kvalo> morning
[06:44] <Omega> night :)
[06:48] <kvalo> :)
[07:57] <MacSlow> greetings everybody!
[07:58] <kvalo> hello MacSlow
[07:59] <MacSlow> hey kvalo, kamstrup
[08:11] <didrocks> good morning
[08:18] <kvalo> kamstrup: morning. I'm sure you have missed my merge requests ;) so here's a new one: https://code.launchpad.net/~kvalo/indicator-network/libconnman-vala/+merge/47366
[08:19] <kvalo> kamstrup: this one was so strange, I didn't get it: http://bazaar.launchpad.net/~kvalo/indicator-network/libconnman-vala/revision/153
[08:28] <kamstrup> kvalo: is it |just| the cheader_filename that you've changed in the .vapi?
[08:29] <kamstrup> kvalo: because in that case it could make sense to a 'sed' invocation in your Makefile.am to get the Connman-1.0.vapi to be purely autogenerated
[08:36] <kamstrup> kvalo: needs fixing
[08:41] <kvalo> kamstrup: the regexp wouldn't be simple, because there are two different filenames
[08:42] <kamstrup> kvalo: ah, bugger
[08:42] <kvalo> yeah, it really sucks
[08:42] <kamstrup> kvalo: although I guess you could fix that by making one super header that includes the two, no?
[08:43] <kvalo> kamstrup: can you check if you have libreadline-dev installed? I'm guessing configure check doesn't fail if it's missing
[08:43] <kamstrup> kvalo: and generally I push for single header includes everywhere anyway. Including discrete headers is a path of pain for consumers and maintainers alike
[08:44] <kvalo> kamstrup: so you are saying that I should have libconnman.h which will contain all classes?
[08:44] <kvalo> ah, it will just include all the class .h files
[08:44] <kvalo> makes a lot of sense
[08:44] <kamstrup> kvalo: a libconnman.h that just includes manager.h and service.h or whatever you need
[08:44] <kamstrup> kvalo: in fact for all my public
[08:44] <kamstrup> kvalo: (damn return key!)
[08:45] <kamstrup> kvalo: in fact for all my public libs i *force* this and raise a compile time error if you try to include one of the subheaders
[08:46] <kamstrup> kvalo: like http://bazaar.launchpad.net/~libzeitgeist-developers/libzeitgeist/trunk/view/head:/src/zeitgeist-monitor.h#L21
[08:46] <kamstrup> kvalo: but of course this is not as important for an internal lib
[08:47] <kvalo> I'll add it anyway
[08:47] <kamstrup> this gives absolute freedom for me to restructure the internal source layout, which is otherwise impossible
[08:48] <kvalo> kamstrup: thanks for the tips
[08:50] <kvalo> yeah, configure doesn't fail if readline is missing
[08:50]  * kvalo starts reading the autoconf bible
[08:54] <kamstrup> kvalo: meh, readline doesn't have pkg-config integration...
[08:54] <kamstrup> kvalo: you can just do: echo '#include <readline/readline.hads>' | gcc -E - > /dev/null 2>&1
[08:55] <kamstrup> kvalo: in configure.ac and check $? == "0"
[08:55] <kvalo> kamstrup: I'm using AC_CHECK_LIB already, I was just missing the error case
[08:55] <kamstrup> kvalo: ah, ok
[08:55] <kvalo> kamstrup: but yeah, readline is _old_.
[08:55] <kamstrup> kvalo: but it works :-)
[08:56] <kvalo> sure does
[09:03] <kvalo> kamstrup: just to keep merge requests simple, I will create a new branch for the automatic vapi generation
[09:03] <kvalo> kamstrup: ok?
[09:04] <kamstrup> kvalo: suer
[09:04] <kamstrup> sure
[09:32] <kamstrup> njpatel: !
[09:32] <njpatel> kamstrup, !
[09:32] <kamstrup> njpatel: I was thinking...
[09:33] <njpatel> uh-oh
[09:33] <kamstrup> njpatel: why is the group_model per PlaceRendererInfo and not just shared globally across a PlaceInfo (like the sections_model already is)...
[09:33] <kamstrup> njpatel: considering https://wiki.ubuntu.com/Unity/Places
[09:34] <kamstrup> njpatel: sorry, the correct terminology would be RendererInfo and PlaceEntryInfo respectively in the above
[09:34] <njpatel> kamstrup, I think it's because different renderers might have different groups, where sections would remain constant across the place entry
[09:34] <kamstrup> njpatel: at least it makes for some oddities in the place daemons
[09:34] <njpatel> oh, wait, I se what you mean
[09:35] <njpatel> kamstrup, I guess it could be global
[09:35] <kamstrup> njpatel: indeed, and you can still have different renderes even if you use the same label for the group, that would just be two entries in the group model with the same labeæ
[09:35] <njpatel> right
[09:36] <kamstrup> njpatel: so I think it's a taad more consistent, and it's one less DeeSharedModel on startup (they are not entirely cheap)
[09:36] <kamstrup> ((because of the dbus interactions)
[09:36] <njpatel> kamstrup, this isn't something we need to change, though, right? I mean I've just come out of doing this and if you make me go back to gdbus I might kill you
[09:36] <njpatel> oh, you do want to change
[09:36]  * njpatel books tickets to Denmark
[09:36] <kamstrup> njpatel: i don't have to
[09:37] <kamstrup> njpatel: it's because I am sitting here adding the Control Center stuff to the apps place
[09:37] <njpatel> kamstrup, I'd say leave it for now, we've got enough to do for A2. Maybe once the places stuff has settled down next week?
[09:37] <kamstrup> njpatel: and the current spec makes this rather ugly in my code
[09:37] <kamstrup> njpatel: ok, I'll put it in the gdoc of pending changes
[09:37] <njpatel> thanks
[09:42] <kvalo> kamstrup: I updated now https://code.launchpad.net/~kvalo/indicator-network/libconnman-vala/+merge/47366
[09:42] <kamstrup> kvalo: ok, on it
[09:44] <kvalo> kamstrup: thanks
[09:52] <rodrigo_> dbarth_, a11y call now?
[09:53] <kamstrup> kvalo: approved, with a small request...
[09:54] <kvalo> kamstrup: hey, I can't say no to you ;)
[10:13] <rodrigo_> API, dbarth_: a11 weekly call now?
[10:13] <rodrigo_> hey aruiz
[10:13] <aruiz> hey rodrigo_ !
[10:13] <aruiz> :-)
[10:25] <rodrigo_> API, hmm, about your last comment in my branch, the PanelViewAccessible has several children, not only 1 (the layout), as shown on accercizer
[10:25] <rodrigo_> API, not sure what you mean?
[10:27] <API> rodrigo_, it has several because you are exposing layout content
[10:27] <rodrigo_> API, right, and you'd prefer to just expose the layout as the only child?
[10:27] <API> no
[10:27] <API> please read again
[10:27] <API> my last review
[10:28] <API> your way to implement that could be also valid
[10:28] <API> but, there is any reason to do that?
[10:28] <API> I mean that the normal is the other way
[10:28] <API> expose the only child
[10:28] <API> becase after all
[10:28] <API> is the only child of the panel
[10:28] <API> your way is also valid
[10:28] <rodrigo_> hmm, but what do we need the layout for?
[10:28] <API> but, imho, it should be a reason to do that in this way
[10:29] <API> and why repeat the code to expose the children of a layout?
[10:29] <API> we have that code on nuxlayoutaccessible
[10:29] <API> so it is valid for any layout used
[10:29] <rodrigo_> hmm, ok
[10:30] <rodrigo_> so, I just change it to return 1 child (the layout) then, right?
[10:32] <API> well, unless you find a good reason to do that in the other way ;)
[10:32] <API> yes,
[10:32] <API> you can take basewindow as reference
[10:32] <kvalo> kamstrup: I want to create a uber test script/makefile target which would run all possible tests there are and print an "OK!" banner if there are no errors. would makefile target "allchecks" or similar be the best solution?
[10:32] <rodrigo_> no, just didn't think we needed the full real hierarchy, but if that's how everything is done, I'll change it
[10:32] <rodrigo_> so yeah, don't have a good argument to convince you :-D
[10:33] <kamstrup> kvalo: just stick this in your makefile for s in test_foo test_bar test_baz; do echo $s OK; done
[10:34] <kamstrup> kvalo: is everything using the gtester framework?
[10:34] <kvalo> kamstrup: most are, but I want to also run distcheck
[10:35] <kamstrup> kvalo: check how I do it lp:libunity. You need a Makefile.decl copy pasted to your source root from there
[10:35] <kamstrup> kvalo: and then include it in your test makefiles
[10:35] <kvalo> kamstrup: thanks, I'll check it
[10:47] <smspillaz> gord: could you file a bug saying that we need multimonitor support in the switcher and staticswitcher plugins so I don't forget :)
[11:02] <gord> smspillaz, not right now, if i remember when i'm less busy though :)
[11:03] <smspillaz> :p
[11:25] <ronoc> njpatel, a serializedstring gvariant would look like something like this no -> "(s)", "thing"
[11:25] <ronoc> for the gsettings command line tool
[11:29] <njpatel> ronoc, erm, no idea dude. kamstrup ? ^
[11:30] <kamstrup> ronoc, njpatel: ehhh, probably? What does "serialized" mean here?
[11:32] <ronoc> kamstrup, njpatel from the docs of the gsettings command line tool the set command takes key and then value, "The value is specified as a serialised GVariant "
[11:33] <kamstrup> ronoc: it probably refers to the format used by g_variant_print()/g_variant_parse()
[11:33] <ronoc> ah yes
[11:33] <ronoc> thx guys
[11:39] <kamstrup> ronoc: so what I see here is that a variant created with g_variant_new ("s", "Hello") prints as ('Hello',)
[11:41] <ronoc> kamstrup, tried that already, doesn't like it
[11:41] <kamstrup> ronoc: he - then I'm at a loss
[11:42] <ronoc> kamstrup, no worries - just trying to helpful on a bug report ...
[11:43] <kamstrup> ronoc: look at the format from a get command - the docs say it's the same
[11:45] <kamstrup> ronoc: gsettings get org.gnome.desktop.default-applications.terminal exec
[11:45] <kamstrup> ronoc: so it's a 'single quoted string'
[11:46] <ronoc> kamstrup, the format of the value in my hash is an array of strings
[11:46] <ronoc> so I have been trying gsettings set com.canonical.indicators.sound blacklisted-media-players @as ["rhythmbox"]
[11:46] <ronoc> since get returns
[11:47] <ronoc> @as []
[11:47] <kamstrup> ronoc: ['foo', 'bar']
[11:48] <kaleo> hello
[11:48] <kamstrup> kamstrup: gsettings get com.canonical.Unity.Launcher favorites
[11:48] <kamstrup> kaleo: Where's the original Kaleo?!
[11:48] <Kaleo> :)
[11:48]  * Kaleo is me 
[11:48] <kamstrup> Kaleo: oh, hi Kaleo, you here too?
[11:48] <kamstrup> ;-)
[11:49] <Kaleo> after a good night of rest yes
[11:49] <kamstrup> hehe
[11:49] <ronoc> kamstrup, still not working, a key error is now the problem even though it has no problem fetching
[11:49] <ronoc> weird
[11:49] <ronoc> will come back to it later
[11:50] <multiplatinum> ivanka,  remember me? (last week xD)
[11:51] <ronoc> kamstrup, got it
[11:52] <ronoc> gsettings set com.canonical.indicators.sound blacklisted-media-players "['rhythmbox']"
[11:52] <kamstrup> ronoc: right, looks sane
[12:25] <kvalo> kamstrup: actually I can't generate the vapi automatically. I just remembered that I did other manual changes as well
[12:26] <kvalo> kamstrup: I think I just leave as it is for now and revisit then the api is stable, and hopefully tools are more stable
[12:26] <kamstrup> kvalo: right, no worries
[12:38] <didrocks> seb128: do you still have the issue with alt + mouseclick not dragging your window?
[12:43] <seb128> didrocks, still get it
[12:43] <seb128> you don't?
[12:43] <seb128> using alt-click-dnd doesn't move anything there
[12:44] <didrocks> seb128: no, I never had it
[12:44] <didrocks> seb128: can you try this (maybe it's a perf issue that some people have): ccsm -> move plugin -> opacity back to 100%
[12:44] <didrocks> (and check that alt + button 1 is set as well)
[12:45] <seb128> didrocks, it's not happening in a guest session, just checked
[12:45] <seb128> so don't bother
[12:45] <didrocks> seb128: ok, something weird again in the session :)
[12:47] <seb128> hate compiz, it's still crashing every second ccsm run
[12:48] <didrocks> seb128: do you enable/disable pluginis?
[12:48] <seb128> no
[12:48] <didrocks> plugins* even
[12:48] <seb128> just run ccsm
[12:48] <didrocks> oh, weird, I didn't with that
[12:48] <seb128> every second run compiz crashes
[12:48] <seb128> ok
[12:49] <seb128> I can move the dialogs which are not focused
[12:49] <didrocks> I have some random crashes though
[12:49] <seb128> that's weird
[12:49] <seb128> like if I've to dialogs on screen I can alt-click and dnd the one which is not focussed
[12:49] <seb128> but not the one which is focussed
[12:49] <didrocks> seb128: maybe related to the new decorator? (just a stupid guess)
[12:49] <didrocks> there is still the older one if you want to give it a try
[12:50] <seb128> didrocks, that fixes it
[12:50] <didrocks> not that stupid then \o/
[12:51] <didrocks> in the guest session, which decorator is running? (should be the unity one still…)
[12:52] <seb128> or not
[12:52] <seb128> didrocks, it seems restarting the decorator just made it work once
[12:52] <seb128> didrocks, I will keep watching for it but don't bother with that for now
[12:52] <didrocks> ok, that's weird :/
[12:52] <seb128> it doesn't happen in my guest session so it's likely a profile thing
[12:52] <seb128> I will try to debug it later
[12:52] <didrocks> seb128: ok, keep my in touch :)
[12:52] <seb128> but I've other tasks I want to get done before
[12:52] <seb128> k
[12:52] <seb128> session restart brb
[12:52] <didrocks> thanks :)
[13:08] <ogra> Kaleo, so (finally) looking into the merge, do you think we could drop some of the depends in u-2d-d-s to recommends ?
[13:08] <ogra> the dependency list is quite long
[13:10] <Kaleo> ogra: hmmm, that's kind of a broad question
[13:10] <Kaleo> ogra: any specific depends you have in mind?
[13:10] <ogra> nautilus looks like a good candidate
[13:11] <ogra> metacity too (since you apparently can also use compiz)
[13:11] <Kaleo> ogra: metacity is a no go
[13:11] <ogra> why ?
[13:11] <Kaleo> ogra: we want to run by default on hardware without hw accelerated OpengGL
[13:11] <Kaleo> -g
[13:11] <didrocks> well, there is custom patch in metacity like the decorator one
[13:11] <ogra> if i can use compiz instead there needs to be an option to uninstall metacity
[13:12] <Kaleo> ogra: and we do not QA on Compiz very much
[13:12] <ogra> Kaleo, by default the unity-2d package will pull in metacity
[13:12] <Kaleo> ogra: so for now it's experimental
[13:12] <Kaleo> ogra: which is normal
[13:12] <Kaleo> a
[13:12] <Kaleo> ah
[13:12] <ogra> we install recommends by default
[13:12] <Kaleo> right
[13:12] <ogra> its just about the optional removing
[13:12] <Kaleo> ogra: I see
[13:13] <ogra> and i can see people using it with pcmanfm or compiz
[13:13] <didrocks> ogra: what do you set in the session file?
[13:13] <didrocks> metacity ?
[13:13] <Kaleo> ogra: to back up a little here our package u-2d-d-s should depends/recommends most of the same things that Unity deps/recommends
[13:13] <Kaleo> didrocks: yes
[13:13] <ogra> probably even with xfce-session if there is nothing that hardcodes gnome-session functions
[13:13] <didrocks> so, the session won't start if someone uninstall metacity
[13:13] <Kaleo> didrocks: good point
[13:13] <ogra> didrocks, no, but you can modify it manually
[13:14] <didrocks> right, but I'm unsure about letting people shooting on their feet :)
[13:14]  * didrocks tries to think how to do that
[13:14] <ogra> well, we will get complaints if we have to hard deps
[13:14] <Kaleo> didrocks: ogra: what package should I look at that contains Unity's session?
[13:14] <didrocks> Kaleo: gnome-session
[13:14] <Kaleo> didrocks: thanks
[13:14] <ogra> i'm fine going with what we have but try to think ahead
[13:15] <didrocks> ogra: maybe gnomewm needs some tweaking
[13:15] <ogra> so things that arent absolutely needed should be removable
[13:15] <didrocks> Kaleo: you need to look at /usr/share/gnome-session/sessions/ubuntu.session
[13:15] <ogra> if we indeed have hardcoded bits that really depend on gnome stuff there is no way for recommends
[13:15] <ogra> but i see for example ubuntu-wallpapers in the deps
[13:16] <didrocks> ogra: strictely speaking, I can only see the decorator patch
[13:16] <ogra> and light-themes
[13:16] <ogra> these seem like recommends candidates
[13:17] <Kaleo> ogra: light-themes does not have to b there at all AFAIK
[13:17] <ogra> we often have people building custom images for unsupported arm HW ...
[13:17] <Kaleo> ogra: so, we have a long list of deps
[13:17] <Kaleo> ogra: it needs cleaning while keeping all existing functionalities
[13:17] <ogra> i just try to think of that guy who wants to run everything xfce and pcmanfm with custom themes
[13:18] <ogra> Kaleo, right, thats why i ask :)
[13:18] <Kaleo> ogra: and we should look into Unity's deps
[13:18] <Kaleo> ogra: and mimick what is done there
[13:18] <ogra> ugh
[13:18] <ogra> they are way bigger than ours :P
[13:18] <Kaleo> ogra: sure
[13:18] <Kaleo> ogra: but for example the indicator-* are recommends for them
[13:18] <Kaleo> http://packages.ubuntu.com/natty/unity
[13:19] <ogra> heh
[13:19] <didrocks> yeah, because without the indicators…
[13:19] <didrocks> and it's only recommends
[13:19] <didrocks> the required bits are:
[13:19] <didrocks> compiz of course
[13:19] <didrocks> unity-common which is internal
[13:20] <didrocks> libglib2.0-bin for the gsettings binary
[13:20] <ogra> the indiocators would have been the bits i wouldnt have made recommends :)
[13:20] <ogra> funny
[13:20] <didrocks> python for some migration script and the unity binary
[13:20] <didrocks> nux-tools for the detection bits
[13:20] <didrocks> unity-asset-pool for the icons
[13:20] <didrocks> ogra: well, if you install unity, you want to have a way to disconnect from your session for instance
[13:21] <didrocks> or you maybe want the clock :)
[13:21] <ogra> right
[13:21] <Kaleo> ogra: http://ietherpad.com/2s0NezImPo
[13:21] <ogra> thats why i mean i wouldnt have made indicators a recommends
[13:21] <Kaleo> ogra: I started putting the plan there
[13:21] <didrocks> ogra: oh, you mean a dep?
[13:22] <Kaleo> ogra: let's figure out the whole changes there, agree on it, and then push it
[13:22] <didrocks> ogra: we have some people who wants to remove the appmenu
[13:22] <ogra> ugh
[13:24] <ogra> Kaleo, wallüpapers and themes should be recommends there
[13:26] <ogra> Kaleo, hmm we could drop wallpapers and themes and move them into the netbook/desktop seeds
[13:26] <ogra> (i think they are in there anyway)
[13:27] <Kaleo> apt-cache rdepends answers part of the question I suppose
[13:27] <didrocks> ogra: they are
[13:27] <ogra> right, lets drop them
[13:27] <Kaleo> didrocks: http://ietherpad.com/2s0NezImPo contains the discussion in a more efficient format
[13:27] <Kaleo> ogra: can you leave them on the document please
[13:27] <ogra> oops
[13:27] <ogra> back
[13:28] <Kaleo> thanks
[13:28] <ogra> what about metacity ?
[13:28] <ogra> if its hardcoded in the session file we indeed need to keep it
[13:29] <ogra> how about gnome-session ? can we use other session managers without breaking ?
[13:31] <Kaleo> ogra: don't forget that this pacakge is meant to install the session in GDM
[13:31] <ogra> and what about the dep on unity ? that should be lowered to the bits we actually need i guess
[13:31] <Kaleo> ogra: that's its purpose
[13:31] <ogra> (unity-common/-asset-pool)
[13:31] <ogra> Kaleo, what if i want to use it with kdm ?
[13:31] <Kaleo> ogra: we don't depend on these
[13:31] <didrocks> right, we need to clean up what's in -common
[13:31] <ogra> Kaleo, right
[13:31] <didrocks> I'll have a look to ensure you have all you need
[13:31] <ogra> Kaleo, we depend on unity though
[13:32] <Kaleo> ogra: not in 2d-default-settings AFAIK
[13:32] <ogra> or am i misreading the doc ?
[13:32] <ogra> didrocks, so drop g-s-d and nautilus ?
[13:32] <Kaleo> unity-2d-launcher depends on unity-asset-pool
[13:32] <didrocks> ogra: yes, you should IMHO
[13:33] <ogra> can you tag it DROP ?
[13:33] <didrocks> sure
[13:33] <ogra> thanks
[13:33] <ogra> so only the pixbuf engine left
[13:34] <didrocks> should be brought by something else IMHO
[13:34] <didrocks> let me check
[13:34] <didrocks> ogra: finally, you have more dep than unity has :)
[13:34] <ogra> well, can i install unity-2d and still have a working UI ?
[13:34] <ogra> with these deps
[13:34] <bregma> didrocks, could you look at #684275 (upload request for the ginn project)?
[13:34] <ogra> else we need to re-add recommends
[13:35] <didrocks> ogra: that's the question, I don't really know for that one  :)
[13:35] <didrocks> bug #684275
[13:35] <ogra> didrocks, can i do that with unity ?
[13:35] <didrocks> bregma: excellent, will get to it that week, thanks :)
[13:36] <ogra> Kaleo, i agree with your comment in the doc
[13:36] <didrocks> ogra: we don't use any theme engine
[13:36] <ogra> it should still be possible to just install unity-2d
[13:36] <ogra> without a toplevel metapackage
[13:36] <bregma> didrocks, thank, there are a few more multitouch upload requests pending I'll follow up on later
[13:36] <ogra> so things we need for functioning should be recommends
[13:37] <didrocks> bregma: got it, do not hesitate! :)
[13:37] <didrocks> ogra: you need rather a metapackage then, but we can have the same rationale with every apps…
[13:38] <ogra> didrocks, we will have a unity-2d package, i need to migrate unity-2d-default-settings into something
[13:38] <didrocks> in that case… :-)
[13:39] <ogra> at some point i would like to merge the other binary packages of the unity-2d source package into that too, but Kaleo wants them distinct for now for flexibility
[13:39] <Kaleo> ogra: what what
[13:39] <Kaleo> ogra: that's a very different problem
[13:39] <ogra> thats probably natty+1
[13:39] <Kaleo> ogra: merging the binaries is an upstream thing
[13:39] <Kaleo> ogra: that will not happen
[13:39] <ogra> Kaleo, no, its a packaging thing
[13:40] <Kaleo> ogra: which is equivalent
[13:40] <ogra> you currently build four binary packages
[13:40] <ogra> while unity doesnt
[13:40] <Kaleo> ogra: we distribute separate binaries for reasons that make the binary package existence valid
[13:40] <ogra> with my merge we will have one meta and four binaries
[13:40] <Kaleo> ogra: Unity _cannot_
[13:40] <Kaleo> ogra: Unity does not have multiple binaries
[13:41] <ogra> and it would make sense *at some point, i dont say _now_* to merge all binaries into the meta
[13:41] <Kaleo> ogra: I hint never :)
[13:41] <ogra> that doesnt make sense
[13:41] <Kaleo> ogra: we want to keep the flexibility for users
[13:41] <Kaleo> ogra: that means separate binaries and separate binary packages
[13:41] <ogra> why do you actually need these binary packages? do you expect anyone to use either of them standalone ?
[13:42] <Kaleo> ogra: yes
[13:42] <didrocks> well, for instance, we have in the unity package the plugin and the unity panel service, but you can't use one without the other one
[13:42] <Kaleo> didrocks: that is actually going to change AFAIK
[13:42] <Kaleo> didrocks: because it's likely Unity 2d is going to depend on the unity panel service
[13:42] <didrocks> Kaleo: if you are going to migrate to it, for sure
[13:42] <didrocks> yeah, I'll make a separate bin package for it then
[13:42] <ogra> well, if the intention is to use the launcher standalone (and if it acrtually works without any of the other) then i agree indeed
[13:42] <Kaleo> didrocks: right
[13:42] <Kaleo> ogra: that is the intention
[13:43] <Kaleo> ogra: and it does work
[13:43] <Kaleo> ogra: in fact some people already use it athat way
[13:43] <ogra> yeah, tne i fully agree
[13:43] <Kaleo> -a
[13:43] <ogra> *then
[13:43] <didrocks> Kaleo: just keep me in touch once all the seperating work done, so that we can work on the minimal package req.
[13:43] <Kaleo> :)
[13:43] <Kaleo> didrocks: sure, I will let you know when the time comes
[13:43] <ogra> i thought there were inter-dependencies between them
[13:43] <Kaleo> ogra: hopefully they will be resolved one day
[13:43] <Kaleo> ogra: oh, sorry
[13:43] <Kaleo> ogra: I misread you
[13:43] <Kaleo> ogra: there are no inter dependencies
[13:43] <Kaleo> ogra: or rather
[13:44] <ogra> right, sorry for assuming that :)
[13:44] <Kaleo> ogra: if they are they are going to be fixed soon
[13:44] <Kaleo> ogra: there is no runtime dependency that's for sure
[13:44] <Kaleo> ogra: you can run all four binaries on their own
[13:44] <ogra> k
[13:44] <Kaleo> ogra: there is some packaging dependenc for wrong reasons
[13:45] <Kaleo> ogra: and bug reports to fix them
[13:45] <Kaleo> +ies
[13:45] <ogra> so back to our cod
[13:45] <ogra> *doc
[13:45] <Kaleo> right
[13:45]  * ogra cant type today
[13:45] <ogra> pixbuf engine
[13:45] <Kaleo> so, I don't know for that one
[13:45] <ogra> what about that ?
[13:45] <Kaleo> let me bzr qlog
[13:45] <ogra> i cant imagine any qt binary using it
[13:46] <ogra> so it would only be pulled in as a meta dep
[13:46] <ogra> which makes it a recommend
[13:48] <Kaleo> https://bugs.launchpad.net/watuppa/+bug/645977
[13:48] <Kaleo> ogra: we use a bit of GTK internally
[13:49] <ogra> ok
[13:49] <ogra> heh, not allowed ... but i belive you :)
[13:49] <ogra> so keep it as dep
[13:49] <Kaleo> ogra: no
[13:49] <Kaleo> ogra: that's not the reason
[13:49] <Kaleo> ogra: we depend on libgtk2.0-0 in unity-2d-launcher already
[13:50] <Kaleo> ogra: looking at the bug report I think that it could be made a recommends
[13:50] <ogra> k
[13:51] <Kaleo> ogra: so
[13:51] <Kaleo> ogra: what is the difference between
[13:51] <Kaleo>  ubuntu-wallpapers and nautilus
[13:51] <Kaleo> for example
[13:51] <Kaleo> why DROP one and make the other a RECOMMEND
[13:51] <Kaleo> +s
[13:52] <ogra> you can run completely without wallpapers, but you should have some filemanager to be functional ?
[13:53] <ogra> and recommends allows you to replace nautilus with something else
[13:53] <Kaleo> ogra: I get it
[13:53] <ogra> so i would keep g-p-m, gnome-session, polkit and nautilus as recommends
[13:53] <Kaleo> ogra: didrocks: everybody happy with the final list?
[13:54]  * ogra is
[13:56] <Kaleo> ogra: thanks for bringing this up
[13:56] <ogra> Kaleo, well, it blocked me :)
[13:56] <didrocks> ogra, Kaleo: looks good to me. Still ensure about g-s-d and other stuff, but we'll see if you need a separate metapackage or not :)
[13:56] <ogra> i'll create the unity-2d package now and show you a diff for review
[13:57] <Kaleo> great
[13:58] <danilos> none of the gtk+ menus work for me in natty anymore since today
[13:58] <danilos> anyone knows what might be the problem and how do I best debug them?
[14:00] <Kaleo> ogra: do you want to take care of this too? https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/703170
[14:02] <ogra> Kaleo, heh, yeah
[14:04] <didrocks> danilos: stacking issue, try to right click on the wallpaper
[14:10] <lucazade1> Hi all! Is it a known bug that maximized windows don't blend in unity-panel if I use unity2d + compiz ?
[14:11] <lucazade1> (at least in maverick)
[14:12] <Kaleo> lucazade1: yes
[14:12] <Kaleo> lucazade1: and let me give you a tip
[14:12] <thisfred> ohai. I wonder if there is anything like a PPA we (the ubuntu one team) can start using to look at the launcher progress bars API. Or are they in Natty proper already?
[14:13] <lucazade1> Kaleo: ok
[14:13] <Kaleo> lucazade1: set the gconf key /apps/compiz/plugins/decoration/allscreens/options/decoration_match
[14:13] <Kaleo> lucazade1: to !(state=maxvert)
[14:14] <thisfred> njpatel: ^ (sorry yours is the only irc nick I know :D )
[14:14] <lucazade1> Kaleo: great, it works!
[14:16] <Kaleo> lucazade1: fantastic
[14:24] <jcastro> cando__: jamalta: hey guys I'm working on the unity report, anything you'd like to add for this week?
[14:27] <boulabiar> didrocks, ping
[14:27] <didrocks> boulabiar: hey
[14:27] <boulabiar> I want to ask you about putting a package in universe
[14:27] <boulabiar> bug #684275
[14:28] <didrocks> boulabiar: I was already pong by bregma some minutes ago )
[14:28] <boulabiar> ahh, haven't seen that
[14:28] <didrocks> boulabiar: so, will do a first review before EOW is the summarry :)
[14:29] <boulabiar> thanks
[14:29] <didrocks> yw
[14:33] <multiplatinum> ivanka,  remember me?
[14:37] <cando__> jcastro, nope..nothing new..:(
[14:58] <nerochiaro> Kaleo: did you see my note about CacheEffect on your MR ?
[15:03] <Kaleo> nerochiaro: yes still waiting for more input from you
[15:03] <nerochiaro> Kaleo: what do you need ?
[15:04] <Kaleo> "Florian, please hold on on this merge for a bit."
[15:04] <Kaleo> I suppose that "a bit" means you are going to investigate
[15:04] <Kaleo> and come back to me with "please merge"
[15:05] <Kaleo> or "don't merge"
[15:05] <nerochiaro> Kaleo: well, it was actually meant in the sense of "it seems broken in this case, so please don't merge before first figuring it out (or merge and go ahead if you don't care that i don't use it in my code for now)"
[15:05] <nerochiaro> Kaleo: guess it wasn't clear. sorry about that
[15:06] <Kaleo> nerochiaro: it was very clear
[15:06] <Kaleo> nerochiaro: but in the wrong sense
[15:06] <Kaleo> nerochiaro: so, you have the code that is broken with it
[15:06] <nerochiaro> Kaleo: ok. so if you want i can spend time and investigate it. i just know nothing about CacheEffect
[15:06] <Kaleo> nerochiaro: please investigate
[15:06] <nerochiaro> Kaleo: sure
[15:11] <Kaleo> nerochiaro: do you have the link to your todo list?
[15:12] <nerochiaro> Kaleo: http://ietherpad.com/eVgMjsVwiF
[15:12] <Kaleo> nerochiaro: thank you
[15:13] <multiplatinum> any gmail users in here?
[15:13]  * spikeb  
[15:14] <multiplatinum> spikeb,  may I pm u?
[15:14] <spikeb> sure
[15:19] <nerochiaro> Kaleo: i don't really understand why the cache effect actually caches. some explanatory comment would actually help in the class file. all i see is that it takes the sourcePixmap and paints it. doesn't the same thing happen normally when there's no effect at all ?
[15:22] <Kaleo> nerochiaro: you need to look at how an effect works
[15:24] <nerochiaro> Kaleo: well, the effects sit between the source element and the destination (i.e. the viewport in our case) and basically do their own custom painting by reimplementing the draw function
[15:25] <nerochiaro> Kaleo: " If effects are disabled, the source is rendered directly." which looks like pretty much what happens in your cache effect: you take the source and render it straight on the destination
[15:25] <nerochiaro> i'm surely missing something
[15:26] <Kaleo> nerochiaro: yes you are mising reading the code of Qt
[15:26] <Kaleo> nerochiaro: let me fetch the file
[15:26] <nerochiaro> Kaleo: so you're basically saying that the documentation sucks and one should not rely on it ;)
[15:27] <Kaleo> nerochiaro: src/gui/effects/qgraphicseffect.cpp
[15:27] <Kaleo> nerochiaro: no, I am saying you are interpreting the documentation
[15:27] <nerochiaro> Kaleo: and anyway, if one has to go read the QT source to now how your code works, you surely need comments, in my opinion
[15:27] <Kaleo> nerochiaro: that's true
[15:27] <Kaleo> nerochiaro: probably
[15:27] <nerochiaro> reading that source
[15:27] <Kaleo> nerochiaro: someone who wrote effects before would not need that documentation
[15:28] <nerochiaro> Kaleo: no, but someone trying to figure out why the effect wrote by something else screws up his otherwise working code does
[15:29] <Kaleo> nerochiaro: sure
[15:30] <Kaleo> nerochiaro: you are frustrated because your work is broken and there is no explanation in CacheEffect
[15:30] <Kaleo> nerochiaro: take the time you need to read src/gui/effects/qgraphicseffect.cpp and then we can talk
[15:31] <nerochiaro> Kaleo: doing that right now
[15:33] <smspillaz> (#ayatana, if you are cool with compiling compiz from source, then there is a fix for stacking http://smspillaz.ucc.asn.au/0001-Fix-stacking-madness.patch - I need testers :) )
[15:50] <nerochiaro> Kaleo: so basically the source internally uses a global cache, so whatever comes out of sourcePixmap is cached and you just draw it. right ?
[15:53] <Kaleo> nerochiaro: irhgt
[15:53] <Kaleo> nerochiaro: orrather whatever you draw is cached
[15:53] <nerochiaro> Kaleo: but isn't that what happens with declarative images anyway ?
[15:53] <ogra> Kaleo, http://paste.ubuntu.com/558148/
[15:53] <Kaleo> nerochiaro: not necessarily
[15:53] <Kaleo> nerochiaro: besides we are not dealing with an image here
[15:54] <ogra> i'm waiting for persia to return to cross check the transition for me
[15:54] <nerochiaro> Kaleo: isn't the background an image ?
[15:54] <ogra> but thats essentially what i plan to put into natty-release
[15:54] <Kaleo> ogra: is that the merge into unity-2d?
[15:54] <ogra> right
[15:54] <Kaleo> ogra: can you submit a merge request instead?
[15:54] <Kaleo> nerochiaro: look at the code
[15:54] <nerochiaro> Kaleo: ok, i take that back, it's the entire Item
[15:54] <ogra> Kaleo, into my own branch ?
[15:54] <Kaleo> :)
[15:54] <ogra> k
[15:54] <Kaleo> ogra: into trunk
[15:55] <ogra> Kaleo, does trunk already have all bits from natty-release ?
[15:55] <Kaleo> ogra: I don't know I was not aware of natty-release until a few days ago
[15:56] <Kaleo> ogra: I have not synced anything yet
[15:56] <nerochiaro> Kaleo: so what's wrong there is that the effect doesn't take into account correctly the fact that the Item is being scaled
[15:56] <nerochiaro> probably
[15:56] <ogra> i think natty-release is a bit ahead atm
[15:56] <ogra> at least chanbgelog wise
[15:56] <ogra> upstream should be identical
[15:56] <ogra> *changelog
[15:56] <Kaleo> ogra: you see why I dislike having 2 branches
[15:57] <ogra> Kaleo, totally
[15:57] <Kaleo> ogra: because we end up having that conversation :)
[15:57] <ogra> yeah, but its there now
[15:57] <Kaleo> yep
[15:57] <Kaleo> trying a merge
[15:57] <ogra> :/
[15:58] <Kaleo> ogra: I merged natty-release into trunk
[15:58] <Kaleo> ogra: can't you just do the work on trunk?
[15:58] <ogra> no conflicts ?
[15:58] <Kaleo> ogra: none
[15:59] <ogra> Kaleo, well, then i need to change all the Vcs-Bzr entries again
[15:59] <Kaleo> ogra: that's a small price to pay :)
[15:59] <ogra> i just adjusted all of them for the natty-release branches
[15:59] <Kaleo> yes that's what I just merged
[15:59] <ogra> right
[15:59] <Kaleo> but unless NCommander comes in screaming
[15:59] <ogra> there was also a .bzrconfig setup i added
[15:59] <Kaleo> I say let's drop them
[15:59] <Kaleo> ogra: which is great for trunk
[16:00] <ogra> to get bzr builddeb working
[16:00] <Kaleo> ogra: we like .bzrconfig
[16:00] <ogra> right, did that get in as well ?
[16:00] <Kaleo> ogra: yes
[16:00] <ogra> great
[16:00] <Kaleo> ogra: bzr did its job :)
[16:00] <ogra> just wanted to be sudre
[16:00] <ogra> :)
[16:01] <ogra> lets discuss the natty-release branches once NCommander is awake, i dont want to rule that above his head
[16:01] <ogra> i fully agree with you though
[16:09] <multiplatinum> ivanka1,  you there?
[16:10] <ivanka1> multiplatinum: hi - I am in meetings all afternoon. We will have to talk another day. Sorry!
[16:10] <multiplatinum> Np, cya
[16:35] <nerochiaro> Kaleo: ping me whenever you want to pick up where we left
[16:54] <Kaleo> nerochiaro: back
[16:58] <nerochiaro> Kaleo: ok. so basically i was say that probably what's wrong there is that the effect doesn't take into account correctly the fact that the source Item is being scaled
[17:06] <Kaleo> nerochiaro: hmmm, interesting idea
[17:07] <nerochiaro> Kaleo: well, that's what i am imagining from seeing the visual issue and peeking at the code, and the fact that you only used it with backgrounds whose scale is not animated
[17:07] <nerochiaro> Kaleo: so you probably didn't test if it worked in case the source changed
[17:07] <Kaleo> nerochiaro: the source changed? what?
[17:08] <Kaleo> nerochiaro: you mean in case the scale changes
[17:08] <nerochiaro> Kaleo: for example, yes
[17:08] <Kaleo> nerochiaro: what do you mean for example? isn't it the entire problem here (supposedly)
[17:09] <nerochiaro> Kaleo: well, in my case yes. but i guess it will have the same problem if the source is rotated or transformed in any other way. i guess you need to reimplement QGraphicsEffect::sourceChanged to be notified about any changes
[17:10] <Kaleo> nerochiaro: so you see here the issue is
[17:10] <Kaleo> nerochiaro: that the cacheeffect purpose is to prevent redraws when this happens
[17:11] <Kaleo> nerochiaro: when it's being moved or transformed
[17:11] <Kaleo> nerochiaro: and it's important if you want to get smooth animations
[17:12] <Kaleo> nerochiaro: I need to see the issue visually, can I pull your branch?
[17:12] <nerochiaro> Kaleo: certainly. you only have to comment the cacheeffect in the gnomebackground
[17:13] <nerochiaro> Kaleo: i mean, un-comment
[17:13] <nerochiaro> Kaleo: then trigger the workspace switcher, and un-zoom a workspace and zoom another
[17:13] <nerochiaro> (that's the nastiest case)
[17:14] <Kaleo> nerochiaro: is there a workspace switcher button?
[17:15] <nerochiaro> Kaleo: not yet. it's down in the list
[17:15] <nerochiaro> Kaleo: just activate it as you did the original spread
[17:15] <Kaleo> ok
[17:15] <Kaleo> I see
[17:16] <nerochiaro> Kaleo: same as last time you tried it
[17:16]  * Kaleo is going to make some pasta
[17:16] <Kaleo> (and think)
[17:16] <nerochiaro> Kaleo: damn, you're making me hungry now
[17:17] <Kaleo> nerochiaro: the way I see it it sounds like a bug in Qt
[17:19] <nerochiaro> Kaleo: I can't honestly say i understand enough of the whole effect framework from my quick look today to be able to tell. I just don't see where you take scale into account in the effect code though
[17:19] <nerochiaro> Kaleo: i mean, the cacheeffect code
[17:19] <Kaleo> nerochiaro: you don't have to
[17:21] <Kaleo> nerochiaro: http://bugreports.qt.nokia.com/browse/QTBUG-5918
[17:22] <Kaleo> nerochiaro: not the same thing but interesting
[17:25] <nerochiaro> Kaleo: that's rotating the destination, but i guess similar indeed
[17:28] <Kaleo> nerochiaro: http://bugreports.qt.nokia.com/browse/QTBUG-9543
[17:28] <Kaleo> nerochiaro: this is probably the one
[17:31] <nerochiaro> Kaleo: looks like that one is fixed in 4.7 though
[18:16] <lamalex> dbarth_, njpatel who is going to that x meeting / what time is gmt?
[18:16] <njpatel> lamalex, what x meeting? http://www.google.co.uk/search?sourceid=chrome&client=ubuntu&channel=cs&ie=UTF-8&q=time+in+gmt
[18:17] <lamalex> njpatel, im sorry i meant to ping jay- but he's not here
[18:17] <lamalex> so i guess me