[06:03] knome: The product of this night's work on the docs - and yes, one can avoid *translating* it twice, I may not have got you right at first: http://paste.openstack.org/show/pgTMDd937sYjZhUaeO5K/ [06:06] This one puts PDF links at the top of every page that has a normal header (i.e. not the credits-license one), if they were generated before. [06:09] That is, at build time - if no PDF creation, no links. [08:12] knome: ping [08:41] ochosi, Do you know what else i'd have to add to the sgt-puzzles-launcher before we could start using it? [08:41] hey Noskcaj [08:41] i haven't had time to try it yet [08:41] hey [08:41] It's just a 6x6 grid of the games with there icons [08:42] yeah [08:42] i saw Unit193 mentioned some concerns, have you addressed those already? [08:42] All the sgt-puzzles are installed at once, so i was hoping a dep in the packaging would be enough [08:43] It definitely needs it's own icon, but other than that and maybe translation support, it should just be a case of packaging it and making the sgt desktop files notshowin xfce [08:44] It'd still should error or check for the applications though. [08:45] yeah, that ^ makes sense to me [08:45] another thing that would be nice is type-ahead search for the game-name [08:45] currently you can only navigate with the cursor buttons [08:46] i presume you're using gtkbuttons there, maybe an iconview would be better, it should have that feature automatically [08:46] or you could filter the results on keyboard-typing ;) [08:46] I'll get the checks in soon, but search doesn't really work with how i've designed it. i'll have a look though [08:47] It's just gtkbuttons so far, designed in glade because i'm a crap coder [08:49] right [08:49] i haven't looke at the code yet tbh [08:49] g'day flocculant [08:49] morning ochosi :) [08:50] Noskcaj: another easy fix is closing the launcher with either ctrl+w, ctrl+q or Esc [08:53] As-is it doesn't handle close well, right. [08:57] Noskcaj: still, as bluesabre said, it's a good start considering you haven't coded too much yet. so just keep on poking! [11:03] ochosi, pong [11:05] hey [11:05] oh bah, krytarik's not here [11:06] afternoon [11:06] hello flocculant [11:06] ochosi, did you have something in mind? [11:06] knome: i've just been toying with a few more LO icons [11:07] aha [11:07] much of it is just resizing icons that i've already refreshed from 24 to 16px [11:07] so nothing spectacular there [11:07] right [11:07] maybe we could take another peek at the status page [11:07] sure [11:09] maybe you're right - maybe we need "tabs" [11:09] * knome goes looking at that now [11:10] yeah, i mean we can keep the page as is [11:10] it's really a lot better than status.ubuntu.com already [11:10] good [11:10] but i think it can still be improved (like everything, always) [11:10] yes too [11:10] for instance, i was wondering whether LP provides the data for the burndown graphic [11:11] not that we as a team *really* need it, but it'd be a nice starting image/graphic for the developer area [11:11] showing that there's stuff going on in a timeline sort of view [11:11] it doesn't [11:11] right, so status.ubuntu was collecting/calculating that on its own then, i presume [11:11] there is no history for LP, you got to gather the data yourself [11:11] yse [11:11] *yes [11:12] humm [11:12] let's put that to the end of the todo-list then :) [11:12] let's start with the lower-hanging fruit [11:12] to the worst we can always show progressbars instead [11:12] aren't we doing that already? [11:13] no, i was still thinking of the entry page for the developer area [11:14] rrright [11:14] i know that needs some IS interaction, so it might take time to land, but we could still plan for it [11:15] that sounds like a $lot more work [11:15] well for one we could make the "tracker" link in the developer area point to your page [11:15] cause status.ubuntu is dead [11:15] so it's not really useful [11:15] because even if i can feed the data easily out from the tracker, there needs to be something that outputs it on the website [11:16] well that's the other question - can we have a space where it is under the IS control in xubuntu.org? [11:16] sure, then all code needs to go through IS, but meh [11:16] i thought of just rendering it to an image when there's an update [11:16] the status bars? [11:16] yeah [11:16] right... [11:17] we can also add an iframe ;) [11:17] huho [11:17] i kind of understand your point, but otoh, don't [11:17] people can just go to the tracker to see the status [11:17] the progress bars are useless as is on the developer area [11:18] you need to follow-up on the details anyway [11:18] knowing we're "23% towards 15.10" doesn't tell a lot [11:19] yeah, it's just a visual gimmick there, i know that [11:19] but a meaningful image makes ppl click links [11:20] * knome shrugs [11:20] anyway, let's focus on the status page itself instead [11:20] ;) [11:20] so what was your thought re:tabs again? [11:20] i'm working on it [11:21] oh ok [11:21] i'll just give you some time for that then and get some other stuff done meanwhile [11:21] mhm [11:22] also, just a small thought: maybe we could also put the "total progress" as the first item in the list [11:22] i know it's the sum, so that makes sense at the end [11:22] * knome shrugs [11:22] :P [11:22] still, it also makes sense as the first item [11:44] if you want to do it like that, then i need to change the code [11:44] the total isn't saved anywhere [11:44] (maybe it should..) [11:44] do it like what? [11:44] ah [11:44] you mean put the total first [11:44] yes [11:44] right, then keep it where it is [11:45] see the status now [11:45] has tabs [11:45] nice [11:46] what about color-coding the inprogress/todo/done in the expanded overview? [11:46] (just the status column on the right) [11:47] or the whole line with a very pale version of the main status color [11:49] flocculant: wanna start setting up your LP account? [11:50] (just added you to x-qa) [11:50] ochosi, i thought about that, but i'm not really sure [11:50] at least the whole row would be obtrusive [11:50] mhm, maybe [11:51] then maybe just try to add a bg color for the status column [11:51] (maybe even that is too obtrusive, but it'd be nice to know/see) [11:51] for the details page it'd definitely help [11:51] another thought is to append something to the item row [11:52] yeah, could work just as well [11:55] there you go [11:55] i don't know if that's useful [11:56] i was actually thinking that it might be more useful to color the status text [11:56] right, that could work too [11:56] question is whether the text "inprogress" etc is still needed then [11:56] if things are color-coded anywa [11:57] y [11:57] looky now [11:57] definitely better! [11:57] ochosi: you found it then ;) [11:57] and appending might still be worth a try [11:57] though now it's a bit too colorful on the details page [11:57] or at least it doesn't help me much... [11:57] flocculant: sure ;) just wanted to wait until we were both around [11:57] :) [11:58] knome: yeah, on the overview it's good, details not that much [11:58] actually, it's more or less useless on overview ;) [11:58] the column is too far away [11:58] knome: yeah, that's what i mean with "appending" [11:59] look now [11:59] would something like that work? [11:59] i mean, just color todo/blocked [11:59] yeah [11:59] maybe a bit less colorful red [12:00] it's a bit funny though that done is grey-strikethrough ;) [12:00] but yeah, maybe better than making it green tbh [12:00] not at all.. [12:00] "don't worry about this" [12:00] :) [12:00] yeah [12:00] no actually i think this works wel [12:00] l [12:01] ok, done with the color tweaking now [12:02] another idea... [12:02] prepend "TODO: " to the todo items [12:02] like this [12:03] then the color might not be needed (for the whole row) [12:03] like this [12:03] hm, dunno, the "TODO" is a bit of a duplication there and the color is not as easy to see as before [12:03] because it's just four letters instead of (usually) more [12:04] then would it not be better to remove the status column and add the status to all the work items [12:04] yeah, sort of [12:04] ochosi, refresh [12:04] flocculant, that might be an option [12:04] heh, flashier color :) [12:04] though i don't think we need a status for every row [12:04] i think it's useful enough [12:04] and not too obtrusive [12:05] the colors do it well enough for my taste [12:05] could also b smaller font [12:05] i wouldn't need the status column at all as it is now [12:05] it's pretty clear what is done and what's not [12:05] yes [12:05] lookie now [12:05] or refresh [12:05] that might be my favorite [12:06] can also prepend blocked items with "BLOCKED" [12:06] mhm, nice [12:06] makes it look more like a tag or label [12:07] gotta step out for 10mins or so [12:07] brb [12:27] ok, enough of this hacking now [12:31] looks better like that imo [12:44] knome: well done [12:45] also, is there a style for "postponed" yet? [12:45] nope [12:46] (could be like "done" but with "Postponed:" prepended) [12:46] * knome shrugs [12:46] i'll look at that the next time [12:46] sure [13:10] it's looking really good [13:11] i just modified the tabs so that you can actually link to either tab and get that tab opened on load [13:12] (also note that the tabs remember the "state", eg. you can go to details and then come back to "overview" and it keeps stuff you had expanded, expanded) [13:19] ochosi, there you have it, postponed style [13:19] (lookie under web) [13:24] hey bluesabre [13:24] hey ochosi [13:24] knome: yeah, looks nice! [13:24] bluesabre: still on holidays? :) [13:25] ochosi: pretty much, just checking in here for a few minutes this morning [13:25] gotta bake a blackberry cobbler this morning as promised ;) [13:26] heh, lovely [13:26] btw, i marked my artwork items done, since they're all just pending in terms of getting uploaded [13:27] sounds good to me [13:27] maybe we'll see that new ubiquity this week [13:28] that'd be good too [13:28] oh, and a xfpanel-switch release ;) [13:28] yup [13:28] that'll be here probably monday [13:29] gotta review the build system to make sure its up to snuff for release [13:29] ochosi, also now you can see that POSTPONED items aren't counted towards the progress [13:29] in good or bad [13:29] which is, IMO, the only right way [13:30] knome: that sounds good to me [13:30] knome: indeed, that sounds right [13:30] status.u.c didn't do that [13:31] ochosi, what do you think of the following idea: [13:31] mark blocked items with the BLOCKED tag [13:31] remove the tag from TODO [13:31] add the tag to INPROGRESS [13:32] guess i'd have to see [13:32] ok, just a moment, it's a trivialish css operation now [13:33] refresh [13:33] i think it makes more sense logically [13:34] because obviously, all items here are "TODO" [13:34] just with different statuses [13:34] this way the blocked items also get more weight and prominence in the list [13:34] yeah, puts the (visual) stress on WIP instead of TODO [13:34] mhm [13:34] which is desirable [13:34] or at least is from my POV [13:34] yeah [13:34] this way it's very easy to see what needs unblocking [13:35] woops, gotta run [13:35] hha [13:35] be back in 30mins [13:35] have fun :) [13:35] ok [13:35] u2! [13:35] will do [13:35] also thanks for reminding me music exists :P [13:54] bluesabre, http://xstatus.knome.fi/#tab-details/bluesabre [13:54] bluesabre, http://xstatus.knome.fi/#tab-details/ochosi [13:54] eh, [13:54] ochosi, http://xstatus.knome.fi/#tab-details/ochosi [14:07] knome: nice, almost done :) [14:07] that's a really useful view [14:07] yes [14:08] would be nice to integrate that back into LP somehow [14:08] also, http://xstatus.knome.fi/#tab-overview/expand [14:08] into the personal page overview [14:09] nice, much cleaner [14:09] (no, see the url without /expand) [14:09] into this page, i meant: https://launchpad.net/~ochosi [14:09] it would be a resource hog, they'd likely need to create db views for all people and look through all specifications [14:09] mhm, nice [14:09] there's no way to know which specs you are involved with until you check all the specs [14:10] yeah, i guess [14:10] or check all specs where you/any of the teams you're a member of is in some of the fields [14:10] but since it seemed like we're building our own frontend to (parts of) LP almost... [14:10] so yeah, it's not sustainable by all means [14:10] sure [14:10] we are [14:10] good lord they have an API for that [14:12] :) [14:39] added a dropdown [14:39] so you can now pick a nick from the UI [14:41] do whatever you wish with it :P [14:42] nice [14:42] that's pretty cool too [14:50] knome: you could (if you wanted to) style that combobox too to fit in with the rest of the page though ;) [14:51] naah [16:35] very nice link: http://xstatus.knome.fi/#tab-overview/expand didn't know about it [17:06] jjfrv8: ok, in the file-manager-window page i'd add the right-click menu (to show / hide sidepane items) [17:07] http://lists.alioth.debian.org/pipermail/pkg-xfce-devel/2015-July/020878.html - https://bugzilla.xfce.org/show_bug.cgi?id=12012 [17:07] bugzilla.xfce.org bug 12012 in General "xfce4-session configured with --disable-legacy-sm breaks qt4 integration" [Normal,New] [17:08] jjfrv8: other than that, that page looks great! [17:14] jjfrv8: the working with files and folders isn't finished, but what's there looks good! lemme know when that's done and i can review the rest of it [20:20] hello what's up [20:22] hello [20:27] Howdy. [20:29] jcjordyn120, are you looking for something or somebody? [20:30] no knome [20:30] jcjordyn120, what brings you here then? :) [20:31] just seeing what up with the xubuntu development. knome [20:32] ok; it varies how quiet/loud it is here, but feel free to ask or comment if there's anything [20:33] okay knome [20:34] krytarik, hello! [20:34] knome: Howdy. [20:34] o/ [20:34] krytarik, avoiding translating twice was the (other) thing i thought about - great to have that sorted [20:35] krytarik, what's VPATH? [20:35] krytarik, and what's translate: | get-translations ? [20:35] hahaha [20:36] and for the pdf linking, i'd rather use something else than sed [20:36] practically something that would just be hidden from the PDF [20:37] but would be part of the documentation [20:37] that would also allow a (better) description (that can be trasnslated) [20:38] and while
    kind of is most semantic, i'd likely just drop it all inside a

    [20:38] (avoid most of the CSS and all) [20:39] knome: http://www.gnu.org/software/make/manual/make.html#Directory-Search - and - http://www.gnu.org/software/make/manual/make.html#Prerequisite-Types [20:40] right [20:43] whats up with that QA position [20:43] jcjordyn120: What do you mean "what's with it"? f has it. [20:43] jcjordyn120, a person by the nick "flocculant" is being appointed as the QA lead if there is no objections [20:44] jcjordyn120, the QA lead coordinates the testing and quality assurance related tasks for xubuntu [20:44] oh ok [20:44] why is abiword and gnumeric included with xubuntu instead of libreoffice suite [20:44] I'm not going to remember that nick very well, sigh. [20:45] jcjordyn120: It isn't, in Wily. [20:45] oh i was talking about vivid [20:45] vivid is done with, wily is the target. [20:46] oh ok, so what is included with wily [20:47] Libreoffice. [20:47] okay [20:49] Unit193, basically, you just xsltproc to a .fo file, then use fop to make a PDF out of that [20:49] Unit193, in our case, using the PDF customization layer [20:50] Unit193, done. [20:52] (Thinking about adding it to my daily build script.) [20:53] sure [21:12] hello can you here me, my internet went out [21:12] jcjordyn120, yes, we can read you. [21:13] oh thanks, i by mistake flipped my wifi switch off [21:17] UTC'ized the tracker [21:25] evening all [21:26] knome: looking forward to the date switch and the status tracker burndown's second line ;) [21:26] hey ochosi [21:27] ochosi, it already happened when the tracker thought it was supposed to follow UTC+3 time [21:27] oh [21:27] crap, i missed it [21:27] but i of course fixed it and removed the other line ;) [21:27] :) [21:27] yeah, i don't intend to keep it this way [21:27] hm, planning to rotate those progressbars by 90°? [21:27] the problem is that i don't really want to create a SVG [21:27] yeah [21:27] and i don't know how i could draw the burndown line [21:27] hmm, css maybe? [21:28] or js [21:28] (i know php could draw it) [21:28] hah [21:28] with html5 canvas, maybe [21:28] i should know what the area for the burndown chart was then [21:29] the other option is some hacking with css rotation [21:30] yeah that sounds about ok [21:30] "about ok" [21:30] :) [21:30] that sounds like headache [21:30] well, it could be a lot of work [21:30] is what i mean [21:30] but the result would likely work [21:30] though it might be less than canvas [21:30] meh [21:30] the problem is [21:30] i should figure out the printing of the vertical lines next [21:31] eg. store start/end days somewhere [21:31] indeed, that's likely more important than the burndown line [21:31] the burndown line is actually quite trivial after that, i just figured [21:32] right [21:32] hmm, have you ever exported to xpm from inkscape? [21:32] no [21:32] * knome gets some puke to his mouth from the thought alone [21:33] yeah, it's quite terrible, i know [21:33] i was considering to port parts of greybird's wm theme to svg [21:33] but then there seems to be little benefit because of the xpm-iness [21:33] heh [21:35] what was the 15.04 release day [21:36] and what is the scheduled 15.10 release day [21:43] ochosi, SAMBA! [21:43] ochosi, or in other words, look at the burndown page [21:43] :D [21:58] ochosi, well, there you have it [21:58] ;) [21:58] now for the burndown line [21:58] nice that didn't take that long :) [21:58] now for the burndown line [21:58] (still waiting for that date-change) [21:58] 2 more hours [21:58] though i could add some fake informácion [21:59] actually, first [21:59] some other stuff [21:59] you'll see soon [21:59] * knome sighs in advance [22:00] * ochosi waits patiently [22:01] ochosi, refresh [22:01] 10% line [22:01] i see a line [22:02] yes [22:02] it's at 10% [22:02] k [22:02] now for the rest [22:02] * knome hacks the css linear-gradient background [22:03] 10 + 20 [22:03] well, at least should be [22:03] that doesn't look unifrom [22:03] *form [22:03] maybe my eyes just fail me [22:03] let's see 30 [22:04] that looks better [22:04] haha [22:04] ok [22:04] there's something fishy with the bar [22:08] *there* we go [22:11] yup [22:11] that looks good [22:11] let me try something completely different [22:12] that [22:12] could be subtler [22:12] but believe me or not, that's half easier than the previous one [22:13] there [22:13] could be even more subtler [22:13] now? [22:15] huh what [22:15] quite fat lines, but the gradient is nice [22:15] ok [22:16] it's a visual thing [22:16] there aren't lines [22:16] there are just 10 gradients [22:16] oh [22:16] right [22:16] maybe subtler? [22:16] haha, it's already 2.5% black [22:16] but ok [22:17] now? [22:17] still? [22:17] still looks like 2px lines, but my eyes might be tired [22:17] well, yeah [22:17] there seems to be some glitch [22:18] it's %'s anyway [22:18] and i guess the effect is stronger with the low brightness i'm using atm [22:18] now the gradients is barely visible [22:18] *are [22:18] but the lines are definitely still "fat" [22:18] when i pump it up, the gradients fade out a bit [22:19] * knome returns to the lines [22:19] for now, at least [22:19] ok, the burndown line now [22:19] * knome sighs [22:19] i think i need js there [22:20] * knome sighs again [22:21] whoops, where did the burndown tab go? [22:21] oh, it's at the bottom [22:22] what? [22:22] ok, something failed [22:22] only my js. [22:22] my bad! [22:22] think i'll figure this out with greasemonkey