Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Show READMORE in Posts

by shotgunefx (Parson)
on Sep 30, 2002 at 08:25 UTC ( [id://201645] : monkdiscuss . print w/replies, xml ) Need Help??

Often I'll think twice about front-paging a large node because I'm concerned that the manifesto might not have a <readmore> tag.

It would be nice if it rendered a grayed out <readmore> tag or some other indicator of it's existance.


"To be civilized is to deny one's nature."

Replies are listed 'Best First'.
Re: Show READMORE in Posts
by dws (Chancellor) on Sep 30, 2002 at 08:52 UTC
    Often I'll think twice about front-paging a large node because I'm concerned that the manifesto might not have a <readmore> tag.

    If you see a node that you truly think is worthy of being on the front page, then front-page it and consider the node, asking for a readmore to be added. A crew of editors is standing by, happy to add the occasional <readmore> (or the more occassional <code> tag).

      Well we get back into what's supposed to be "truly worthy". I don't front page nodes that often, I usually only do it if the post is above average or the problem really interesting. But I've seen many discussions around here saying that the The Monastery Gates should be representitive of what's going through the site and not just excellent posts.

      But your point is taken. Oddly enough, I felt a little deja-vu posting this and I guess this is why.


      "To be civilized is to deny one's nature."
      Another thought would be that you get a gentle reminder when previewing a large node to add readmore tags. Which if you are going to do that, well then you might as well check for sigils and remind them to add <CODE> tags.


      "To be civilized is to deny one's nature."
(kudra) Re: Show READMORE in Posts
by kudra (Vicar) on Sep 30, 2002 at 10:33 UTC
    I read this question differently than the previous answers. Instead of 'how to get a readmore tag added to a post', I see 'how to tell if a post has a readmore tag or not'.

    If that's the question, then the simple solution of course is to simply view the source and look for a readmore tag. I guess I see formatting as the kind of thing you hopefully don't notice when it is done properly, not the sort of thing you want to display.

    Besides, if you give some indication of readmore tags, what about other formatting that could be wrong? For example, try to tell the difference between someone who put code in pre and tt tags from someone who put it in code tags if you don't have line wrap set. I just don't worry about it--I figure soon enough someone with line wrap will notice and consider it.

    So I'm with the others in saying just go ahead and fp the node. If you note that it is lacking a readmore tag, consider it. If you don't, someone else probably will.

      Other formatting is easily obvious if you have usersupplied CSS, since one can't add class attributes to tags when posting. My stylesheet renders class="code" with a blue border and font, so it's immediately obvious whether someone just inserted PRE tags or properly used CODE ones.

      READMORE on the other hand is harder, a small indication of its presence would be helpful. Even though I do agree with your assessment that the current situation is just fine, I'd find it easier than having to view source - or worse yet, check the gates to see if it shows with a link.

      I could live without it, but would enjoy having this feature. Of course, someone has to code it. Seeing as I was recently welcomed among the ranks of the pmdevils, maybe that could be my first contribution. :-)

      Makeshifts last the longest.

        Sounds like a good idea. (Specificly, I'd like <readmore>s to show up as <hr>s when they're being looked at directly.) Or, we could do what livejournal does, which solves this problem (though it isn't as much of a problem there), and gives the user more control. LJ has an <lj-cut> tag, which can look like <lj-cut text="Example cut...">stuff inside the cut</lj-cut>. That renders as ( example cut ) in a cutting context, and ( example cut )
        stuff inside the cut
        when not. (If there is no close tag, then the cut is taken to last until the end of the post.) That would be significantly more work to implement, though.

        Oh, and welcome to the team, Aristotle. (/me takes a moment to bask in the minor glory of a self-coined term catching on.)

        Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

      No but they are similar requests. I wasn't aware that readmore tags showed up in the source for a page. Thinking about it, as I said to dws, a gentle reminder during preview for readmore and code tags isn't a bad idea. I understand the Editors can and are willing to add the appropriate tags, but it would be better if they never had to at all. Which will never happen of course :)


      "To be civilized is to deny one's nature."
Re: Show READMORE in Posts
by Marza (Vicar) on Oct 01, 2002 at 07:10 UTC

    You should not be concerned about READMOREs for front-paging. If it is good, it should be front-paged no matter what. An editor will come along and "repair" it when he sees it.

    More of a question to the others but would it be possible to automagically add the tags?

      True but a gentle dope slap while previewing might make less work for the editors. (Not that I've heard them complain...)


      "To be civilized is to deny one's nature."