[00:04] if you reboot your warrior, you should see a purple envelope indicator now and clicking on it should display the 'about' tab with the announcements. [00:05] the announcements are coming from projects.json [00:08] also notable is anthonyeden contribution to show the task counters at the top of the project page [00:16] nice [00:18] Better than I could have done. Especially that fast. [00:48] did the warrior just force reboot? [00:49] it does that once a week. [00:50] https://github.com/ArchiveTeam/seesaw-kit/blob/master/seesaw/warrior.py#L681 [00:51] oh [01:52] [13seesaw-kit] 15anthonyeden opened pull request #68: Add time indicator to each item. Shows how long it's been running. (06master...06master) 02https://github.com/ArchiveTeam/seesaw-kit/pull/68 [12:11] chfoo: no orangered? :P [12:12] chfoo: hold on, you need to take an extra action to view announcements? [14:47] joepie91: i realized that having a banner at the top will confuse users with the "no connection with warrior" error message [14:50] also in my opinion, a persistent message will be less likely be read. a user clicking indicator has a high chance that the user is interested in reading it [14:54] chfoo: so just relocate the notification then? an indicator means that the majority of users will *not* click it, which defeats the point of it being a broadcast as such :P [14:54] i don't know where to put it [14:55] in the project box? [14:55] hold [14:55] chfoo: can you make me a screenshot of a warrior running a project [14:55] so I can draw on it [14:55] can't currently afford the RAM to spin up a VM [14:55] :P [14:56] ok, give me a sec [14:56] joepie91: https://dl.dropboxusercontent.com/u/672132/archiveteam/Screenshot%20from%202014-09-09%2010%3A56%3A03.png [14:58] chfoo: http://owely.com/011LRn8 [14:58] move the website/leaderboard links and description up a bit [14:58] put some kind of colored-background notification bar under it, like the rectangle [14:59] when there is a notification [14:59] leave it white otherwise [14:59] but there's not enough space in that header [14:59] ... how isn't there? [14:59] ideally your notifications are a single sentence anyway, so it'd fit horizontally [14:59] vertically, it fits even if you don't move the rest up, but it would look misaligned [15:00] if the notifications are larger, only display the first X words/characters [15:00] let me try a real project [15:00] which still allows to either catch somebody's attention or make somebody go "meh, not something I need to care about" [15:00] without having to explicitly click through [15:01] (sidenote: text in the 'task status summary' thingies is a little misaligned vertically) [15:01] (by 2px or something) [15:07] for twitch, there was the countdown timer. the title was 5 words and it pushed the links onto the second row. the description was ~15 words which overflowed the "collapse" toggle box underneath the image. [15:10] this only happens if you don't have the window maximized though [15:11] the warrior ui is a pain to work with since all the positions are hard coded in css [15:14] ah, i got it. show only a few words but clicking on it will bring up the about tab with the full message [15:14] * joepie91 is still a bit confused [15:19] joepie91: what i mean is that the header doesn't handle things gracefully when there isn't enough space: https://dl.dropboxusercontent.com/u/672132/archiveteam/Screenshot%20from%202014-09-09%2011%3A17%3A12.png [15:19] but i understand that is an unusual situation [15:21] chfoo: there's some very fun CSS properties involving ellipsis that could help there :) [15:23] if only it were that simple. if you inspect the warrior page, you'd find the projects page is margin-left: 175px; [15:24] chfoo: I'm sure something can be done with it :P [15:26] maybe the warrior ui needs a new look [15:30] nah [15:30] the look is fine [15:30] good, even [15:31] chfoo: people understand how to use it without complex instructions, and the only complaint is the errors that show up in the log that aren't actually errors (which the notification thing should help with) [15:31] that's a pretty good score, and I'd not change it unless absolutely necessary :P [15:43] python 2.6 forever :) [15:54] Maybe the mail icon should fade in and out slowly? It would make new users more likely to click it. [15:55] aaaaaaaaa: they'll just click it to get rid of it, then close the page again without reading :) [15:56] intrusive things don't work, they just teach the user to find the quickest way to get rid of it [15:56] Like the jumping dog effect on OS X. [15:56] preferably without giving any attention to the thing in question, because it is now a hate-able object [15:56] this is why I propose an always-visible notification [15:57] doesn't require user interaction, removes the friction for reading it (no cognitive load because you don't need to decide whether to click the envelope or not) [15:57] does not present itself as something to route around [15:57] also not familiar with a 'jumping dog effect' :) [15:59] see this https://www.youtube.com/watch?v=xKMJ_I3gMIA the print monitor is trying to notify them of a problem [16:00] Maybe calling it the jumping dog is not as widespread as I thought. [16:00] just not an OS X user :) [16:00] and heh [16:00] that would annoy the living hell out of me [16:01] then again, I also have a strongly adverse reaction to blinking taskbar buttons [16:01] it's a reason for me to literally replace my 'active applications' dock/bar with a different one [16:01] if I can't turn it off [16:01] (which is exactly what I've done in XFCE) [16:01] (exchanged it for dockbarx) [16:01] in earlier versions, you had to click the actual item, so if you clicked where it usually is when it is mid-air it would get focus [16:01] err, not get focus [16:02] did I mention how mindnumbingly boring implementing an audit log is [16:04] why? what makes it especially bad? [16:04] because it comes down to dumb data shovelling [16:04] and fussing about with relationships between items [16:04] and triple checking absolutely everything [16:05] there's absolutely no interesting problem to solve (we've solved the problem of 'display a table of data on a screen' for, what, the past 30 years?) [16:05] and it's incredibly repetitive work that requires a lot of attention and care [16:05] much more care than any other aspect [16:05] because if your audit log misses an entry, you have a Problem with a capital P [16:06] as a bonus, it's near impossible to generalize it into a reusable blob of code [16:06] without making it unusable for end users [16:06] so you end up doing all of the above for /every single project that needs an audit log/, over and over again [16:06] :| [16:07] I like engineering, but I hate programming, so to say [16:07] it mostly just comes down to being a typist with a slightly different character set and vocabulary [16:07] hence, boring [16:07] :P [16:07] cc aaaaaaaaa [16:09] Oh, that makes sense. You can't really let things just flow. [16:09] pretty much [16:25] joepie91: i'm looking at the html and it seems like the header space is unique per tab [16:26] did you mean to say that the message is to be displayed only on the current projects tab? [16:27] chfoo: no, on the page that you screenshotted [16:27] where it shows the current worker logs [16:27] the suggestion was a per-project message thing :P [16:27] ah, the message i have set up is meant to be global [16:28] aha. [16:28] didn't I specify per-project in the ticket? [16:28] but if we want per project messages, won't it be easier to just edit the html in the pipeline? [16:30] chfoo: does it update that with a reasonable frequency...? [16:30] I thought that was only updated on pipeline updates [16:30] it checks every hour [16:30] let me confirm [16:31] yes, it does a git fetch every hour and then starts the new code as the selected project [16:32] I thought of adding a

in the html for the project [16:32] and then have a tornado event look for messages and overwrite that [16:34] it does that already. the header image, links, description, and count down timer are all build from the pipeline [16:34] i just assumed that alard never envisioned that it would be used for displaying announcements [16:37] heh [16:37] chfoo: in that case, just add a nice CSS class to the warrior CSS [16:37] .alert or something [16:38] yeah, you just read my mind [16:38] :P [16:38] I'd go for a not-too-intrusive red shade background color [16:38] with sufficient padding, maybe border-radius [16:38] that should fit in okay [16:38] but you still have a point about the indicator in the about tab