Beta

Slashdot: News for Nerds

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Ignore this JE, unless you work for Slashdot

squiggleslash (241428) writes | about 6 months ago

User Journal 4

You haven't (I think?) open sourced the new Slashcode, so consider this my contribution.

Executive summary

You haven't (I think?) open sourced the new Slashcode, so consider this my contribution.

Executive summary

  • This is something to aid functionality testing.
  • There is formatting involved. This line, for example, is part of a unordered list (ul)
  • This document is both a test case (and has been posted twice, once as a journal entry, and once as a comment) and a functionality checklist.
  • There should be four bulleted list items here, a blank line above the first bulleted line, and "Executive summary" written in bold above that. Then another blank line and so on, but you get the picture. Underneath "What we, the users, are looking for" (which is in bold too) is a numbered list (ol). Take a gander at the source if you need to.

What we, the users, are looking for

  1. We should be able to read the discussions, nested, with some way to filter by moderation level
  2. Comments below our moderation level (or blocked for any other reason) should not appear, and neither should subthreads of those comments. We should be notified if such comments exist.
  3. Comments should be correctly formatted
  4. It should be easy to add a comment to a discussion starting a new subthread, or respond to an existing comment
  5. It should be immediately obvious how to format the comments we're writing.
  6. We should be able to easy visit a user's profile or our own profile
  7. We should be able to see what we've (or any user has) written (paged if necessary/desirable), with recent activity being prominent, and know what activity (moderation and number of replies) have centered around each contribution
  8. We should be able to visit a comment in isolation and see and interact with the discussion of that comment.
  9. We should be able to see journal entries written by a particular user, in order latest to earliest (paged if necessary/desirable), seeing the full content of each
  10. We should be able to post a journal entry from a button clearly visible on the front page and on pages relating to journals or ourselves
  11. We should be able to see all journal entries written by our friends (or by some equivalent means whereby we can build a list of users whose journal entries we're interested in) in order latest to earliest.
  12. We should be able to open any journal entry and, if discussion is ongoing, contribute to the discussion in the same way we do front page articles
  13. We should be able to add users to our friends list, or our foes list, or equivalent functionality
  14. We should have some way of using our friends and foes list to change what comments we see in a discussion at each moderation level. Alternatively we should have some other means by which to identify users whose journals we want to read, users whose comments we always want to see, and users whose comments we never want to see.

Nice to haves

In the words of every Slashdot user ever:

What's taking so long with the unicode support, man?

Also most websites let you edit comments, even if only for a window of time immediately after they were posted. And isn't it rediculous we don't have a spell checker? (Answer - not really, Firefox has that, but I thought I'd mention it because it's a common complaint.)

This line should stand on its own and have blank lines above and below it.

This line and the next one should be paired. There should be a blank line above this one but not below it.
This line and the previous one are paired. There should be a blank line below this one but not above it.

Also everything above should be in the same font. Just saying.

cancel ×

4 comments

And here it is again, as a comment (1)

squiggleslash (241428) | about 6 months ago | (#46218499)

You haven't (I think?) open sourced the new Slashcode, so consider this my contribution.

Executive summary

  • This is something to aid functionality testing.
  • There is formatting involved. This line, for example, is part of a unordered list (ul)
  • This document is both a test case (and has been posted twice, once as a journal entry, and once as a comment) and a functionality checklist.
  • There should be four bulletted list items here, a blank line above the first bulletted line, and "Executive summary" written in bold above that. Then another blank line and so on, but you get the picture. Underneath "What we, the users, are looking for" (which is in bold too) is a numbered list (ol). Take a gander at the source if you need to.

What we, the users, are looking for

  1. We should be able to read the discussions, nested, with some way to filter by moderation level
  2. Comments below our moderation level (or blocked for any other reason) should not appear, and neither should subthreads of those comments. We should be notified if such comments exist.
  3. Comments should be correctly formatted
  4. It should be easy to add a comment to a discussion starting a new subthread, or respond to an existing comment
  5. It should be immediately obvious how to format each comment.
  6. We should be able to easy visit a user's profile or our own profile
  7. We should be able to see what we've (or any user has) written (paged if necessary/desirable), with recent activity being prominent, and know what activity (moderation and number of replies) have centered around each contribution
  8. We should be able to visit a comment in isolation and see and interact with the discussion of that comment.
  9. We should be able to see journal entries written by a particular user, in order latest to earliest (paged if necessary/desirable), seeing the full content of each
  10. We should be able to post a journal entry from a button clearly visible on the front page and on pages relating to journals or ourselves
  11. We should be able to see all journal entries written by our friends (or by some equivalent means whereby we can build a list of users whose journal entries we're interested in) in order latest to earliest.
  12. We should be able to open any journal entry and, if discussion is ongoing, contribute to the discussion in the same way we do front page articles
  13. We should be able to add users to our friends list, or our foes list, or equivalent functionality
  14. We should have some way of using our friends and foes list to change what comments we see in a discussion at each moderation level. Alternatively we should have some other means by which to identify users whose journals we want to read, users whose comments we always want to see, and users whose comments we never want to see.

Nice to haves

In the words of every Slashdot user ever:

What's taking so long with the unicode support, man?

Also most websites let you edit comments, even if only for a window of time immediately after they were posted. And isn't it rediculous we don't have a spell checker? (Answer - not really, Firefox has that, but I thought I'd mention it because it's a common complaint.)

This line should stand on its own and have blank lines above and below it.

This line and the next one should be paired. There should be a blank line above this one but not below it.
This line and the previous one are paired. There should be a blank line below this one but not above it.

Also everything above should be in the same font. Just saying.

One other comment (1)

squiggleslash (241428) | about 6 months ago | (#46218631)

The checklist is essentially a list of things that work, or almost do ;-), in the current system that one would reasonably expect to be in the new version if the aim is equivalent functionality. I'm not assuming anything, and it could be you intend to, say, get rid of "Friends and Foes" or journals or many other things. I'd recoommend against removing journals, and against removing friends and foes without a good replacement - Slashdot used to have a thriving journals circle system before D2 kinda upended everything - but I'm assuming you'll probably want to keep them and hence putting in them in the list. It's there as something to start with, or integrate into your own checks.

And even if you take none of the functionality points as something you want to use, at least you have a formatted document you can make sure the CSS works with.

Editing comments (1)

gmhowell (26755) | about 6 months ago | (#46223417)

No. No editing comments. There's no reason. You can post a followup if you screwed up. Permanency has value.

Re:Editing comments (1)

squiggleslash (241428) | about 5 months ago | (#46227445)

You can post a followup if you screwed up.

If only that were true... There's been way too many times I've posted something, seen immediately a major mistake that will make it misunderstood by the majority of readers, tried to follow up, and been locked out by Slashcode's "Anti-spam" thing. By the time I've been allowed to reply to my own comment, it's too late. It's also worth pointing out a response to a mistake by you doesn't guarantee the response will be read.

The Guardian's website lets you edit anything you've posted within twenty minutes of you posting it, and I've seen that elsewhere too. Something along those lines would be great. People can and do f--- up. The purpose of a discussion is to exchange ideas. It's one thing when someone misreads you and goes off on a tangent as a result, it's quite another when someone reads something you did say that wasn't what you intended to say.

Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Create a Slashdot Account

Loading...