[00:01] <ochosi> brainwash: bleh, i made a mistake, s/none/transparent/
[00:06] <ochosi> Unit193: also feel free to give this a shot if you can ^
[00:06] <ochosi> will take another week until i get trusty
[00:06] <brainwash> nope
[00:06] <ochosi> doesn't work?
[00:06] <brainwash> not for me
[00:07] <brainwash> setting the background of .menu to "none" does kinda work
[00:07] <ochosi> a-ha?
[00:08] <brainwash> background stays completely blue, but font won't turn white
[00:08] <brainwash> changes to the *hover thingy don't seem to have any effect
[00:09] <brainwash> *:hover
[00:09] <ochosi> you can add "color: @panel-fg-color;"
[00:09] <ochosi> to *:hover
[00:09] <ochosi> or the label/image hover
[00:11] <brainwash> *:hover is ignored completely I think
[00:11] <ochosi> no, at least in your screenshot the whole area around the label is drawn by *:hover
[00:12] <ochosi> it just seems like the "background-color: transparent;" is broken or something
[00:14] <brainwash> removed *:hover -> no changes at all
[00:15] <ochosi> ok, then try to remove all the menu code and see what happens
[00:16] <brainwash> ochosi: another funny thing: when I move the cursor between the panel and the opened indicator menu, icons in the menu get slightly brighter
[00:17] <ochosi> yeah, that's a gtk3 feature
[00:17] <ochosi> it's the same in toolbars
[00:17] <brainwash> oh
[00:19] <brainwash> removed the menu code, highlighting works now, background + font... but the font has an ugly shadow effect now
[00:21] <brainwash> but wait a minute, you still did not setup a trusty test environment? :)
[00:22] <Unit193> What do you think you're for?
[00:23] <ochosi> brainwash: i have a 100gb ssd atm, which holds all my data, so no, i don't have free space
[00:23] <ochosi> and +1 Unit193 
[00:24] <brainwash> 100gb
[00:24] <brainwash> that's huge
[00:26] <ochosi> only if you're used to chromebooks
[00:31] <ochosi> brainwash: apart from the text-shadow, which should be straightforward to fix, do multi-line hovers look ok as well?
[00:31] <ochosi> e.g. when you use the soundmenu and have a track running in some musicplayer
[00:31] <ochosi> you should get a hover effect spanning 3 lines
[00:32] <ali1234> works with orion :)
[00:33] <ochosi> cool
[00:33] <ochosi> well nice, less code is better then
[00:33] <ochosi> i'll see whether i can put that together so that it works in both saucy and trusty
[00:33] <ali1234> less code = fewer bugs, always
[00:33] <ochosi> yeah, pretty much
[00:34] <ochosi> actually we've been adding new stuff to the greeter (i'm about to merge a branch that'll fix nouveau), so if you wanna look for leaks... ;)
[00:34] <sergio-br2> ochosi, i did:  git pull origin master
[00:35] <sergio-br2> is it right?
[00:35] <ochosi> yeah, if master is the branch you want
[00:35] <sergio-br2> but there is nothing related to me in github
[00:36] <sergio-br2> how can i see the commit?
[00:36] <ochosi> related to you? if you want to push something, then pull isn't the correct command
[00:36] <sergio-br2> humm
[00:37] <ali1234> what are you actually trying to do?
[00:37] <sergio-br2> but i can't push to shimmerproject
[00:37] <sergio-br2> i'm trying to send a commit at elementary-xfce
[00:37] <ali1234> there's multiple ways to do that
[00:37] <ali1234> pull is not one of them though
[00:37] <sergio-br2> haha ok
[00:38] <ochosi> you can't push to the shimmerproject directly
[00:38] <ochosi> the best way to get this to work is to create your own github account
[00:38] <ochosi> then fork elementary-xfce (if that's what you wanna work on)
[00:38] <ochosi> and then push the changes to your own repo
[00:39] <Unit193> Or, git diff | pastebinit and send to ochosi. :D
[00:39] <sergio-br2> hum ok. I have an account at github
[00:39] <ali1234> not
[00:40] <ochosi> Unit193: thanks, advocatus diavoli!
[00:40] <brainwash> ochosi: looks ok, multi-line hove
[00:40] <ali1234> Unit193: no, you can't do that. output of git diff cannot be applied. use git format-patch HEAD^ (after commiting) for this :)
[00:41] <Unit193> Seems to work for me, but yeah, I was kidding.  It works for the code, but not attribution.
[00:42] <ochosi> brainwash: ok, so removing those lines fixes everything apart from the text-shadow. i'll try to patch that after i'm done with my merge
[00:43] <ali1234> hmm... well it didn't used to :)
[00:43] <brainwash> ochosi: text-shadow and most likely the background color, it's a bit lighter than the blue used in whisker menu and other panel items I think
[00:43] <ali1234> git diff was deliberately crippled to prevent it
[00:43] <ochosi> brainwash: could you show me a screenshot of that please?
[00:44] <ali1234> format-patch has the advantage of keeping the commit message and attribution
[00:44] <brainwash> let me just get the color codes
[00:44] <ochosi> brainwash: it's a gradient...
[00:45] <ali1234> sergio-br2: https://help.github.com/articles/using-pull-requests
[00:47] <ochosi> brainwash: ok, please pull from git, that should sort out most things now
[00:47] <sergio-br2> ok
[00:48] <ochosi> brainwash: fwiw, here whiskermenu and the indicators (and all other menus) look the same. also: whiskermenu isn't really a gtkmenu, so it's bound to look a little different...
[00:49] <brainwash> ochosi: http://en.zimagez.com/zimage/lelel.php
[00:49] <Unit193> ali1234: Then what was even the point of git diff??
[00:49] <ali1234> Unit193: it's for interactive display of changes only
[00:49] <Unit193> Bleh.
[00:50] <Unit193> patch -p1
[00:51] <ochosi> brainwash: that looks fine. the text-shadow is already fixed in git master now
[00:52] <ali1234> sergio-br2: also you may want to consider uploading a ssh key to github, it makes pushing much easier
[00:53] <brainwash> ochosi: ok, the color difference is minimal
[00:53] <brainwash> nobody will notice that
[00:54] <ochosi> it might be the same color-diff as between gtk2 and gtk3 menus (not noticeable)
[00:54] <ochosi> but yeah, whiskermenu is a different widget, so it's not impossible it looks slightly different
[00:55] <brainwash> places menu also
[00:55] <brainwash> I mean places menu highlight looks like the whisker one
[00:55] <brainwash> it's a darker, stronger blue
[00:56] <brainwash> but whatever... done :)
[00:57] <ochosi> feel free to propose a patch ;)
[00:57] <brainwash> no
[00:57] <brainwash> but what about the other shimmer themes?
[00:57] <brainwash> already patched?
[00:58] <ochosi> nope, will do that another time
[00:58] <ochosi> too tired now
[00:58] <brainwash> ok
[00:59] <brainwash> now we only need to solve the this remaining mystery: why do some indicators occupy 2 rows in deskbar mode?
[02:31] <sergio-br2> i did the request, but just now i realized that 64 icons are a little bit different from 128 icons :D
[02:32] <sergio-br2> subtle difference, i need my glasses
[07:18] <elfy> ochosi: saw a greeter update this morning - not sure what it was for - but if it was for login corruption it didn't work here - either cold boot nor restart
[07:19] <elfy> 201401142148~ubuntu14.04.1
[08:29] <ochosi> elfy: no, greeter was built 10hrs ago, branch was merged 8-9hrs ago
[08:33] <ochosi> elfy: i can ask for a new build now though, then you can test the fix today
[08:38] <ochosi> elfy: just requested a new build now, so whenever it's ready...
[08:38] <ochosi> https://code.launchpad.net/~lightdm-gtk-greeter-team/+archive/daily/+recipebuild/630903
[08:38] <ochosi> in case you wanna monitor it
[08:40] <ochosi> (but don't go crazy: http://xkcd.com/281/ )
[08:49] <elfy> ochosi: LOL
[08:50] <knome> hah
[08:50] <christoffer> haha
[08:50] <elfy> ochosi: I said to someone the other day I'm so laid back I'm a reflex angle - I'll not be doing that :p
[08:50] <ochosi> :]
[08:50] <knome> reminds me of the a-ha song 'move to memphis'
[08:51] <ochosi> reminds me of the song "bakerman" (by laid back)
[08:51] <elfy> knome: they had more than one song?
[08:51] <knome> elfy, sure, many *albums* worth of songs :)
[09:45] <elfy> ochosi: that works then - more or less, still get the cold boot corruption - but just for a short while after login, the bit I was most concerned about - the fragments of and old session don't show at all - thanks :)
[09:55] <ochosi> elfy: cold boot corruption? could you elaborate that a bit?
[09:57] <elfy> https://launchpadlibrarian.net/162094730/CAM00034.jpg
[09:57] <ochosi> oh, after login, that means that it happens when the root-pixmap gets displayed for a short while between the greeter and xfdesktop loading
[09:57] <elfy> yea - that's all 
[09:57] <ochosi> weird
[09:57] <ochosi> that looks bad though
[09:57] <ochosi> and shouldn't really happen
[09:57] <ochosi> have you rebooted once or twice
[09:57] <elfy> the other one - the bit I was really worried about doesn't happen
[09:57] <ochosi> just to be sure
[09:58] <elfy> upgraded/rebooted/shutdown/reboot/shutdown and then a restart
[09:59] <elfy> I agree it looks bad - but of the two issues - I know which I'd rather see
[10:00] <elfy> ochosi: you want me to comment on the bug?
[10:00] <ochosi> please do so
[10:00] <ochosi> well i plan to fix that corruption as well, i just have to find a way to reproduce it first...
[10:01] <elfy> :)
[10:01] <elfy> often the hard bit I guess
[10:34] <ochosi> elfy: i can reproduce the corruption when logging in – and that part also makes sense to me, as i explained earlier (nouveau mistreating the root pixmap) – but what i can't reproduce is the scrambled background at the login window
[10:35] <ochosi> that one looks totally fine for me now
[10:45] <brainwash> ochosi: any idea how the highlight of the play button in the indicator menu is implemented?
[10:45] <ochosi> not really, feel free to look into that
[10:46] <brainwash> so I took the ubuntu themes, removed the gtk3 part... and it still gets highlighted when I hover over the button
[10:47] <brainwash> theme engine specific?
[10:48] <ochosi> not sure
[10:48] <elfy> ochosi: you've misunderstood me 
[10:48] <ochosi> brainwash: first of all, i dont have any idea what weird custom widget they're using there (which would help enourmously for theming it)
[10:49] <elfy> the login screen is fine - you explained the thing I see between login and the desktop
[10:49] <brainwash> ochosi: ah got it, the glow is there by default, but gets overridden by greybird somewhere
[10:50] <brainwash> ochosi: maybe I'll find the right element, but those css files are huge =S
[10:50] <ochosi> elfy: oh, then the "screenshot" you linked to was misleading
[10:50] <ochosi> brainwash: better to read the source of the soundmenu, it's not that long
[10:50] <ochosi> brainwash: or even easier, use gtkparasite
[10:51] <brainwash> ochosi: thanks for the hints :)
[10:51] <elfy> ochosi: was just to show you what I seen between logging in and the desktop - sorry if it wasted your time
[10:51] <ochosi> elfy: hehe, no problem, i'm happy as long as the issue is fixed in the greeter (which it obviously is) :)
[10:51] <elfy> yep
[10:55] <ochosi> elfy: the other part has to be fixed in nouveau
[10:55] <elfy> k - that's fine with me 
[10:55] <elfy> as far as I am concerned the most important issue is dealt with - the fragments of old sessions - not seeing them at all
[10:56] <elfy> I didn't really think about it till I saw someone's e-mail address and infraction record sitting there :)
[10:57] <elfy> so that's taken 250 out of the bugs heat lol 
[11:00] <ochosi> :)
[11:00] <ochosi> well, happy i could fix it
[11:00] <elfy> so am I 
[11:01] <elfy> bbl 
[11:01] <elfy> ochosi: thanks :)
[11:02] <ochosi> np, yw :)
[11:05] <brainwash> does the settings manager ignore "always on top"?
[11:05] <ochosi> yeah, seems so
[11:06] <brainwash> ok, thanks for confirming
[11:06] <ochosi> probably because of its window-manager hints
[11:06] <ochosi> in fact, the label doesnt even change when you click it
[11:06] <ochosi> so it seems to be expected
[12:05] <brainwash> ochosi: gtkparasite is really a nice tool
[12:05] <ochosi> yup
[12:05] <ochosi> it is
[12:07] <brainwash> used it to identify gtkwidget for bug 1268243
[12:07] <brainwash> not sure how to use it for the sound menu
[12:07] <ochosi> run the panel from the terminal?
[12:08] <brainwash> mmh, worth a try
[12:08] <brainwash> https://github.com/shimmerproject/Greybird/blob/master/gtk-3.0/gtk-widgets.css#L2289
[12:09] <brainwash> can it be changed to the toolbar background color or even none?
[12:11] <brainwash> but I have no clue what this change might break :)
[12:13] <ochosi> well, test it :>
[12:13] <brainwash> this shade looks weird in synaptic anyway
[12:13] <ochosi> imo synaptic should be fixed
[12:14] <ochosi> but frankly i don't care too much as it's not installed by default anymore
[12:16] <Unit193> micahg: Guess you ended up without time?  Is there anything else I can do to make the process easier?
[12:18] <brainwash> ochosi: you could push the change, then we just wait until someone complains about it :D
[12:19] <ochosi> brainwash: anyway, the thing you propose doesn't make sense. it's basically switching styles to a flat toolbar look
[12:19] <ochosi> which would mean also changing gtk2
[12:19] <ochosi> and all because synaptic has some weird elements in its toolbar
[12:20] <ochosi> if you've found the widget structure, you can patch that single searchbox in synaptic, but the other way round isn't acceptable
[12:23] <brainwash> ochosi: ok, the difference in other gtk3 apps seems to be noticeable
[12:24] <brainwash> so the report is invalid then
[12:25] <micahg> Unit193: fell asleep, where's that bug
[12:25]  * knome pats micahg on the head
[12:26] <brainwash> ochosi: or better won't fix
[12:26] <Unit193> https://code.launchpad.net/~unit193/xubuntu-default-settings/session-fix/+merge/198177 thought knome ate it for a sec.
[12:26] <knome> mm, well i did eat quite some things today
[12:26] <knome> :d
[12:27] <Unit193> micahg: Built, tested.
[12:29] <micahg> I still wish it would clean up the old config, but I don't know offhand how it would do that
[12:29] <Unit193> Same, not without sed. :/
[12:39] <ochosi> micahg: you have until feature-freeze to improve the patch ;)
[12:39] <ochosi> but i think we need a live-session for the time being
[12:39] <micahg> yep, writing the same in my comments
[12:40] <Unit193> lightdm-set-defaults is gone, which could have been used.
[12:40] <ochosi> brainwash: add a synaptic-specific workaround that styles that searchbox like a toolbar is an option, but i won't do the work for that
[12:40] <ochosi> s/add/adding/
[12:43] <micahg> Unit193: One comment, LP: # closes bugs, not LP: unless something changed (I made the change to the main branch already)
[12:46] <Unit193> Thank you.  http://packaging.ubuntu.com/html/fixing-a-bug.html#documenting-the-fix agrees with you and I could have seen that by only looking at the last entry...
[12:49] <Unit193> Thanks for taking a look!
[12:50] <micahg> I'm also adding aline for automated translations updates to the changelog since those made their way in as well
[12:52] <micahg> Unit193: uploaded, please keep an eye on regressions and ping me if something comes up
[12:52] <micahg> I'll probably be hiding in -offtopic :)
[12:52] <Unit193> Sure thing, will do.
[12:52] <Unit193> Saaame. :P
[13:01] <brainwash> ochosi: lets ignore this "bug"
[13:01] <ochosi> brainwash: haha, this coming from you is just hillarious
[13:02] <ochosi> usually you like to nitpick about these tiny glitches, no?
[13:02] <brainwash> ochosi: any idea how to inspect the sound menu? once you've clicked the indicator, the inspector tool disappears
[13:02] <ochosi> afaik, the inspector opens a new window for each plugin
[13:02] <ochosi> but i haven't tested it personally in a longer time
[13:03] <brainwash> secretly I'm working on greybird-flat
[13:03] <ochosi> well, that's basically a merge of numix and greybird
[13:04] <brainwash> numbird or greyix
[13:04] <brainwash> so I get the parasite window for wrapper 2.0, but the sound menu needs to activated by mouse click
[13:05] <brainwash> so the inspector tool always captures the indicator icon in the panel and not the sound menu
[13:05] <ochosi> usually there were expanders to look down the widget structure (also of plugins that weren't open)
[13:06] <ochosi> bbl
[13:07] <brainwash> ochosi: it only captures the indicator alignment / image / label
[13:19] <brainwash> ochosi: did anything strange happen to the greeter drop down menus after the recent greybird changes? :)
[14:22] <brainwash> ochosi: strange icon highlighting eliminated (when cursor is moved from the opened sound menu back to the indicator icon in the panel) + play button glow http://lpaste.net/98529
[14:27] <jjfrv8> knome, ping
[15:02] <ochosi> brainwash: thanks for the soundmenu patch! if you wanna be in the commit-log as author, please do a merge-request on github
[15:02] <ochosi> i'm not 100% sure about my stance on the gtk-image-effect story
[15:02] <ochosi> so if you wanna do a merge-request, only do the menu:selected part
[15:03] <brainwash> the 2nd gtk-image-effect is causing the ugly effect
[15:05] <brainwash> leaving the gtk3 indicator menu and playing the cursor above the indicator highlights all icons in the menu
[15:05] <brainwash> so it needs to be addressed
[15:06] <brainwash> and just commit the changes you like, no need to list me as author
[15:09] <jjfrv8> bbiab
[15:14] <christoffer> knome, I must say that the application finder is pretty fantastic...have been missing that since Unity arrived.
[15:15] <christoffer> though it doesn't find the calculator for some reason
[15:16] <ochosi> christoffer: really? http://www.zimagez.com/zimage/screenshot-01152014-041600pm.php
[15:16] <christoffer> ochosi, I mean the <alt><f2>
[15:16] <christoffer> different gui
[15:17] <christoffer> but must be same application finder
[15:17] <christoffer> or?
[15:17] <ochosi> it only shows results as soon as they are unique
[15:17] <ochosi> hitting the "arrow-down" key expands the view
[15:17] <ochosi> (what you see in my screenshot)
[15:17] <christoffer> aha ok
[15:17] <ochosi> then you see the stuff filtered
[15:18] <christoffer> though typing "calculator" and pressing enter doesn't start the application
[15:18] <christoffer> even if it's unique
[15:18] <ochosi> because that's not the command
[15:18] <ochosi> as long as the searchglass is on the left (and no app-icon), you're executing a command
[15:18] <ochosi> and the command "calculator" doesn#t exist
[15:18] <christoffer> ok
[15:19] <ochosi> it's gnome-calculator
[15:19] <christoffer> can I expand the window with some key command?
[15:19] <ochosi> arrow-down
[15:19] <brainwash> christoffer: it's gnome-calculator
[15:19] <brainwash> oh
[15:19] <brainwash> tzzzz
[15:20] <christoffer> yea that is perhaps the fastest ...rebind arrow down to something better and press <alt><f2>calculator<arrow-down><enter><enter>
[15:32] <ochosi> brainwash: sound-indicator fix is pushed
[15:33] <slickymaster> afternoon all
[15:33] <brainwash> ochosi: and the icon thingy? any idea how to fix it properly?
[15:33] <ochosi> brainwash: i'm not sure yet i see the problem you're seeing, can you describe it again plz?
[15:33] <brainwash> ochosi: is the dim/highlight really needed?
[15:34] <ochosi> i think it can be helpful in some contexts
[15:34] <ochosi> but i don't see the problem in the indicators yet
[15:34] <brainwash> ochosi: uhm, let me try to make a screencast, brb
[16:24] <brainwash> ochosi: finally back, so here's the link http://www.youtube.com/watch?v=LgpWmS05iFA
[16:25] <brainwash> ochosi: and you need to fix the drop down menus in the greeter, they are broken after the recent removal of menu theme code
[16:26] <brainwash> text shadows once again
[16:33] <ochosi> brainwash: thanks for the screencast, i understand what you mean now
[16:33] <ochosi> i guess my current monitor is too bad, so i can't see it
[16:33] <ochosi> (although that's a bit odd, cause i can see it in the screencast)
[16:35] <ochosi> the greeter code is still in flux, so don't worry about glitches like that with daily
[16:35] <ochosi> i'm trying to finalize things for a release, then i'll release a greybird version that works with it alongside
[18:04] <brainwash> ochosi: did you try to load gtk3 indicators, so they are displayed in the greeter?
[18:04] <brainwash> I mean, does this actually work
[18:04] <brainwash> it did not for me
[18:28] <knome> jjfrv8, ping
[18:28] <knome> christoffer, iirc, gcalctool links to the calculator as well
[18:28] <knome> i guess you could add /home/user/.bin/ to PATH and then add a symlink for 'calculator' in that dir
[18:30] <christoffer> knome, gcalctool works in unity but not xubuntu
[18:30] <knome> hmm, right, seems it's dropped in 13.10...
[18:30] <knome> it used to work in xubuntu as well
[18:32] <christoffer> gno<enter>ca<enter> is the quickest way :)
[18:32] <christoffer> only adding a custom symlink for "calc" would be quicker I assume
[18:32] <christoffer> =)
[18:34] <christoffer> I'm actually thinking about remapping my caps-lock key...I see more and more people doing that. Not sure if it should be another <enter> or <backspace>
[18:34] <christoffer> backspace is far away but when you write text/code a left hand side <enter> would be nice.
[18:35] <christoffer> and just make sure you never mistype
[18:38] <knome> binding it to the "open right-click/application menu" might be useful
[18:40] <christoffer> yea that's another option...still leaning towards the symmetry of an extra enter key
[18:40] <knome> nah, i don't think one should replicate anything
[18:40] <knome> another good idea is binding it to ctrl+tab (changes tab in firefox and other apps)
[18:41] <christoffer> hmm <alt Gr> might be really good to rebind 
[18:41] <christoffer> when writing code
[18:42] <brainwash> don't abuse the devel channel, join -offtopic :)
[18:51] <knome> brainwash, there's only one response to that...
[18:51] <knome> brainwash, please use -offtopic to advertise other channels
[18:51] <knome> ;)
[19:20] <brainwash> anyone familiar with SRU reports? we need one for bug 1222021
[19:21] <brainwash> it's issue #1 in saucy, affecting many many people
[19:22] <brainwash> a patched debian package won't be available anytime soon, so we will have to ship our own version in the meantime (currently available via noskcaj's PPA, link in the report)
[20:59] <elfy> bluesabre: any update on menulibre - if I've gone shout at piskie instead :p
[21:00] <knome> elfy, he said earlier today everything should be in debian in a week, and in ubuntu at the beginning of feb
[21:01] <elfy> oh right ok - missed that 
[21:01] <elfy> knome: ty 
[21:01] <Unit193> Hopefully two days worth of development until it's ready though.
[21:02] <knome> elfy, you couldn't have missed that; it wasn't on this channel
[21:02] <elfy> oh 
[21:02] <elfy> should be in this channel as well then
[21:03] <knome> probably... but that happened in a middle of a different discussion
[21:38] <brainwash> bluesabre, ochosi: the new parole dev version uses the "play" icon as background picture, but it lacks the functionality of a "play" button
[21:38] <brainwash> people might get confused
[21:39] <brainwash> scenario: you watch a video and it ends, you want to watch it again and there is this play icon in the middle of the center.. you press it, just like you would do on youtube and co, but nothing happens
[22:04] <jjfrv8> knome, ping pong
[22:05] <knome> jjfrv8, hello :)
[22:05] <jjfrv8> Hi, a few questions?
[22:05] <knome> always
[22:05] <jjfrv8> about bug 1207493, I see it is marked as "fix released", does that mean it will make it into the SRU next month with no other changes?
[22:06] <knome> yep
[22:06] <knome> well,
[22:06] <knome> there's a problem with that; the SRU is broken
[22:06] <knome> we need to look at it
[22:07] <knome> i will do that when i have time and then adjust the bug as needed
[22:07] <jjfrv8> the problem with the initial page missing the graphics, you mean?
[22:07] <knome> i guess that was it
[22:07] <knome> it's probably a trivial thing to fix
[22:08] <jjfrv8> skellat was stumped on how to fix it last I checked
[22:08] <knome> i guess i know more of that then ;)
[22:08] <jjfrv8> his PPA works but the version in -proposed does not
[22:08] <knome> for me, it looks pretty straightforward (disclaimer: i haven't really looked at the package)
[22:09] <jjfrv8> ok, but if you can't fix it, will it go in the way it is now?
[22:09] <jjfrv8> at least the content would be correct finally
[22:10] <knome> as long as we have done a new upload with the fixed package
[22:10] <knome> yes, even if we didn't fix the graphical glitch, the content will be up-to-date
[22:10] <jjfrv8> I can live with that
[22:11] <jjfrv8> next question: no one has responded to your call on the ML yet but there were two guys who volunteered a while back
[22:11] <jjfrv8> both said they had web design experience
[22:11] <knome> that's barely needed, but if they are willing to help with the docs, that's good
[22:11] <jjfrv8> do you think I should contact them directly to ask if they're interested in helping out with the tour and about stuff
[22:11] <knome> slickymaster replied on the channel and will be working on the mugshot documentation
[22:12] <knome> i've already talked with bluesabre about it as well
[22:12] <knome> i also asked david to send a mail to the list to notify he's starting with that
[22:12] <knome> contacting directly is good
[22:12] <knome> if you do that, you can optionally CC me
[22:13] <jjfrv8> will do
[22:13] <jjfrv8> is whiskermenu still under consideration to replace alacarte by default?
[22:13] <knome> whiskermenu is not a replacement for alacarte
[22:14] <knome> menulibre is a replacement for alacarte, and as long as it is ready and landed before the feature freeze, we will be using it
[22:14] <knome> whiskermenu is an optional replacement for the applications menu on the panel
[22:14] <jjfrv8> I thought that was alacarte
[22:15] <knome> nope :)
[22:15] <knome> alacarte is a menu editor like menulibre
[22:15] <knome> so that's why whiskermenu is somewhat tied to the panel layout change
[22:15] <jjfrv8> but is it going to stay optional?
[22:16] <knome> that's to be decided
[22:17] <jjfrv8> reason I ask is that there are a lot of references to the applications menu in the current docs
[22:17] <knome> if it's optional, then we need no changes in the documentation whatsoever
[22:17] <jjfrv8> right
[22:17] <knome> yes, i'm aware of that...
[22:17] <knome> fortunately, we are using the xubuntu icon to denote the menu
[22:17] <knome> so we don't need to change the wording in *too* many places
[22:18] <jjfrv8> yup
[22:18] <knome> as long as the categories are the same, and we use the xubuntu icon as the menu button
[22:18] <knome> but the reality is
[22:18] <knome> we will most probably change the panel layout anyway
[22:18] <knome> with that being done, i think updating relevant parts to say whiskermenu is easy enough
[22:18] <jjfrv8> any idea when it will be firmed up?
[22:19] <knome> once ochosi gets a final proposal up, and we've discussed/voted on it on a team meeting
[22:19] <knome> we probably should try to do that at the latest in two weeks
[22:19] <jjfrv8> sounds good
[22:20] <jjfrv8> is there a trusty branch yet for the docs to start working on?
[22:20] <knome> yep
[22:20] <knome> it's what is now lp:xubuntu-docs
[22:20] <jjfrv8> I'll go ahead and pull that then
[22:22] <jjfrv8> that's it for now, thanks
[22:22] <knome> np :(
[22:22] <knome> :) that is
[22:22] <knome> tell me if you have any problems with anything
[22:22] <jjfrv8> sure
[22:22] <knome> or if you are concerned about running out of time to prepare docs for something, poke me and i'll try to hurry things up
[22:23] <jjfrv8> k
[23:10] <bluesabre> ochosi, brainwash: so much scrollback, any luck with the gtk3.10 menuitems?
[23:10] <bluesabre> it also affects Numix
[23:18] <brainwash> bluesabre: the gtk3 indicator menus look fine now (greybird git)
[23:18] <brainwash> in trusty
[23:18] <bluesabre> great!
[23:18] <brainwash> just some strange icon highlighting issue remaining
[23:19] <brainwash> but the recent changes to fix the indicator menus broke the drop down menus in lightdm-gtk-greeter :)
[23:20] <brainwash> "broke" might be the wrong word, the fix added text shadows
[23:21] <brainwash> bluesabre: did you read my concern regarding parole's background picture?
[23:21] <brainwash> the "non functional" play button
[23:27] <ochosi> brainwash: it's just a logo in parole. it was never intended as a playbutton (and it would be a useless duplication anyway
[23:28] <brainwash> ochosi: but it looks like a play button..
[23:28] <ochosi> i haven't tested the gtk3 indicators
[23:29] <brainwash> ok, I'll try to debug this
[23:30] <brainwash> I really want to get the gtk3 indicator menus completely fixed, do you think that the icon highlight effect can be solved differently?
[23:31] <ochosi> not sure yet, i was away until now, so no new insights ;)
[23:31] <brainwash> the unity themes do not use these dim/highlight effects
[23:32] <ochosi> it's possible that the indicators don't work in the greeter anymore because their loading mechanism was changed
[23:32] <ochosi> so basically the changes of the indicator-plugin would have to be ported to the greeter, i suppose (if they're not working now)
[23:32] <ochosi> not sure i wanna open that pandora's box
[23:33] <ochosi> still have lots of other things to fix in the greeter, e.g. fix wallpaper drawing in gtk2
[23:33] <brainwash> mmh, true.. they removed the dbus activation and switched to upstart magic
[23:38] <brainwash> ochosi: mmh, I got some more stuff to share, but I better don't bother you with more greeter glitches :)
[23:40] <brainwash> so I'll try to fix it myself and provide patches or report it eventually
[23:41] <ochosi> :}
[23:41] <ochosi> well my todo-list for the greeter looks like this:
[23:41] <ochosi> 1) fix gtk2 wallpapers (so that we're in release-ready state again)
[23:41] <ochosi> 2) finish language-menu patch
[23:42] <ochosi> and anyway, according to someone on the ML, the greeter's biggest glitch is that its "ascetics"(sic!) look "ugy"(sic!)
[23:42] <brainwash> -> 2) really show "en_US" or just "en"?
[23:43] <ochosi> "en_US" ofc
[23:43] <brainwash> ok
[23:43] <ochosi> it already works, it just doesn't get updated properly when switching users via the combobox
[23:44] <brainwash> yeah, nothing bad about the full string "en_US", but usually it gets shortened to just "en" (gnome-screensaver,..)
[23:48] <knome> do you think there is any reason why we couldn't just show the two first letters?
[23:49] <knome> (eg. drop the countrycode)
[23:49] <ochosi> knome: well since the menu offers all of those choices, it seems weird not to show them
[23:50] <ochosi> e.g. if you only have english installed, you still get 4 or 5 options
[23:50] <knome> sure... but isn't the menu also able to show the selected one?
[23:50] <ochosi> and in case you care about using en_AU for some reason, it'd be quite the usability loss to cut those two chars
[23:50] <knome> i rather see "fi" than "fi_FI"
[23:50] <ochosi> the menu always shows the selected one
[23:50] <ochosi> yeah, but the default is "fi"
[23:50] <ochosi> or "en"
[23:50] <knome> (because, being honest, there is no "fi" outside "FI")
[23:51] <knome> aha
[23:51] <ochosi> only variants get country-codes
[23:51] <ochosi> so normally, it'd say "en" or "de" or "fi", unless you use a specific variant
[23:51] <ochosi> and then i think it's ok to show them
[23:51] <knome> i'm still not sure why the countrycode is really important
[23:51] <ochosi> currency and units
[23:51] <ochosi> (for the more international languages)
[23:52] <knome> right, but it's a selection you pretty much do once
[23:52] <knome> and then forget about it
[23:52] <knome> example: jackson uses en_AU, and keeps on using it.
[23:52] <knome> also, what if all of my locale strings aren't fi?
[23:52] <knome> or, en
[23:53] <knome> don't seem to have that setup on the laptop, but on my desktop, the main locale is en, but some units are fi
[23:53] <knome> the greeter is failing to show me that anyway!
[23:53] <knome> (and no, i don't think that's a completely rare setup, many people want the interface in english but units in other language)
[23:54] <knome> so basically, that item is only able to show, what, LANG/LANGUAGE
[23:54] <knome> so your argument on "being able to know which units are in use" is faulty
[23:54] <knome> because that tells nothing about the units
[23:55] <knome> feel free to prove me wrong.
[23:55] <brainwash> how about a vote in the next meeting
[23:56] <knome> i don't think we need a vote, we need a sane choice
[23:56] <bluesabre> sane choice is whatever the language code is specified as
[23:56] <brainwash> both are valid options
[23:57] <bluesabre> we should take what we get and pass it along
[23:57] <bluesabre> en_US -> en_US
[23:57] <bluesabre> (my opinion anyway) ;)
[23:58] <knome> bluesabre, from my pov, the problem with that thinking is that it implies more things than it possibly may be
[23:58] <knome> in my desktop, example using en_GB would imply i'm using british units
[23:58] <brainwash> make it configurable :P
[23:58] <knome> even if in fact, i'm using finnish
[23:59] <knome> bluesabre, what can we learn from this?
[23:59] <knome> bluesabre, we can be sure the shown string can only imply the *language*
[23:59] <bluesabre> knome does not like his native toungue
[23:59] <knome> do you need an example why?