Topic on Talk:Structured Discussions

The way the branches logically separated text before Now it is not. Now it is a wall of text.

wiki -- flow

In these places it turns out that the user does not continue the conversation, does not respond to the last / the last few posts, he he begins a new mini talk, a new branch. The plain text of this moment of this transition does not markedly. It is difficult to understand.

Your discussion is not good example for illustration of flow's indentation bug. Compare two themes: ru:Тема:Sjnbtu70fpp8c990 and ru:Тема:Sjnbzj23r6t4lrs8 This themes looks equal, but in first one, replies sequence is like this:

***
├***
│ └***
└***

and in second - like

***
├***
├***
└***

I came up with three solutions:

• tree structure diagram. If I reply on higher level message, it creates a node on left vertical line that connects to my message. Like this:

***
├─***
│ ***
├─***
│ ***
***
***

• seperation rule. If I reply not on the previous message, but on higer level, it will divide my one. Like this:

***
│***
│***
├───
│***
│***
***
***

• extra indentations. Every next branching makes an indentation (reversial indentaiton system). Like this:

***
││***
││***
│***
│***
***
***

bump

Thanks for the ideas and feedback (both). :-)

There has been a lot of feedback that the current indenting system is a confusing mixture of the main external standard systems. The team is planning to re-examine the indent system, in the future. (Currently they're focusing on Echo/Notifications work). For now, I've added this topic to the (incomplete) list at Flow/Prior discussion-thread-roundup#Indenting Levels.

Hi @Tucvbif, the last time we discussed indentation we arrived to a model that I illustrated with this post.

It was a combination of your "reversal indentation" and "separation rule" solutions, where a second direct reply to a comment would push one level up the the previous thread of replies to that same comment, but this would happen only once per level.

I called that "Dynamic style", and at this later thread I posted an example of how it works with the content of a real conversation. I think that model best respects the expectations of experienced editors (having a real tree of comments), while avoiding deep threads for most conversations. If work on indentation is ever restarted, I'd like to explore that model.