View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 228 | Composr | core_cns | public | 2010-11-29 00:52 | 2012-03-12 17:46 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 228: Threaded comments | ||||
| Description | Threaded comments (for comment topics, not forum). | ||||
| Additional Information | Draw on Disqus on Slashdot for how to implement with good usability (not older style threading like trekweb.com). | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Time estimation (hours) | 10 | ||||
| Sponsorship open | |||||
| parent of | 379 | Resolved | Chris Graham | Thumbs up or down a post/comment |
|
|
This is being sponsored. I was asked to analyse http://www.dpreview.com/news/2012/01/06/Woodfordstandsaside and here are my implementation notes... 1) It has to limit how much it loads at once (in case there are loads of replies), yet we can't do pagination Solution) The example just seems to always load downwards, which I don't think is good, because it could be one high level reply has huge numbers of replies itself. I think we can algorithmically decide what subtrees to load initially, and what parts of those subtrees, to reach the best posts, and we can have "load more" links placed throughout as appropriate. 2) The conversation depth could get ridiculously deep, and then it would not display well. Solution) I think we'd just need to put a limit on it. People can use the Comcode 'quote' tag to also make it clear what they're replying to, if they are forced to not just keeping replying deeper and deeper. 3) Intuitive placement of reply form (not just at bottom) Solution) The example takes you to another screen to reply I think (although I'm not sure because I wasn't logged in to check). I think we can have a reply button beneath each post that puts the reply form in that spot as required. 4) Arranging by 'likes' when 'likes' are actually happening on different levels Solution) The example again doesn't do it well. You can see it only considers the like ordering on each level at a time. So there are some higher rated things low down because they are beneath unrated posts. I think we can do better, in combination with the solution to '1'. 5) How to do for forum - do users get a choice of what to make - or is it per forum - or does a topic have two view modes Solution) I think you should be able to configure a forum as a "threaded" forum or a "linear" forum. Then any topics made in it are handled accordingly. I've seen forum systems that have two view modes, but I think that is a terrible idea because it's just going to confuse people and make a mess. 6) Not table based Solution) Composr's forum topics are shown in a table because that's what it really is, but this definitely isn't. So there'd be a lot of reworking. But that's fine. |
