I find the collapsing functionality very helpful. The only thing that I've never used is collapsing only-child comments (though this is useful for unhiding hidden comments).
I am pretty sure we are not supporting hidden comments so we could probably remove the collapse button by default from only-child comments. However, if users could eventually sort/filter comments by the upvote/downvote of comment tags then we could collapse/expand comments which don't match. So it would probably be useful to keep only-child comment collapse buttons... Anyway, I find collapse buttons very useful and helpful. On 10/17/2015 6:38 AM, [email protected] wrote: > Send Design mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.snowdrift.coop/mailman/listinfo/design > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Design digest..." > > > Today's Topics: > > 1. Re: discussion/ticket system mockups (mray) > 2. Re: discussion/ticket system mockups (Stephen Michel) > 3. Re: discussion/ticket system mockups (Aaron Wolf) > 4. Re: discussion/ticket system mockups (Stephen Michel) > 5. Re: discussion/ticket system mockups (Stephen Michel) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 16 Oct 2015 20:06:07 +0200 > From: mray <[email protected]> > To: [email protected] > Subject: Re: [Design] discussion/ticket system mockups > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > > > On 16.10.2015 04:57, Stephen Michel wrote: >> >> On Thu, Oct 15, 2015 at 6:29 PM, mray <[email protected]> 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. > > > Robert > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 819 bytes > Desc: OpenPGP digital signature > URL: > <http://lists.snowdrift.coop/pipermail/design/attachments/20151016/8c6827d8/attachment-0001.sig> > > ------------------------------ > > Message: 2 > Date: Fri, 16 Oct 2015 17:41:24 -0400 > From: Stephen Michel <[email protected]> > To: Design discussion for Snowdrift.coop <[email protected]> > Subject: Re: [Design] discussion/ticket system mockups > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > > > On Fri, Oct 16, 2015 at 2:06 PM, mray <[email protected]> wrote: >> >> >> On 16.10.2015 04:57, Stephen Michel wrote: >>> >>> On Thu, Oct 15, 2015 at 6:29 PM, mray <[email protected]> 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. > >> >> >> Robert >> >> _______________________________________________ >> Design mailing list >> [email protected] >> https://lists.snowdrift.coop/mailman/listinfo/design > > ~Stephen > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.snowdrift.coop/pipermail/design/attachments/20151016/1f62f4b2/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Fri, 16 Oct 2015 14:47:32 -0700 > From: Aaron Wolf <[email protected]> > To: [email protected] > Subject: Re: [Design] discussion/ticket system mockups > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > > > On 10/16/2015 02:41 PM, Stephen Michel wrote: >> >> >> On Fri, Oct 16, 2015 at 2:06 PM, mray <[email protected]> wrote: >>> On 16.10.2015 04:57, Stephen Michel wrote: >>> >>> On Thu, Oct 15, 2015 at 6:29 PM, mray <[email protected] >>> <mailto:[email protected]>> 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- >> <https://img.bi/#/bZHUWcV!bS6MpE0KIso8MSg8f3vDKgXjvYNBVP4rF6i3RKD-> >> > That link was no good because it was coded with http://https:// in the > link. The text worked though. > > >> 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 >> <https://img.bi/#/q1mhu9l!A8SXKRNJ6v3l9RTgHGn1KgyWq8kxDnUxc0OV1fO->, I >> changed the top and left borders of post A to be in the style of border >> 2. That's all I'm proposing. >> > > While I see Robert's point that the borders aren't necessarily > important, I must say that I agree with Stephen in that his mockup that > had all internal borders be equally thick simply looked better to me. I > find the increased border clarity to simply make it easier to > distinguish things and just looks better to me. So I 100% support > Stephen's subtle proposal. > _______________________________________________ Design mailing list [email protected] https://lists.snowdrift.coop/mailman/listinfo/design
