Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

I think the idea is great. I also agree it should be an option in the user profile.

Furthermore, I'd suggest that the default be "off", i.e. do not show rep. details. The reason for this is that a novice at the Monastery already has so much new stuff to discover. When the novice starts to find his/her way around here s/he will become more curious and start looking for personal configuration. It will then be a new discovery to find the detailed rep. information.

It should also be verified if this would have a negative impact on the database performance, in which case I would tend to say it's not worth it. (Performance is currently acceptable but not brilliant.)


Everything went worng, just as foreseen.


In reply to Re: Node Tension by Biker
in thread Node Tension by mojotoad

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.