Re: [Design] discussion/ticket system mockups
On October 17, 2015 5:04:55 AM EDT, mray wrote: > > >On 16.10.2015 23:41, Stephen Michel wrote: >> >> >> On Fri, Oct 16, 2015 at 2:06 PM, mray wrote: >>> >>> >>> On 16.10.2015 04:57, Stephen Michel wrote: On Thu, Oct 15, 2015 at 6:29 PM, mray wrote: > After some discussions with wolftune it dawned on me that we >probably > have to stick to our discussion/ticket system. Stick to our discussion/ticket system as opposed to...? >>> >>> ... something that can be considered a finished product. >>> > I thought we might as well make it more usable then. Here is >where we > currently are: > > https://img.bi/#/tMpXHzF!jefIs_vKO6A8a2S4CFDwDg6TK4Qw9JNMzHkb99u5 > > > Any feedback? The border around the inner shaded posts is not dark enough for me >to clearly distinguish the border. Making all the inner borders the >same darkness makes a world of difference, though it's a small change: https://img.bi/#/q1mhu9l!A8SXKRNJ6v3l9RTgHGn1KgyWq8kxDnUxc0OV1fO- ~Stephen >>> >>> It is ok not to be able to distinguish the border. >>> The border has the sole purpose of highlighting the change of >background >>> color. And even that does not have to be something that needs to be >>> distinguished clearly. >>> >>> The main goal is to make it easy to read the connection of posts in >>> terms of partents and children so that you don't get confused. >>> indentation is probably the biggest mechanism that cares about that, >>> background and borders are just supposed to help. >>> >>> The really dark border at the very left is just to indicate that >this is >>> the topmost post and you're not missing any context. >> >> I think I may have been unclear. Here's your original image, with >> borders and posts identified. >> >> https://img.bi/#/bZHUWcV!bS6MpE0KIso8MSg8f3vDKgXjvYNBVP4rF6i3RKD- >> >> Border 1 is very dark. >> Border 2 is dark. >> Border 3 and 4 are light. So light that it is difficult for me to >pick >> out the borders of post A and B. >> This makes posts A and B run together for me. >> >> I propose changing borders 3 and 4 to be the same darkness as border >2 >> (maybe it's just a rendering issue, but borders 3 and 4 are lighter >in >> the image. In my earlier image, I changed the top and left borders of >> post A to be in the style of border 2. That's all I'm proposing. >> > >I agree. This is my fault, I should have noted that these mockups >aren't >really "clean" in any sense. Just have a look at the horrible spacing >differences. This subtle amount of difference is due to me using >transparency to quickly adapt the predefined color-swatches in >intensity. No worries! >>> >>> >>> Robert >>> >>> ___ >>> Design mailing list >>> Design@lists.snowdrift.coop >>> https://lists.snowdrift.coop/mailman/listinfo/design >> >> ~Stephen >> >> >> >> ___ >> Design mailing list >> Design@lists.snowdrift.coop >> https://lists.snowdrift.coop/mailman/listinfo/design >> > > > > > >___ >Design mailing list >Design@lists.snowdrift.coop >https://lists.snowdrift.coop/mailman/listinfo/design -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design
Re: [Design] discussion/ticket system mockups
On 16.10.2015 23:41, Stephen Michel wrote: > > > On Fri, Oct 16, 2015 at 2:06 PM, mray wrote: >> >> >> On 16.10.2015 04:57, Stephen Michel wrote: >>> >>> On Thu, Oct 15, 2015 at 6:29 PM, mray wrote: After some discussions with wolftune it dawned on me that we probably have to stick to our discussion/ticket system. >>> >>> Stick to our discussion/ticket system as opposed to...? >> >> ... something that can be considered a finished product. >> >>> I thought we might as well make it more usable then. Here is where we currently are: https://img.bi/#/tMpXHzF!jefIs_vKO6A8a2S4CFDwDg6TK4Qw9JNMzHkb99u5 Any feedback? >>> >>> The border around the inner shaded posts is not dark enough for me to >>> clearly distinguish the border. Making all the inner borders the same >>> darkness makes a world of difference, though it's a small change: >>> >>> https://img.bi/#/q1mhu9l!A8SXKRNJ6v3l9RTgHGn1KgyWq8kxDnUxc0OV1fO- >>> >>> ~Stephen >>> >> >> It is ok not to be able to distinguish the border. >> The border has the sole purpose of highlighting the change of background >> color. And even that does not have to be something that needs to be >> distinguished clearly. >> >> The main goal is to make it easy to read the connection of posts in >> terms of partents and children so that you don't get confused. >> indentation is probably the biggest mechanism that cares about that, >> background and borders are just supposed to help. >> >> The really dark border at the very left is just to indicate that this is >> the topmost post and you're not missing any context. > > I think I may have been unclear. Here's your original image, with > borders and posts identified. > > https://img.bi/#/bZHUWcV!bS6MpE0KIso8MSg8f3vDKgXjvYNBVP4rF6i3RKD- > > Border 1 is very dark. > Border 2 is dark. > Border 3 and 4 are light. So light that it is difficult for me to pick > out the borders of post A and B. > This makes posts A and B run together for me. > > I propose changing borders 3 and 4 to be the same darkness as border 2 > (maybe it's just a rendering issue, but borders 3 and 4 are lighter in > the image. In my earlier image, I changed the top and left borders of > post A to be in the style of border 2. That's all I'm proposing. > I agree. This is my fault, I should have noted that these mockups aren't really "clean" in any sense. Just have a look at the horrible spacing differences. This subtle amount of difference is due to me using transparency to quickly adapt the predefined color-swatches in intensity. >> >> >> Robert >> >> ___ >> Design mailing list >> Design@lists.snowdrift.coop >> https://lists.snowdrift.coop/mailman/listinfo/design > > ~Stephen > > > > ___ > Design mailing list > Design@lists.snowdrift.coop > https://lists.snowdrift.coop/mailman/listinfo/design > signature.asc Description: OpenPGP digital signature ___ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design
Re: [Design] discussion/ticket system mockups
On 17.10.2015 00:35, Stephen Michel wrote: > > > On Thu, Oct 15, 2015 at 8:19 PM, mray wrote: >> >> >> On 16.10.2015 01:08, Bryan Richter wrote: >>> On Fri, Oct 16, 2015 at 12:29:36AM +0200, mray wrote: After some discussions with wolftune it dawned on me that we probably have to stick to our discussion/ticket system. I thought we might as well make it more usable then. Here is where we currently are: https://img.bi/#/tMpXHzF!jefIs_vKO6A8a2S4CFDwDg6TK4Qw9JNMzHkb99u5 Any feedback? >>> >>> Looks great! As I said in IRC, I like the avatar integration and it >>> seems like the links around the text-entry box are not too cluttered. >>> [These were two points discussed after an earlier iteration.] >>> >>> I have two specific questions and one unrelated question: >>> >>> 1. I find it hard to recognize the dash (-) as something to click on >>> to hide a thread. That might be because the dash is *inside* the block >>> it ostensibly closes. Maybe better like this? >>> >>> https://img.bi/#/abqkwvI!pka8hJ924A1YWjwi6W58pwO_uQpg3758Yn13YVV6 >> >> You're moving the dash outside the box right? >> I think a box and its functionality should remain contained in itself. >> The dash was [-] before and is also positioned like on >> https://www.reddit.com/r/science/comments/2ypaa7/enceladus_saturns_6th_largest_moon_has_a_warm/ >> >> for example. >> I might play with alternatives like triangles like fr33domlover >> suggested on IRC tough. >> The reason I stuck with typographical elements is that they are >> minimalistic and fit to the rest. If possible I want to avoid attention >> in the header part, it is already too loud up there imho. > > For what it's worth, of all the nested comment systems I've used, I've > only ever used collapsing functionality in one. I'm not sure if I > haven't used it because it's not useful to me (I doubt this) or because > the design didn't work for me (lack of affordance, visual prominence). > Interestingly the only collapsing functionality I use is actually in my > email client, Geary. Here's a screenshot: > > https://img.bi/#/3yaA600!teR8S47vA3gjMicuK0QuMg1f7vOOmJJgt-WW1TqO > > This is definitely too much visual noise for every post, but maybe just > for top-level posts? > > ~Stephen > > I like the collapse/expand bar idea. But for one it would be inconsistent with other collapsing functionality, and as you said it adds much clutter and takes away screen real estate. Your questioning the collapse function all in all actually makes me wonder what *are* reasons to collapse. Because if by default anything is EVER collapsed I consider rethinking the whole thing. /me looks over to Aaron Robert signature.asc Description: OpenPGP digital signature ___ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design
