Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This is the best feature ever! You rule! I wish I could be just like you!
    • This is the best feature ever! You rule! I wish I could be just like you!
      Dude, have some dignity.
      • This is the best feature ever! You rule! I wish I could be just like you!
        Dude, have some dignity.
        Oh, you only wish you could be as cool as me.
        • This is the best feature ever! You rule! I wish I could be just like you!
          Dude, have some dignity.
          Oh, you only wish you could be as cool as me.
          I hate you! Moooooooom!
          • I don't see a 'quote' button. Where did you hide it?
            • I don't see a 'quote' button. Where did you hide it?
              Ah, forgot to mention one thing: you need to have Discussion2 turned on. You should see "Slashdot's New Discussion System Testing" under "Discussion Style" on your comment preferences [perl.org].
              • O well. No quotes for me then.
              • I don't see a 'quote' button. Where did you hide it?

                Ah, forgot to mention one thing: you need to have Discussion2 turned on. You should see "Slashdot's New Discussion System Testing" under "Discussion Style" on your comment preferences [perl.org].

                Speaking of which, is use.perl running an older slash? The floating comment thingy works fine for on Slashdot (sites in the left column), but on use.perl it obscures the top of the screen.

                Why yes, I am a Safari user. :-)

                -Dom

                • Speaking of which, is use.perl running an older slash? The floating comment thingy works fine for on Slashdot (sites in the left column), but on use.perl it obscures the top of the screen.

                  No, useperl is actually a newer version of slash. It's just a design difference. useperl actually has no room on the lefthand side. We'll be cleaning up the horizontal bar though, sometime soon.
              • I don't see a 'quote' button. Where did you hide it?
                Ah, forgot to mention one thing: you need to have Discussion2 turned on. You should see "Slashdot's New Discussion System Testing" under "Discussion Style" on your comment preferences [perl.org].

                Do the titles have to cascade in this mode?

                • Ah, forgot to mention one thing: you need to have Discussion2 turned on. You should see "Slashdot's New Discussion System Testing" under "Discussion Style" on your comment preferences [perl.org].

                  Do the titles have to cascade in this mode?

                  I don't know what you mean. Please explain titles/cascade.
                  • Ah, forgot to mention one thing: you need to have Discussion2 turned on. You should see "Slashdot's New Discussion System Testing" under "Discussion Style" on your comment preferences [perl.org].

                    Do the titles have to cascade in this mode?

                    I don't know what you mean. Please explain titles/cascade.

                    They do this:

                    Re:
                        Re:
                            Re:
                                Re:

                    • OK, now explain "have to." :-)

                      The way it works is that if the comment is a reply and has the same subject line, then we just use "Re:" in "abbreviated"/"oneline" mode, to reduce clutter and take up less space. There's no way around that currently.

                      Does that answer your question? Would you prefer the whole subject line be displayed?
                    • OK, now explain "have to." :-)

                      The way it works is that if the comment is a reply and has the same subject line, then we just use "Re:" in "abbreviated"/"oneline" mode, to reduce clutter and take up less space. There's no way around that currently.

                      Does that answer your question? Would you prefer the whole subject line be displayed?

                      I would actually rather it do this:

                      Re:
                      Re:
                      Re:

                      That way it stays on the "page".

                    • I don't understand. They are indented because they are children. If they were immediately below instead of indented, they would look like children of a common parent, instead of children of each other.
              • Ah, forgot to mention one thing: you need to have Discussion2 turned on.
                This convinced me to turn on Discussion2.
  • The quote button indeed rules. Quite a lot. Thank you!

    I noticed quoting is done by by wrapping a <quote> tag around quoted text. Is this tag new? Is it documented somewhere?

    HTML's <q> and <blockquote> have a cite attribute for indicating the source of a quotation. Is anything like that supported for <quote>? If so, is there any possibility of having the quote button automatically add attribution?

    • quote is a new "tag" we made up, like ecode. We are tossing around ideas for attribution; co-opting the cite attribute is a good idea, thanks.
      • We are tossing around ideas for attribution

        An idea I just had is that you might use the cid (or whatever the post number is, the post I'm quoting is 51856) as the value of the cite attribute.

        A common use-case for me on Slashdot is seeing a reply buried 5 levels down quoting something and responding to it, but none of its parents are displayed; so I have to use the "Parent" links to traverse up the thread until I find the quote. It would be stellar if I had some way of going directly to the quoted post. (Of course, this still doesn't handle the UI

        • We are tossing around ideas for attribution

          An idea I just had is that you might use the cid (or whatever the post number is, the post I'm quoting is 51856) as the value of the cite attribute.

          Yeah, another good idea. I was thinking of merging the user and CID, but ... why CID knows UID.

          The question is, though, how to catch that information and use it. I have some ideas, and it's not hard, but then when we come back with nested quotes, it becomes kinda hard. See here, I clicked Quote, and it took the <div class="quote"> around your quote of my comment, and turned it back into <quote>, because, we don't want to leave it as <div class="quote"> for two major reasons: it's ugly t

          • Interesting. I had always assumed that Slash stored the original representation of whatever a user entered so that editing was possible, and rendered that as "output" HTML when dispaying a page (and possibly cached the rendered version).

            I'm really impressed that you're able to roundtrip everything with the quote button, if my assumption was incorrect.
        • That’s not how it works. The only valid values for the cite attribute are URIs.

  • One other feature I'd really like to see here is for the Subject field to be pre-filled with "Re: ORIGINAL SUBJECT", like in e-mail clients.
    • One other feature I'd really like to see here is for the Subject field to be pre-filled with "Re: ORIGINAL SUBJECT", like in e-mail clients.

      It is. It's only not prefilled if you are replying to the story/journal/etc., because then almost every comment would have the same subject as the story title. We don't want that, so if you respond to the story itself, you have to add your own subject. But if you reply to another comment (as I am doing here), then it is prefilled (as it was here).

      • Ok. That doesn't make sense to me.

        Why wouldn't you want the same subject? That's the current context in which you write the reply. If the conversation changes to something else, then you change the subject.

        But never mind, if you already think of it as a feature I doubt I'll change your mind.