[15:23] <ali1234> when I try to load indicator-bluetooth i get this error: "WARNING    Gtk                       gtk_menu_new_from_model: cannot find type 'com.canonical.indicator.switch'"
[15:23] <ali1234> i thought all these custom Gtk menu models were supposed to be in ido, but this one is not
[21:14] <cwayne> is the orange bar under the panel hardcoded? or configurable?
[21:20] <cwayne> mzanetti: ^ any idea?
[21:30] <mzanetti> cwayne: hardcoded
[21:31] <cwayne> mzanetti: any chance to make it a dconf key or configurable somehow?
[21:31] <mzanetti> cwayne: if its needed, sure
[21:31] <mzanetti> cwayne: I wonder if this shouldn't be a theme property
[21:31] <mzanetti> cwayne: which would also affect the one in the indicators etc
[21:32] <cwayne> mzanetti: i think that would make sense
[21:32] <mzanetti> cwayne: but once again, you need to ask design if they are fine with it
[21:32] <cwayne> it should definitely be somehow configurable, as it doesn't fit with certain backgrounds
[21:33] <cwayne> right now i have a blue background, and the orange bar just looks weird with it
[21:33] <mzanetti> cwayne: I think you need to start a broader discussion about all of this. so we can find a way to centrally configure all the stuff you are doing instead of creating different custom settings here and there
[21:33] <cwayne> fair enough
[21:37] <cwayne> mzanetti: should i start a discussion on any particular mailing list?
[21:38] <mzanetti> cwayne: yes
[21:38] <cwayne> which one? :)
[21:39] <mzanetti> :)
[22:06] <cwayne> mzanetti: btw is jenkins back up yet?
[22:07] <mzanetti> cwayne: yes. since a couple of hours
[22:07] <cwayne> mzanetti: awesome, so we should see some unity fixes soon?
[22:08] <mzanetti> cwayne: yes. but so far the release jenkins didn't stop by
[22:08] <cwayne> ah
[22:21] <cwayne> mzanetti: last question, i swear :)  i need to write a quick (mostly-faked) scope that adds a category to the apps master scope.  is there any tutorial for this?
[22:22] <mzanetti> cwayne: no idea. mhr3 would be the right one to ask
[22:25] <cwayne> mzanetti: ah, thanks
[23:21] <bregma> cwayne, have you read http://developer.ubuntu.com/resources/tutorials/scopes/writing-a-unity-scope/ ?
[23:22] <cwayne> bregma: i thought that was for desktop (i.e. unity 7)
[23:22] <bregma> the back end is the same regardless
[23:23] <cwayne> ah, i thought it'd changed
[23:25] <bregma> nope, you're supposed to be able to run Unity 7 and Unity 8 on the same machine, soon, sort of
[23:27] <cwayne> ah right, of course, that makes sense
[23:28] <cwayne> unfortunately all the scopes i've written in the past have been in python rather than c :)
[23:32] <bregma> python works, it's just more resource-intensive
[23:32] <cwayne> right
[23:32] <cwayne> also it's not in the default utouch image as i understand it
[23:32] <bregma> most of the satndard ones have been rewritten in vala
[23:32] <cwayne> yeah
[23:33] <cwayne> bregma: i don't suppose any of them are packaged in click packages yet?
[23:33] <bregma> none of the standard scopes are in click packages because they come on the Touch image
[23:34] <cwayne> yeah, that's what i thought
[23:35] <cwayne> whats the plan for installing additional scopes on the R/O image?  either putting them in ~/.local/share/scopes or as click packages *should* work