| krytarik | 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:03 |
|---|---|---|
| krytarik | 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:06 |
| krytarik | That is, at build time - if no PDF creation, no links. | 06:09 |
| ochosi | knome: ping | 08:12 |
| Noskcaj | ochosi, Do you know what else i'd have to add to the sgt-puzzles-launcher before we could start using it? | 08:41 |
| ochosi | hey Noskcaj | 08:41 |
| ochosi | i haven't had time to try it yet | 08:41 |
| Noskcaj | hey | 08:41 |
| Noskcaj | It's just a 6x6 grid of the games with there icons | 08:41 |
| ochosi | yeah | 08:42 |
| ochosi | i saw Unit193 mentioned some concerns, have you addressed those already? | 08:42 |
| Noskcaj | All the sgt-puzzles are installed at once, so i was hoping a dep in the packaging would be enough | 08:42 |
| Noskcaj | 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:43 |
| Unit193 | It'd still should error or check for the applications though. | 08:44 |
| ochosi | yeah, that ^ makes sense to me | 08:45 |
| ochosi | another thing that would be nice is type-ahead search for the game-name | 08:45 |
| ochosi | currently you can only navigate with the cursor buttons | 08:45 |
| ochosi | i presume you're using gtkbuttons there, maybe an iconview would be better, it should have that feature automatically | 08:46 |
| ochosi | or you could filter the results on keyboard-typing ;) | 08:46 |
| Noskcaj | 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:46 |
| Noskcaj | It's just gtkbuttons so far, designed in glade because i'm a crap coder | 08:47 |
| ochosi | right | 08:49 |
| ochosi | i haven't looke at the code yet tbh | 08:49 |
| ochosi | g'day flocculant | 08:49 |
| flocculant | morning ochosi :) | 08:49 |
| ochosi | Noskcaj: another easy fix is closing the launcher with either ctrl+w, ctrl+q or Esc | 08:50 |
| Unit193 | As-is it doesn't handle close well, right. | 08:53 |
| ochosi | Noskcaj: still, as bluesabre said, it's a good start considering you haven't coded too much yet. so just keep on poking! | 08:57 |
| knome | ochosi, pong | 11:03 |
| ochosi | hey | 11:05 |
| knome | oh bah, krytarik's not here | 11:05 |
| flocculant | afternoon | 11:06 |
| knome | hello flocculant | 11:06 |
| knome | ochosi, did you have something in mind? | 11:06 |
| ochosi | knome: i've just been toying with a few more LO icons | 11:06 |
| knome | aha | 11:07 |
| ochosi | much of it is just resizing icons that i've already refreshed from 24 to 16px | 11:07 |
| ochosi | so nothing spectacular there | 11:07 |
| knome | right | 11:07 |
| ochosi | maybe we could take another peek at the status page | 11:07 |
| knome | sure | 11:07 |
| knome | maybe you're right - maybe we need "tabs" | 11:09 |
| * knome goes looking at that now | 11:09 | |
| ochosi | yeah, i mean we can keep the page as is | 11:10 |
| ochosi | it's really a lot better than status.ubuntu.com already | 11:10 |
| knome | good | 11:10 |
| ochosi | but i think it can still be improved (like everything, always) | 11:10 |
| knome | yes too | 11:10 |
| ochosi | for instance, i was wondering whether LP provides the data for the burndown graphic | 11:10 |
| ochosi | not that we as a team *really* need it, but it'd be a nice starting image/graphic for the developer area | 11:11 |
| ochosi | showing that there's stuff going on in a timeline sort of view | 11:11 |
| knome | it doesn't | 11:11 |
| ochosi | right, so status.ubuntu was collecting/calculating that on its own then, i presume | 11:11 |
| knome | there is no history for LP, you got to gather the data yourself | 11:11 |
| knome | yse | 11:11 |
| knome | *yes | 11:11 |
| ochosi | humm | 11:12 |
| ochosi | let's put that to the end of the todo-list then :) | 11:12 |
| ochosi | let's start with the lower-hanging fruit | 11:12 |
| ochosi | to the worst we can always show progressbars instead | 11:12 |
| knome | aren't we doing that already? | 11:12 |
| ochosi | no, i was still thinking of the entry page for the developer area | 11:13 |
| knome | rrright | 11:14 |
| ochosi | i know that needs some IS interaction, so it might take time to land, but we could still plan for it | 11:14 |
| knome | that sounds like a $lot more work | 11:15 |
| ochosi | well for one we could make the "tracker" link in the developer area point to your page | 11:15 |
| ochosi | cause status.ubuntu is dead | 11:15 |
| ochosi | so it's not really useful | 11:15 |
| knome | 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:15 |
| knome | well that's the other question - can we have a space where it is under the IS control in xubuntu.org? | 11:16 |
| knome | sure, then all code needs to go through IS, but meh | 11:16 |
| ochosi | i thought of just rendering it to an image when there's an update | 11:16 |
| knome | the status bars? | 11:16 |
| ochosi | yeah | 11:16 |
| knome | right... | 11:16 |
| ochosi | we can also add an iframe ;) | 11:17 |
| knome | huho | 11:17 |
| knome | i kind of understand your point, but otoh, don't | 11:17 |
| knome | people can just go to the tracker to see the status | 11:17 |
| knome | the progress bars are useless as is on the developer area | 11:17 |
| knome | you need to follow-up on the details anyway | 11:18 |
| knome | knowing we're "23% towards 15.10" doesn't tell a lot | 11:18 |
| ochosi | yeah, it's just a visual gimmick there, i know that | 11:19 |
| ochosi | but a meaningful image makes ppl click links | 11:19 |
| * knome shrugs | 11:20 | |
| ochosi | anyway, let's focus on the status page itself instead | 11:20 |
| knome | ;) | 11:20 |
| ochosi | so what was your thought re:tabs again? | 11:20 |
| knome | i'm working on it | 11:20 |
| ochosi | oh ok | 11:21 |
| ochosi | i'll just give you some time for that then and get some other stuff done meanwhile | 11:21 |
| knome | mhm | 11:21 |
| ochosi | also, just a small thought: maybe we could also put the "total progress" as the first item in the list | 11:22 |
| ochosi | i know it's the sum, so that makes sense at the end | 11:22 |
| * knome shrugs | 11:22 | |
| knome | :P | 11:22 |
| ochosi | still, it also makes sense as the first item | 11:22 |
| knome | if you want to do it like that, then i need to change the code | 11:44 |
| knome | the total isn't saved anywhere | 11:44 |
| knome | (maybe it should..) | 11:44 |
| ochosi | do it like what? | 11:44 |
| ochosi | ah | 11:44 |
| ochosi | you mean put the total first | 11:44 |
| knome | yes | 11:44 |
| ochosi | right, then keep it where it is | 11:44 |
| knome | see the status now | 11:45 |
| knome | has tabs | 11:45 |
| ochosi | nice | 11:45 |
| ochosi | what about color-coding the inprogress/todo/done in the expanded overview? | 11:46 |
| ochosi | (just the status column on the right) | 11:46 |
| ochosi | or the whole line with a very pale version of the main status color | 11:47 |
| ochosi | flocculant: wanna start setting up your LP account? | 11:49 |
| ochosi | (just added you to x-qa) | 11:50 |
| knome | ochosi, i thought about that, but i'm not really sure | 11:50 |
| knome | at least the whole row would be obtrusive | 11:50 |
| ochosi | mhm, maybe | 11:50 |
| ochosi | then maybe just try to add a bg color for the status column | 11:51 |
| ochosi | (maybe even that is too obtrusive, but it'd be nice to know/see) | 11:51 |
| ochosi | for the details page it'd definitely help | 11:51 |
| knome | another thought is to append something to the item row | 11:51 |
| ochosi | yeah, could work just as well | 11:52 |
| knome | there you go | 11:55 |
| knome | i don't know if that's useful | 11:55 |
| knome | i was actually thinking that it might be more useful to color the status text | 11:56 |
| ochosi | right, that could work too | 11:56 |
| ochosi | question is whether the text "inprogress" etc is still needed then | 11:56 |
| ochosi | if things are color-coded anywa | 11:56 |
| ochosi | y | 11:57 |
| knome | looky now | 11:57 |
| ochosi | definitely better! | 11:57 |
| flocculant | ochosi: you found it then ;) | 11:57 |
| ochosi | and appending might still be worth a try | 11:57 |
| knome | though now it's a bit too colorful on the details page | 11:57 |
| knome | or at least it doesn't help me much... | 11:57 |
| ochosi | flocculant: sure ;) just wanted to wait until we were both around | 11:57 |
| flocculant | :) | 11:57 |
| ochosi | knome: yeah, on the overview it's good, details not that much | 11:58 |
| knome | actually, it's more or less useless on overview ;) | 11:58 |
| knome | the column is too far away | 11:58 |
| ochosi | knome: yeah, that's what i mean with "appending" | 11:58 |
| knome | look now | 11:59 |
| knome | would something like that work? | 11:59 |
| knome | i mean, just color todo/blocked | 11:59 |
| ochosi | yeah | 11:59 |
| knome | maybe a bit less colorful red | 11:59 |
| ochosi | it's a bit funny though that done is grey-strikethrough ;) | 12:00 |
| ochosi | but yeah, maybe better than making it green tbh | 12:00 |
| knome | not at all.. | 12:00 |
| knome | "don't worry about this" | 12:00 |
| ochosi | :) | 12:00 |
| ochosi | yeah | 12:00 |
| ochosi | no actually i think this works wel | 12:00 |
| ochosi | l | 12:00 |
| knome | ok, done with the color tweaking now | 12:01 |
| knome | another idea... | 12:02 |
| knome | prepend "TODO: " to the todo items | 12:02 |
| knome | like this | 12:02 |
| knome | then the color might not be needed (for the whole row) | 12:03 |
| knome | like this | 12:03 |
| ochosi | hm, dunno, the "TODO" is a bit of a duplication there and the color is not as easy to see as before | 12:03 |
| ochosi | because it's just four letters instead of (usually) more | 12:03 |
| flocculant | then would it not be better to remove the status column and add the status to all the work items | 12:04 |
| ochosi | yeah, sort of | 12:04 |
| knome | ochosi, refresh | 12:04 |
| knome | flocculant, that might be an option | 12:04 |
| ochosi | heh, flashier color :) | 12:04 |
| knome | though i don't think we need a status for every row | 12:04 |
| knome | i think it's useful enough | 12:04 |
| knome | and not too obtrusive | 12:04 |
| ochosi | the colors do it well enough for my taste | 12:05 |
| knome | could also b smaller font | 12:05 |
| ochosi | i wouldn't need the status column at all as it is now | 12:05 |
| ochosi | it's pretty clear what is done and what's not | 12:05 |
| knome | yes | 12:05 |
| knome | lookie now | 12:05 |
| knome | or refresh | 12:05 |
| knome | that might be my favorite | 12:05 |
| knome | can also prepend blocked items with "BLOCKED" | 12:06 |
| ochosi | mhm, nice | 12:06 |
| ochosi | makes it look more like a tag or label | 12:06 |
| ochosi | gotta step out for 10mins or so | 12:07 |
| ochosi | brb | 12:07 |
| knome | ok, enough of this hacking now | 12:27 |
| flocculant | looks better like that imo | 12:31 |
| ochosi | knome: well done | 12:44 |
| ochosi | also, is there a style for "postponed" yet? | 12:45 |
| knome | nope | 12:45 |
| ochosi | (could be like "done" but with "Postponed:" prepended) | 12:46 |
| * knome shrugs | 12:46 | |
| knome | i'll look at that the next time | 12:46 |
| ochosi | sure | 12:46 |
| bluesabre | it's looking really good | 13:10 |
| knome | i just modified the tabs so that you can actually link to either tab and get that tab opened on load | 13:11 |
| knome | (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:12 |
| knome | ochosi, there you have it, postponed style | 13:19 |
| knome | (lookie under web) | 13:19 |
| ochosi | hey bluesabre | 13:24 |
| bluesabre | hey ochosi | 13:24 |
| ochosi | knome: yeah, looks nice! | 13:24 |
| ochosi | bluesabre: still on holidays? :) | 13:24 |
| bluesabre | ochosi: pretty much, just checking in here for a few minutes this morning | 13:25 |
| bluesabre | gotta bake a blackberry cobbler this morning as promised ;) | 13:25 |
| ochosi | heh, lovely | 13:26 |
| ochosi | btw, i marked my artwork items done, since they're all just pending in terms of getting uploaded | 13:26 |
| bluesabre | sounds good to me | 13:27 |
| bluesabre | maybe we'll see that new ubiquity this week | 13:27 |
| ochosi | that'd be good too | 13:28 |
| ochosi | oh, and a xfpanel-switch release ;) | 13:28 |
| bluesabre | yup | 13:28 |
| bluesabre | that'll be here probably monday | 13:28 |
| bluesabre | gotta review the build system to make sure its up to snuff for release | 13:29 |
| knome | ochosi, also now you can see that POSTPONED items aren't counted towards the progress | 13:29 |
| knome | in good or bad | 13:29 |
| knome | which is, IMO, the only right way | 13:29 |
| bluesabre | knome: that sounds good to me | 13:30 |
| ochosi | knome: indeed, that sounds right | 13:30 |
| knome | status.u.c didn't do that | 13:30 |
| knome | ochosi, what do you think of the following idea: | 13:31 |
| knome | mark blocked items with the BLOCKED tag | 13:31 |
| knome | remove the tag from TODO | 13:31 |
| knome | add the tag to INPROGRESS | 13:31 |
| ochosi | guess i'd have to see | 13:32 |
| knome | ok, just a moment, it's a trivialish css operation now | 13:32 |
| knome | refresh | 13:33 |
| knome | i think it makes more sense logically | 13:33 |
| knome | because obviously, all items here are "TODO" | 13:34 |
| knome | just with different statuses | 13:34 |
| knome | this way the blocked items also get more weight and prominence in the list | 13:34 |
| ochosi | yeah, puts the (visual) stress on WIP instead of TODO | 13:34 |
| ochosi | mhm | 13:34 |
| knome | which is desirable | 13:34 |
| knome | or at least is from my POV | 13:34 |
| ochosi | yeah | 13:34 |
| knome | this way it's very easy to see what needs unblocking | 13:34 |
| ochosi | woops, gotta run | 13:35 |
| knome | hha | 13:35 |
| ochosi | be back in 30mins | 13:35 |
| knome | have fun :) | 13:35 |
| knome | ok | 13:35 |
| ochosi | u2! | 13:35 |
| knome | will do | 13:35 |
| knome | also thanks for reminding me music exists :P | 13:35 |
| knome | bluesabre, http://xstatus.knome.fi/#tab-details/bluesabre | 13:54 |
| knome | bluesabre, http://xstatus.knome.fi/#tab-details/ochosi | 13:54 |
| knome | eh, | 13:54 |
| knome | ochosi, http://xstatus.knome.fi/#tab-details/ochosi | 13:54 |
| ochosi | knome: nice, almost done :) | 14:07 |
| ochosi | that's a really useful view | 14:07 |
| knome | yes | 14:07 |
| ochosi | would be nice to integrate that back into LP somehow | 14:08 |
| knome | also, http://xstatus.knome.fi/#tab-overview/expand | 14:08 |
| ochosi | into the personal page overview | 14:08 |
| ochosi | nice, much cleaner | 14:09 |
| knome | (no, see the url without /expand) | 14:09 |
| ochosi | into this page, i meant: https://launchpad.net/~ochosi | 14:09 |
| knome | it would be a resource hog, they'd likely need to create db views for all people and look through all specifications | 14:09 |
| ochosi | mhm, nice | 14:09 |
| knome | there's no way to know which specs you are involved with until you check all the specs | 14:09 |
| ochosi | yeah, i guess | 14:10 |
| knome | or check all specs where you/any of the teams you're a member of is in some of the fields | 14:10 |
| ochosi | but since it seemed like we're building our own frontend to (parts of) LP almost... | 14:10 |
| knome | so yeah, it's not sustainable by all means | 14:10 |
| knome | sure | 14:10 |
| knome | we are | 14:10 |
| knome | good lord they have an API for that | 14:10 |
| ochosi | :) | 14:12 |
| knome | added a dropdown | 14:39 |
| knome | so you can now pick a nick from the UI | 14:39 |
| knome | do whatever you wish with it :P | 14:41 |
| ochosi | nice | 14:42 |
| ochosi | that's pretty cool too | 14:42 |
| ochosi | knome: you could (if you wanted to) style that combobox too to fit in with the rest of the page though ;) | 14:50 |
| knome | naah | 14:51 |
| sorinello | very nice link: http://xstatus.knome.fi/#tab-overview/expand didn't know about it | 16:35 |
| ochosi | jjfrv8: ok, in the file-manager-window page i'd add the right-click menu (to show / hide sidepane items) | 17:06 |
| Unit193 | http://lists.alioth.debian.org/pipermail/pkg-xfce-devel/2015-July/020878.html - https://bugzilla.xfce.org/show_bug.cgi?id=12012 | 17:07 |
| ubottu | bugzilla.xfce.org bug 12012 in General "xfce4-session configured with --disable-legacy-sm breaks qt4 integration" [Normal,New] | 17:07 |
| ochosi | jjfrv8: other than that, that page looks great! | 17:08 |
| ochosi | 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 | 17:14 |
| jcjordyn120 | hello what's up | 20:20 |
| knome | hello | 20:22 |
| Unit193 | Howdy. | 20:27 |
| knome | jcjordyn120, are you looking for something or somebody? | 20:29 |
| jcjordyn120 | no knome | 20:30 |
| knome | jcjordyn120, what brings you here then? :) | 20:30 |
| jcjordyn120 | just seeing what up with the xubuntu development. knome | 20:31 |
| knome | ok; it varies how quiet/loud it is here, but feel free to ask or comment if there's anything | 20:32 |
| jcjordyn120 | okay knome | 20:33 |
| knome | krytarik, hello! | 20:34 |
| krytarik | knome: Howdy. | 20:34 |
| astraljava | o/ | 20:34 |
| knome | krytarik, avoiding translating twice was the (other) thing i thought about - great to have that sorted | 20:34 |
| knome | krytarik, what's VPATH? | 20:35 |
| knome | krytarik, and what's translate: | get-translations ? | 20:35 |
| krytarik | hahaha | 20:35 |
| knome | and for the pdf linking, i'd rather use something else than sed | 20:36 |
| knome | practically something that would just be hidden from the PDF | 20:36 |
| knome | but would be part of the documentation | 20:37 |
| knome | that would also allow a (better) description (that can be trasnslated) | 20:37 |
| knome | and while <ul> kind of is most semantic, i'd likely just drop it all inside a <p> | 20:38 |
| knome | (avoid most of the CSS and all) | 20:38 |
| krytarik | 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:39 |
| knome | right | 20:40 |
| jcjordyn120 | whats up with that QA position | 20:43 |
| Unit193 | jcjordyn120: What do you mean "what's with it"? f<tab> has it. | 20:43 |
| knome | jcjordyn120, a person by the nick "flocculant" is being appointed as the QA lead if there is no objections | 20:43 |
| knome | jcjordyn120, the QA lead coordinates the testing and quality assurance related tasks for xubuntu | 20:44 |
| jcjordyn120 | oh ok | 20:44 |
| jcjordyn120 | why is abiword and gnumeric included with xubuntu instead of libreoffice suite | 20:44 |
| Unit193 | I'm not going to remember that nick very well, sigh. | 20:44 |
| Unit193 | jcjordyn120: It isn't, in Wily. | 20:45 |
| jcjordyn120 | oh i was talking about vivid | 20:45 |
| Unit193 | vivid is done with, wily is the target. | 20:45 |
| jcjordyn120 | oh ok, so what is included with wily | 20:46 |
| Unit193 | Libreoffice. | 20:47 |
| jcjordyn120 | okay | 20:47 |
| knome | Unit193, basically, you just xsltproc to a .fo file, then use fop to make a PDF out of that | 20:49 |
| knome | Unit193, in our case, using the PDF customization layer | 20:49 |
| knome | Unit193, done. | 20:50 |
| Unit193 | (Thinking about adding it to my daily build script.) | 20:52 |
| knome | sure | 20:53 |
| jcjordyn120 | hello can you here me, my internet went out | 21:12 |
| knome | jcjordyn120, yes, we can read you. | 21:12 |
| jcjordyn120 | oh thanks, i by mistake flipped my wifi switch off | 21:13 |
| knome | UTC'ized the tracker | 21:17 |
| ochosi | evening all | 21:25 |
| ochosi | knome: looking forward to the date switch and the status tracker burndown's second line ;) | 21:26 |
| knome | hey ochosi | 21:26 |
| knome | ochosi, it already happened when the tracker thought it was supposed to follow UTC+3 time | 21:27 |
| ochosi | oh | 21:27 |
| ochosi | crap, i missed it | 21:27 |
| knome | but i of course fixed it and removed the other line ;) | 21:27 |
| ochosi | :) | 21:27 |
| knome | yeah, i don't intend to keep it this way | 21:27 |
| ochosi | hm, planning to rotate those progressbars by 90°? | 21:27 |
| knome | the problem is that i don't really want to create a SVG | 21:27 |
| ochosi | yeah | 21:27 |
| knome | and i don't know how i could draw the burndown line | 21:27 |
| ochosi | hmm, css maybe? | 21:27 |
| ochosi | or js | 21:28 |
| ochosi | (i know php could draw it) | 21:28 |
| knome | hah | 21:28 |
| knome | with html5 canvas, maybe | 21:28 |
| knome | i should know what the area for the burndown chart was then | 21:28 |
| knome | the other option is some hacking with css rotation | 21:29 |
| ochosi | yeah that sounds about ok | 21:30 |
| knome | "about ok" | 21:30 |
| ochosi | :) | 21:30 |
| knome | that sounds like headache | 21:30 |
| ochosi | well, it could be a lot of work | 21:30 |
| ochosi | is what i mean | 21:30 |
| ochosi | but the result would likely work | 21:30 |
| knome | though it might be less than canvas | 21:30 |
| knome | meh | 21:30 |
| knome | the problem is | 21:30 |
| knome | i should figure out the printing of the vertical lines next | 21:30 |
| knome | eg. store start/end days somewhere | 21:31 |
| ochosi | indeed, that's likely more important than the burndown line | 21:31 |
| knome | the burndown line is actually quite trivial after that, i just figured | 21:31 |
| ochosi | right | 21:32 |
| ochosi | hmm, have you ever exported to xpm from inkscape? | 21:32 |
| knome | no | 21:32 |
| * knome gets some puke to his mouth from the thought alone | 21:32 | |
| ochosi | yeah, it's quite terrible, i know | 21:33 |
| ochosi | i was considering to port parts of greybird's wm theme to svg | 21:33 |
| ochosi | but then there seems to be little benefit because of the xpm-iness | 21:33 |
| knome | heh | 21:33 |
| knome | what was the 15.04 release day | 21:35 |
| knome | and what is the scheduled 15.10 release day | 21:36 |
| knome | ochosi, SAMBA! | 21:43 |
| knome | ochosi, or in other words, look at the burndown page | 21:43 |
| ochosi | :D | 21:43 |
| knome | ochosi, well, there you have it | 21:58 |
| knome | ;) | 21:58 |
| knome | now for the burndown line | 21:58 |
| ochosi | nice that didn't take that long :) | 21:58 |
| knome | now for the burndown line | 21:58 |
| ochosi | (still waiting for that date-change) | 21:58 |
| knome | 2 more hours | 21:58 |
| knome | though i could add some fake informácion | 21:58 |
| knome | actually, first | 21:59 |
| knome | some other stuff | 21:59 |
| knome | you'll see soon | 21:59 |
| * knome sighs in advance | 21:59 | |
| * ochosi waits patiently | 22:00 | |
| knome | ochosi, refresh | 22:01 |
| knome | 10% line | 22:01 |
| ochosi | i see a line | 22:01 |
| knome | yes | 22:02 |
| knome | it's at 10% | 22:02 |
| ochosi | k | 22:02 |
| knome | now for the rest | 22:02 |
| * knome hacks the css linear-gradient background | 22:02 | |
| knome | 10 + 20 | 22:03 |
| knome | well, at least should be | 22:03 |
| knome | that doesn't look unifrom | 22:03 |
| knome | *form | 22:03 |
| knome | maybe my eyes just fail me | 22:03 |
| knome | let's see 30 | 22:03 |
| knome | that looks better | 22:04 |
| knome | haha | 22:04 |
| knome | ok | 22:04 |
| knome | there's something fishy with the bar | 22:04 |
| knome | *there* we go | 22:08 |
| ochosi | yup | 22:11 |
| ochosi | that looks good | 22:11 |
| knome | let me try something completely different | 22:11 |
| knome | that | 22:12 |
| knome | could be subtler | 22:12 |
| knome | but believe me or not, that's half easier than the previous one | 22:12 |
| knome | there | 22:13 |
| knome | could be even more subtler | 22:13 |
| knome | now? | 22:13 |
| knome | huh what | 22:15 |
| ochosi | quite fat lines, but the gradient is nice | 22:15 |
| knome | ok | 22:15 |
| knome | it's a visual thing | 22:16 |
| knome | there aren't lines | 22:16 |
| knome | there are just 10 gradients | 22:16 |
| ochosi | oh | 22:16 |
| ochosi | right | 22:16 |
| ochosi | maybe subtler? | 22:16 |
| knome | haha, it's already 2.5% black | 22:16 |
| knome | but ok | 22:16 |
| knome | now? | 22:17 |
| knome | still? | 22:17 |
| ochosi | still looks like 2px lines, but my eyes might be tired | 22:17 |
| knome | well, yeah | 22:17 |
| knome | there seems to be some glitch | 22:17 |
| knome | it's %'s anyway | 22:18 |
| ochosi | and i guess the effect is stronger with the low brightness i'm using atm | 22:18 |
| knome | now the gradients is barely visible | 22:18 |
| knome | *are | 22:18 |
| knome | but the lines are definitely still "fat" | 22:18 |
| ochosi | when i pump it up, the gradients fade out a bit | 22:18 |
| * knome returns to the lines | 22:19 | |
| knome | for now, at least | 22:19 |
| knome | ok, the burndown line now | 22:19 |
| * knome sighs | 22:19 | |
| knome | i think i need js there | 22:19 |
| * knome sighs again | 22:20 | |
| ochosi | whoops, where did the burndown tab go? | 22:21 |
| ochosi | oh, it's at the bottom | 22:21 |
| knome | what? | 22:22 |
| knome | ok, something failed | 22:22 |
| knome | only my js. | 22:22 |
| knome | my bad! | 22:22 |
| knome | think i'll figure this out with greasemonkey | 22:22 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!