[00:37] <DalekSec> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160401-xenial.html#ubuntustudio
[10:05] <zequence> sakrecoer: Oh, lunatic -tac. I see
[10:15] <zequence> What would ge a multimedia alternative to a file folder
[10:15] <zequence> Apart from digital hardware, like harddisks, and such
[10:15] <zequence> I'm thinking about a possible Ubuntu Studio folder icon
[10:16] <zequence> Instead of a folder, we could use something else, that could be just as generic
[10:16] <zequence> Like a simplification of a small shelf of things, CDs or something
[10:28] <zequence> or some sort of presentation of bits (in a nice artistic way), what files actually consist of
[10:58] <zequence> representation*
[11:12] <sakrecoer> a robobrain
[11:12] <sakrecoer> or a roboheart
[11:12] <cfhowlett> a BEATING roboheart!
[11:13] <cfhowlett> ba bump  ba bump ba bump ...
[11:13] <sakrecoer> feels like a robobrain signals CPU
[11:13] <sakrecoer> hehe :)
[11:14] <sakrecoer> zequence: do you find nox in there, or do i seriously need to take a senility test?
[11:17] <zequence> We should add something to the favorites in the menu
[11:17] <zequence> Like system settings
[11:32] <sakrecoer> the settins are always visible in the menu
[11:32] <sakrecoer> next to the power/logoff button
[11:34] <sakrecoer> maybe jack... thinking of an equivalent in graphics, but all that comes to mind is font manager..
[11:38] <zequence> Ah, right. But, it wouldn't hurt to have it in favorites as well
[11:38] <zequence> qjackctl makes sense, yes
[11:39] <zequence> ubuntustudio-controls maybe
[11:41] <zequence> NOX is in there, yes
[11:41] <zequence> Probably included with a multi theme package
[11:41] <zequence> HOw do I change colors now?
[11:42] <zequence> Ah
[11:45] <zequence> sakrecoer: I really don't like murrina blue
[11:45] <zequence> So, I would go with something else there
[11:46] <sakrecoer> but you changed the color of it right?
[11:46] <zequence> Oh, I need to relogin?
[11:46] <sakrecoer> anyways, it looks best with dark buttons that come with nox
[11:47] <sakrecoer> teah, some changes wont effect if you don't.. can't remember which ones..
[11:47] <sakrecoer> also, to see the lightdm changes..
[11:49] <zequence> The murrina blue is very much blue
[11:49] <zequence> There's a problem in the indicator area with the colors
[11:51] <zequence> The custom hilight and custom menu colors are fine
[11:51] <zequence> We might need to do the same for the whisker menu
[11:56] <zequence> Custom panel color doesn't work well
[11:58] <zequence> It's better to change it somewhere else. Like in "Panel"
[12:00] <zequence> I prefer the default window manager theme
[12:00] <zequence> ..when using NOX
[12:01] <zequence> ..but NOX had some GTK issues
[12:01] <zequence> So, that is a big minus
[12:02] <zequence> Wait, NOX brings out GTK3 styling it seems, but without the colors
[12:05] <zequence> I'm not really fond of the NOX grey either. Too bright.
[12:05] <zequence> I do think we should keep the lightdm theming
[12:05] <zequence> I mean, out of your suggestions
[12:09] <zequence> The lightdm theme has the wrong hilighting though. Not an enormous deal, but it looks weird with the red
[12:12] <zequence> sakrecoer: Our lightdm config is in /etc/xdg/xdg-ubuntustudio/lightdm/
[12:12] <zequence> Belongs to the package ubuntustudio-lightdm-theme
[12:13] <zequence> For some reason the default background never shows before first login
[12:22] <zequence> Think the config needs to be put in a different place
[12:38] <zequence> It should work the way it does now, but we can also install the greeter config into a different spot
[13:00] <krytarik> sakrecoer: So, 'ubuntustudio-look' pulls 'murrine-themes', which includes those two themes.
[13:09] <krytarik> zequence: And maybe we should maintain the greeter settings along with the other default settings - because apparently you have a 'lightdm.conf' in there too.
[13:19] <zequence> Really? Well, it's also artwork related, so
[13:20] <zequence> Right
[13:20] <zequence> The config in -default-settings is just to set the correct greeter and session
[13:20] <zequence> Nothing to do with artwor
[13:20] <zequence> artwork*
[13:20] <zequence> So, that makes sense
[13:22] <zequence> All though, that kind of correlates to the theme as well
[14:22] <sakrecoer> not sure i got things right, but krytarik linked me to this yesterday: http://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/view/head:/usr/share/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf and it seems to set the wallpaper for lightdm...
[14:23] <sakrecoer> zequence: 
[14:26] <zequence> Everyone is doing it differently, it seems
[14:26] <sakrecoer> :)
[14:26] <zequence> ubuntu mate has yet another method
[14:55] <OvenWerks> I would caution against populating "favourites" with single use applications such as -controls or settings.
[14:57] <OvenWerks> That is in fact one of my biggest beafs with the indicator over the systray. Indicators dedicate one whole mouse click to a single use purpose (settings) thus removing functionality that was previously available in systray icons.
[15:07] <sakrecoer> zequence: have you noticed the icon for battery charge with greybird?
[15:09] <sakrecoer> it is different when charging...
[15:09] <sakrecoer> colors and kindof pseudo 3d..
[15:12] <sakrecoer> weird... i created a new user, and there the icon is fine. but if i change the appearance theme, log out, log back in, then change back to greybird, the icon is changed, even with ubuntustudio iconset selected in appearance
[15:13] <sakrecoer> http://sakrecoer.com/ubuntustudio/Screenshot_2016-04-06_17-12-51.png
[15:15] <OvenWerks> That looks nice. I hadn't noticed that as I don't use batteries/laptops. I will have to remember to hook up a wiimote when I test.
[15:17] <sakrecoer> i found why: i had enlarged the panel to 28 pixels
[15:17] <sakrecoer> putting it back to 25 gave me the classic bi-chromatic icon
[15:19] <sakrecoer> zequence: but would you agree that the menus pulling down from the indicator and right click on the panel should be the same color than the panel?
[15:21] <OvenWerks> sakrecoer: right now they are the same as window decorations.
[15:23] <OvenWerks> same as menus everywhere
[15:25] <zequence> sakrecoer: The menu color is nice, but it's such a small change that I wonder if that is worth the trouble at this point
[15:25] <zequence> Should we change to the dark theme in lightdm, even though hilighting is red there?
[15:26] <OvenWerks> sakrecoer: remember that some applications set their own menu colours, but are generally based on a light grey.
[15:26] <zequence> sakrecoer: Do you know where the menu is configured - in which file?
[15:27] <OvenWerks> zequence: he said "menus" so not whisker, but all the drop down menus from indicators, etc.
[15:27] <zequence> OvenWerks: Yep, I know
[15:28] <OvenWerks> zequence: I would expect that to be the same as application menus
[15:28] <OvenWerks> (except where the application itself goes somewhere else)
[15:30] <zequence> OvenWerks: Well. Do know which file that is?
[15:31] <sakrecoer> you gave me the path yesterday zequence , i'm looking for it now, but i'm slow
[15:32]  * OvenWerks wishes for a tool that would allow querying the colour under the mouse
[15:32] <zequence> OvenWerks: There is a color picker tool for that
[15:32] <zequence> The same as in GIMP, but a standalone
[15:32] <zequence> gtk2, I think
[15:32] <sakrecoer> OvenWerks: agave is almost always open on my box for that reason
[15:32] <OvenWerks> zequence: I tought menu colour was part of the theme.
[15:33] <zequence> OvenWerks: gcolor2
[15:33] <zequence> OvenWerks: If you read sakrecoer's suggestion for theme changes, you will have seen where in the GUI he makes those changes
[15:33] <zequence> And, those end up in config files
[15:33] <zequence> I'm looking for them in ~/.config/xfce4 
[15:34] <OvenWerks> sakrecoer: I tried agave, but it didn't seem to allow testing colours in other windows... I may be missing something.
[15:36] <zequence> sakrecoer: I found it. It's in .config/gtk-3.0/gtk.css
[15:36] <sakrecoer> whats the magic command to search within files? grep? with it, one could serach for the color HEX...
[15:36] <sakrecoer> ah nice!
[15:36] <zequence> fgrep
[15:36] <sakrecoer> but that is only for gtk3
[15:37] <zequence> Well, yes
[15:37] <sakrecoer> there is one for gtk2 as well..
[15:37] <zequence> sure?
[15:37] <OvenWerks> and qt4 and qt5 and kde ?
[15:37] <sakrecoer> i was looking for the default files in /etc/xdg/*
[15:38] <zequence> I think we should leave this, and put it aside until someone starts working on a ubuntustudio gtk theme
[15:38] <sakrecoer> zequence: i sure have .config/gtk-2.0/
[15:38] <zequence> That would be for some other reason
[15:39] <zequence> ..since I don't have it
[15:39] <zequence> But, I can see that the css file has the correct colors, so I'm assuming that is where it is done
[15:39] <zequence> sakrecoer: Make sure to read files like that with something that has color coding
[15:40] <sakrecoer> it got there after i tried different themes in appearances
[15:40] <zequence> (in case you aren't)
[15:40] <zequence> Ok, well, it wasn't due to the menu change
[15:40] <sakrecoer> what do you mean zequence "something that has color coding"
[15:41] <zequence> sakrecoer: Not the right term. Something that shows code in color, so that you can easily see what is waht
[15:41] <zequence> css files have color schemes for a lot of text editors suitable for coding
[15:41] <zequence> Such as nano, for instance
[15:42] <sakrecoer> ah! nano has color coding now? :D
[15:42] <zequence> Not something recent
[15:43] <sakrecoer> hehe, well html color coding was real poor last time i checked :D
[15:43] <zequence> Think color scheme is a better expression
[15:43] <zequence> It's not perfect, compared to more serious editors
[15:43] <zequence> gedit has fairly good support
[15:43] <zequence> I use atom myself, when I code
[15:44] <zequence> But, it's kind of heavy
[15:44] <sakrecoer> i like nano actualy. vim is nice too, but it just made me pull my hair of when i tried to edit .bashrc
[15:45] <sakrecoer> i'm prolly doing it wrong, but insert and 'I' wouldn't work like i'm used to
[15:47] <sakrecoer> just=20 minutes ago
[15:49] <zequence> I never learned vim. I'm sure it's a great editor, once you understand how it works.
[15:50] <zequence> If it set tab size (in spaces) for several lines of code at once, I would be sold.
[15:50] <zequence> if it can set tab size for several lines of code at once, is what I meant
[15:51] <zequence> Not all editors can do that, and it's so nice when you can. Also to be able to comment large sections of codes by selecting it and using a shortcut
[15:56] <sakrecoer> i think you can add som script for that. I'm not sure, but i think i remember something like that in the script for checking manual-tests..
[15:56] <sakrecoer> because they want 4space tabs in the manual tests..
[16:04] <zequence> Yes, that should not be a problem
[16:04] <zequence> nano can do that too
[16:04] <zequence> I mean, adding spaces instead of tabs
[16:05] <zequence> But, can you change tab size for multiple lines at once?
[16:06] <sakrecoer> i don't know :) i thought i knew how to enter a line and navigate in vi, but it seems i don't anymore... (to give you a scale of my level in vim:D)
[16:06] <zequence> Also, cut and paste code, keeping the tab size within the code you cut, and paste it to any tab depth
[16:08] <sakrecoer> pressing the arrows noe give me letters, cut and paste is waaay out my scope at this level :D
[16:08] <sakrecoer> s/noe/now
[16:10] <zequence> I'm going to fix some package building recipes, so that any changes to our source will autobuilt into our testing PPA
[16:10] <zequence> The ubuntustudio-dev team has one
[16:10] <zequence> That way, it's easy to just add the PPA and do testing before stuff is uploaded
[16:16] <zequence> sakrecoer: I'm adding our wallpaper as default now. Haven't heard from madeinkobaia, so thinking we just go ahead now, as planned
[16:19] <zequence> sakrecoer: Can you think of a good name for it?
[16:19] <zequence> Otherwise, I'll just call it 1604_default.png
[16:21] <sakrecoer> i was about to ask you about madeinkobaia... call it 1604-colorghost.png :p
[16:21] <zequence> Alright
[16:21] <sakrecoer> \o/
[16:22] <zequence> I sent a couple of emails to madeinkobaia already a week ago, or more, so he has had the chance to answer
[16:25] <zequence> We should change the CoF for the plymoth theme
[16:27] <sakrecoer> maybe the ghost cof would do good in there too?
[16:27] <zequence> Ah, damn. I've forgotten to implement the new CoF.
[16:27] <sakrecoer> implement it where?
[16:28] <zequence> Into everywhere
[16:28] <zequence> Maybe we can save that for the next release
[16:28] <sakrecoer> ah you mean the one that knome drew?
[16:28] <zequence> Yes
[16:28] <zequence> I still would like to see how they look after some small adjustment
[16:29] <zequence> As I've mentioned before, they looked a little fat to me.
[16:30] <sakrecoer> yeah, right, but the one we have now looks crooked... i don't know what is best, anyways, i think i've said everything i have to say many times now :D
[16:35] <zequence> Adding the ghost CoF is a little tricky. I need to rewrite the plymoth script
[16:35] <zequence> ..to adjust it's position and size
[16:37] <sakrecoer> i wouldn't know how to, so do as you wish/can... (althought i've been anoyed about the circle being just slliiiightly off for very long, and it still is)
[16:38] <zequence> sakrecoer: If you like, you could fix knomes CoF, making it similar in thickness, make a new wallpaper and a ghost CoF
[16:39] <sakrecoer> ok, i'll try!
[16:43] <zequence> meanwhile, I will see if I can use the current GhostCof in plymoth
[17:18] <sakrecoer> zequence: i'm sorry, but i really don't see that fatness nor what is to be fixed... i'm juxtaposing the crooked one and the knome one, and all i see is "\o/ work is done thank you mr. knome"
[17:20] <zequence> Ok, let me do that then
[17:24] <zequence> sakrecoer: I can't find knomes branch anymore. Where is it? Or you have the files?
[17:24] <sakrecoer> https://code.launchpad.net/~knome/ubuntustudio-artwork/current-standard-fixes
[17:24] <zequence> Ok, yeah found it on his page
[17:25] <zequence> Ah, right. I was looking at the wrong branch before
[17:25] <sakrecoer> don't know how its done but it is also visible here: https://code.launchpad.net/ubuntustudio-artwork
[17:28] <zequence> sakrecoer: If you compare the two CoFs, you'll find some very clear differences
[17:28] <zequence> Like the size of the hole in themiddle
[17:28] <zequence> For me it was a clear change, so not only an improvement
[17:28] <zequence> Not only a fix, so to say
[17:29] <zequence> Since the original was not perfectly shaped, making the new version similar has to be done with some compromize
[17:29] <sakrecoer> that is actualy true, however, it is impossible to see that at small size, AND knome's version works well in small size.
[17:31] <zequence> After looking carefully now, I do find that knomes version might be better after all
[17:32] <zequence> My initial reaction was just - it's not only a fix. It's also a change
[17:32] <zequence> So, I wasn't eager to just pass it through. But, it feels right now
[17:32] <zequence> So, I'll just merge that
[17:32] <knome> :)
[17:32] <sakrecoer> \o/
[17:33] <knome> there are several reasons why it is as it is, most of them related to the old version not being symmetric and not in the middle of the circle
[17:33] <sakrecoer> it's perfect! i acutaly think the hole is better balanced in knomes version
[17:33] <knome> indeed - the middle of the hole is at the middle of the circle
[17:34] <flocculant> no ellipses then
[17:34] <knome> no
[17:34] <knome> or chicken nuggets
[17:34] <zequence> sakrecoer: Please use that CoF to update the wallpaper then
[17:35] <sakrecoer> i will!
[17:35] <sakrecoer> and it's pickles, knome and flocculant 
[17:35] <sakrecoer> in that order :D
[17:35] <knome> a booger it is
[17:39] <sakrecoer> zequence: did you forget to pull my changes to the branch maybe?
[17:40] <sakrecoer> i'm probably just confused about how bzr works again
[17:40] <sakrecoer> i see the number of your commit being "4"..
[17:40] <sakrecoer> yup, nevermind me...
[17:42] <sakrecoer> ok i get it now.. current-standard is another branch...
[17:44] <zequence> sakrecoer: Yeah, if we were using git, we might have that as a submodule to the main branch, so that it's always there, and updated
[17:45] <sakrecoer> ok... then we should remove everything named "current standard" from the trunk, no?"
[17:45] <sakrecoer> or at least, move it over...
[17:46] <zequence> there's no current standard dir in the 1604 development branch, and neither should there e
[17:46] <zequence> be*
[17:47] <zequence> the trunk is only for this release. Once we are done, we'll rename it, and create a new trunk
[17:47] <sakrecoer> no, but there is folder called 16.04, in which there is a copy fo the crooked cof and a text file with "current standard" in the name
[17:47] <zequence> Yes, those should be changed
[17:48] <zequence> That's a bit messy. The current standard file should be removed
[17:48] <sakrecoer> i propose to add the color codes of the workflows in the txt file and move it to current-standrard branch
[17:48] <zequence> Sure
[17:48] <sakrecoer> and delete those the crooked cof and woddmark from there...
[17:48] <sakrecoer> make sure noone uses them again
[17:49] <knome> sakrecoer, you'd think so...
[17:50] <sakrecoer> are saying they will reappear sooner or later, knome? :D
[17:50] <knome> yeah, we're seeing the xubuntu logo from pre-12.04 used around the web
[17:51] <knome> even if it's *completely* different
[17:51] <zequence> We'll need to create a new license. UUFBC - Use Until Forbidden By Creator
[17:51] <sakrecoer> hahaha!!!!
[17:51] <sakrecoer> oh my, i think you  just created a monster zequence!!
[17:51] <sakrecoer> UUFBC :D
[17:52] <knome> zequence, as if people respected licenses..
[17:53] <zequence> When FBI warnings don't even help, I guess not
[17:56] <zequence> sakrecoer: (re finding something from inside a file, -r is recursive): fgrep -r <pattern> <path>
[18:05] <sakrecoer> thanks!!! :)
[18:10] <zequence> sakrecoer: Could you also make one CoF twice the size as last time, with the ghost effect.
[18:11] <zequence> resolution x2, that is. width x2, height x2
[18:11] <sakrecoer> sure!
[18:12] <sakrecoer> my spelling is so terrible, i should be banned from writing commit notes :|
[18:22] <zequence> ubuntustudio-look is probably one of the reasons why our ISO has grown a bit lately
[18:22] <zequence> It's over 100Mb
[18:26] <zequence> sakrecoer: Oh, and if we want to use the ghost CoF with the text logo, it would be helpful if the larger spread of light was removed, or very much focused on a small area
[18:28] <zequence> Right now, the png image is many multiples larger than the CoF itself, which is ok on the wallpaper.
[18:34] <zequence> I'm going to try the one with the larger spread on the plymouth theme to see how that looks
[18:37] <sakrecoer> the blender in the dev build is very weird...
[18:38] <sakrecoer> it gives 2 different results in the viwer and the composite output, altho connected to the same node
[18:44] <sakrecoer> yeah something isn't quite right, but then again, in blender so many things can be missconfigured by user. put that in the context of my hands and then lay back and relax
[18:45] <sakrecoer> anyways upgrading blender is the easiest thing in the world, even tho, upgrading a blender that integrate jack remains a mystery to me
[18:47] <zequence> I was able to make plymouth show a blue background. Not my intention, but at least I changed something!
[18:47] <zequence> Only that. Only a blue background
[18:47] <sakrecoer> :D
[18:48] <sakrecoer> #009bf9?
[18:48] <zequence> Not sure where it came from
[18:48] <sakrecoer> from beta1 maybe? :D
[18:48] <zequence> I changed the script, but for some reason it didn't work
[18:55] <sakrecoer> oh, my blender issue is a lack of ram in compositor.. got a bit greedy when scaling up :D
[19:04] <sakrecoer> it'll have to wait until i get home. scaling the logo instead of the resolution changes the effect...
[20:07] <zequence> The plymouth theme will be pretty sweet with the new logos
[20:07] <zequence> But, this is taking a lot of time :P
[20:53] <zequence> Suspend froze my laptop. Our plymouth theme has artwork for suspend, but I've never actually seen it in action
[20:53] <zequence> It suspended, but did so terminally
[21:00] <zequence> sakrecoer: Would be great if you could smoke test the latest plymouth theme. It doesn't include the right CoF, but I can change that later. For now, I just want to know the dimensions are right
[21:00] <zequence> The package is building right now
[21:00] <zequence> Will be available at this PPA ppa:ubuntustudio-dev/autobuild
[21:02] <zequence> Ah, maybe not. Something's not right
[21:03] <zequence> Well, just pull the source for ubuntustudio-look, and build it locally with 'dpkg-buildpackage -uc -us'
[21:04] <zequence> (check help for dpkg-buildpackage to see what those options mean - they allow you to build without signing)
[21:09] <zequence> I just realized we have a project for plymouth-theme-ubuntustudio, and a branch for it, but it is already included in ubuntustudio-look - very nice
[21:22] <zequence> Actually, it's not up yet, but will be in a few moments
[21:23] <knome> zequence, ubuntustudio.org should now have the latest theme revision up
[21:23] <zequence> knome: Thanks.
[21:29] <zequence> sakrecoer: Ok, ubuntustudio-look is updated with a new plymouth theme, so please try it
[21:36] <zequence> sakrecoer: I also added a new text logo (based on an extablished madeinkobaia variant, that we have on a t-shirt) to current-standard
[21:36] <zequence> The only difference is in that "Studio" is blue
[21:38] <zequence> The plymouth theme needed some color. That could have been done with the background too, of course. I did add a hint of blue to it, just to make it less monochrome
[21:38] <zequence> But, even so, it was too black and white.
[21:40] <zequence> Ok, sleep time. Over and out for now.