posted by
NCommander
on Thursday June 04 2015, @10:00AM
from the lets-do-this-right dept.
So as the post-upgrade dust settles, one of the big things still left on our usability TODO list is implementing inline reply and moderation for the site. A quick survey of our developers is that no one here really is super experienced in writing JavaScript code, so I'm putting a call for help to find someone to help implement and write this. For anyone getting interested in SN development, this appears to be a straightforward task. Here's the official requirements for the feature.
A user should be able to post and moderate comments without a seperate page load
If JavaScript is disabled for whatever reason, the site must degrade to the current click-to-post functionality. We don't want to force people to enable JS if they don't wish to. Dynamically rewriting the DOM to change links may be necessary, but this can be discussed
The rehash API must be extended to add this functionality; this should be relatively easy and straight forward; we have parts of the original AJAX code so this functionality may already be in place.
Contact me, or paulej72 on IRC, or post a comment below if you're interested in helping.
This discussion has been archived.
No new comments can be posted.
I'd like to see a feature which could improve usability a lot and requires no JS at all: Every comment already has an achor (a-tag) with the attribute name="[comment id]". So when replying to a comment or moderating, the redirection url can include the anchor (#).
Example: If i replied to the first comment on this page (name="191977"), the redirection url after submitting should be someting like https://soylentnews.org/meta/article.pl?sid=15/06/03/2213230#191977 [soylentnews.org], so that the browser takes me to the place I have been last. Same goes for moderation. It would be especially useful in long discussions.
Starting Score:
1
point
Moderation
+3
Interesting=1,
Informative=2,
Total=3
Extra 'Informative' Modifier
0
Karma-Bonus Modifier
+1
Total Score:
5
(Score: 3, Informative) by maxwell demon on Thursday June 04 2015, @12:35PM
The same could be used for the parent link whenever the parent comment is already displayed in the thread: There's no need to load the parent in a new page then; just repositioning the page using a link to the anchor is sufficient (that is, have as link target just e.g. "#191997"). If one really wants the comment in a separate window, that functionality is still just one further click away (namely by clicking on the comment number).
This would also help reduce the server load since a simple repositioning creates exactly zero load to the server; the browser does it all locally.
-- The Tao of math: The numbers you can count are not the real numbers.
If i replied to the first comment on this page (name="191977"), the redirection url after submitting should be someting like https://soylentnews.org/meta/article.pl?sid=15/06/03/2213230#191977 [soylentnews.org] [soylentnews.org], so that the browser takes me to the place I have been last. Same goes for moderation. It would be especially useful in long discussions.
If you want to go back to where you were, try the browser's back button ;)
We've looked at this before, its made more difficult by the simple fact that we don't know if a comment would be visible given a users preferences. I can think of a couple of ways to make it work though ...
(Score: 5, Informative) by sudo rm -rf on Thursday June 04 2015, @10:54AM
I'd like to see a feature which could improve usability a lot and requires no JS at all:
Every comment already has an achor (a-tag) with the attribute name="[comment id]".
So when replying to a comment or moderating, the redirection url can include the anchor (#).
Example:
If i replied to the first comment on this page (name="191977"), the redirection url after submitting should be someting like https://soylentnews.org/meta/article.pl?sid=15/06/03/2213230#191977 [soylentnews.org], so that the browser takes me to the place I have been last. Same goes for moderation. It would be especially useful in long discussions.
(Score: 3, Informative) by maxwell demon on Thursday June 04 2015, @12:35PM
The same could be used for the parent link whenever the parent comment is already displayed in the thread: There's no need to load the parent in a new page then; just repositioning the page using a link to the anchor is sufficient (that is, have as link target just e.g. "#191997"). If one really wants the comment in a separate window, that functionality is still just one further click away (namely by clicking on the comment number).
This would also help reduce the server load since a simple repositioning creates exactly zero load to the server; the browser does it all locally.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 2) by urza9814 on Thursday June 04 2015, @03:44PM
If you want to go back to where you were, try the browser's back button ;)
(Score: 2) by NCommander on Friday June 05 2015, @03:29AM
We've looked at this before, its made more difficult by the simple fact that we don't know if a comment would be visible given a users preferences. I can think of a couple of ways to make it work though ...
Still always moving