| SotK | so, I agree that three states is good, I was just lazy and didn't do that whilst experimenting | 06:48 |
|---|---|---|
| SotK | one of the things I was aiming for with the sidebar was to tie the active icon into the page more than the current one does, since at the moment it just sort of sits there at the side and doesn't "feel" like its connected to the rest of the page | 06:51 |
| SotK | that and increasing the contrast at a glance | 06:52 |
| SotK | one of the reasons I started experimenting is that one of the low-low-priority itches I want to scratch in StoryBoard is that our html isn't the nicest to read, compare http://git.openstack.org/cgit/openstack-infra/storyboard-webclient/tree/src/app/storyboard/template/side_menu.html#n17 with http://paste.openstack.org/show/623529/ for example (though the former does have more elements in the sidebar for h | 06:57 |
| SotK | andling the logged-in view at the same time, I feel like the point still stands) | 06:57 |
| SotK | and the sidebar is far from the worst part xD | 06:58 |
| SotK | and so in contemplating ways to fix that I figured I'd also contemplate ways to improve how it looks too | 06:59 |
| SotK | but anyway I'm not particularly concerned about things like "the rest of storyboard has rounded boxes", since any work to actually change it would be part of redesigning everything anyway | 07:00 |
| SotK | my original question was intended to be more "would people be interested in some effort at some point to redesign storyboard's UI along these lines", rather than specifically "is this About page better than the old one?" | 07:01 |
| SotK | I know what you mean about the harshness of the sidebar, but I think one of the problems is I actually like that harshness | 07:02 |
| Zara | haha :) I guessed you were driving at something like the original question, but I think the only way for me to get to an answer to that is to answer the second | 11:38 |
| Zara | because eg: you know which aspects of that layout are conscious design decisions and which things are boilerplate to get it as close to the current layout without importing all our current code for the sake of a demo | 11:39 |
| Zara | whereas from here, I can't tell which things are 'things sotk wants to change' vs 'this sotk is changing in that example for convenience' | 11:39 |
| Zara | so like if your redesigning focused on making all the round boxes square, then I'm opposed. XD if it involves moving all the text so it's more nicely aligned, I'm in favour. so all I can do is point out the specifics of that page and try to analyse my reactions to them. | 11:40 |
| Zara | I find it interesting that you find the sidebar redesign higher contrast, since I personally found it lower contrast (I think you're looking at the current icon and I'm looking at the whole sidebar for that?). and because I am someone who turns the contrast right up, I actually preferred the 'higher' contrast of the old one. :D | 11:42 |
| Zara | width, I'm unsure about, because narrower sidebar leaves more room for content, but narrower sidebar is harder to click | 11:42 |
| Zara | I think where you're making changes, it'd be good to write why so it's easier to tell where we differ because of different aesthetic preferences and where we differ because we're thinking different things around usability | 11:44 |
| Zara | though that may be impractical for lots of changes | 11:45 |
| Zara | I agree on the value of simplifying the html | 11:45 |
| Zara | also I have no idea how I wound up writing 'sotk is changing this' as 'this sotk is changing' | 11:47 |
| Zara | oh also the codepen expired so it's hard for anyone to go back and look atm | 11:48 |
| SotK | yeah, by higher contrast I was considering the contrast between the active icon and the rest of the sidebar | 11:49 |
| SotK | I will try to put explanations in places in future to help | 11:50 |
| SotK | I don't think the reworked sidebar is sufficiently narrower that it harms the ability to click accurately tbh | 11:51 |
| SotK | https://codepen.io/StoK/pen/PJBdzK should be a more permanent link I think | 11:52 |
| Zara | I'm not sure if it does or not so I'm not assuming either way yet. re: contrast, if you take a look at the firefox example the contrast comes across quite differently to the chrome imo. I don't think the firefox version does well out of it. | 11:52 |
| Zara | hard to tell how much accompanying elements play a part there | 11:53 |
| Zara | thanks for the link | 11:53 |
| Zara | (also I'm very used to the current shade so while for me it looks washed out, idk if that's representative). but I think I do prefer reading grey-on-dark-grey to grey-on-mid-grey, and in practice I'm likely to be reading text under all icons, not just current one. | 11:56 |
| Zara | I am very shortsighted and have old glasses and at a glance new is harder to read. | 11:56 |
| Zara | (though not the currently selected icon) | 11:57 |
| * SotK makes it darker | 11:58 | |
| Zara | :) | 11:59 |
| Zara | that's more usable for me. wondering about icons and text same shade as page background. (the pinky beigey ? colour) | 12:04 |
| Zara | atm it's a bit odd that icons are different to text | 12:05 |
| Zara | or at least that the highest contrast bit is the icon rather than the bit you need to read | 12:05 |
| SotK | that probably makes sense, there was no thought in the colour choices there other than "the white text is blinding me" | 12:05 |
| Zara | ahaha | 12:06 |
| Zara | yes we have totally different needs around contrast in general so that can't help. | 12:06 |
| Zara | what blinds you is probably something I like because I can turn my screen brightness right down and put all the lights on | 12:07 |
| SotK | there it is brighter now | 12:07 |
| *** Dobroslaw has quit IRC | 12:26 | |
| SotK | for more context on the design choices (like the drop shadows and such), I was mostly playing around making something inspired by https://material.io/guidelines/ | 13:48 |
| *** jtomasek has quit IRC | 16:49 | |
| *** jtomasek has joined #storyboard | 17:10 | |
| *** jtomasek has quit IRC | 17:45 | |
| fungi | passing along sb discussions which happened between 13:14-15:32z today in #openstack-release: http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2017-10-13.log.html#t2017-10-13T13:14:43 | 17:47 |
| fungi | for reference on the metadata bits we seem to miss from current imports, compare https://launchpad.net/bugs/1349874 with https://storyboard.openstack.org/#!/story/1349874 (even with "all events" toggled on we miss the metadata transition events from lp) | 17:50 |
| openstack | Launchpad bug 1349874 in Monasca "Autocomplete using monasca-api in grafana" [Low,Won't fix] - Assigned to Rob Raymond (rob-raymond) | 17:50 |
| fungi | i haven't looked to see how hard it would be to include them in the migration tool | 17:50 |
| *** jtomasek has joined #storyboard | 17:57 | |
| *** jtomasek has quit IRC | 17:57 | |
| SotK | fungi: interesting conversation, thanks for the link | 21:20 |
| SotK | I dont know enough about launchpadlib to know how easy/hard it'll be to do that | 21:21 |
| SotK | I'd hope fairly easy | 21:21 |
| fungi | yeah, same here. i don't know when i'll have bandwidth to poke at it, but maybe some interested party will hack on it if we keep a note of that as a nice-to-have | 21:21 |
| SotK | though, our statuses don't map exactly I feel, and global priority doesn't make sense from storyboard's pov | 21:22 |
| persia | Although Storyboard is a closer data model to Launchpad than anything else I know. We made a few specific changes to the model (like entirely changing the status set, utterly changing priorities, and dropping support for certain classes of metadata (releases, milestones), but that's probably less invasive than trying to flatten multi-project bugs into something like trac. | 21:26 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!