|
Re: New hints....
by Masem (Monsignor) on Feb 28, 2002 at 20:01 UTC
|
One thing I would like to see expanded in the hints below the postbox is the "where to post" question, specifically:
- the distinction between SOPW and Q&A. The latter should be more general perl questions and should be very short akin to FAQ questions (with a link to perlfaq); SOPW are more specific and may require a longer setup to explain.
- the distinction between Meditations and Discussion. The latter is for discussion on the mechanics and operation of PerlMonks the site, the former is for all other general perl discussion.
Still retain the links, but I think these two points should be clarified if we're going to add more to it to start with.
-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com
||
"You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important
| [reply] |
|
|
| [reply] |
|
|
Some questions/comments:
- The list of approved tags is not complete. I
imagine PRE was left out on purpose, but why list the
tags if it isn't a complete list and there's a link where
a complete list is available? I'd rather see that space
used for something else--in my experience trying to use
unallowed tags is something editors rarely have to fix,
compared to
- the misuse of PRE tags (which is why I think that
the line about CODE tags should be listed before
approved tags),
- posting in the wrong place (maybe SOPW should
be listed first, as it is where most people should post),
- people who aren't logged on (when they want to be),
- and poor titles. I'd rather see the things that
cause the most work addressed in the limited space
than the things which
are automatically taken care of.
- I agree with the person who suggested the mention
of search and super search.
| [reply] |
|
|
|
|
Pretty close, save that I wouldn't use abbreviations in the text here, since this should be considered newbie text.
But it was only meant to be a suggestion, or at least a starting point for additional discussion. :-) If others feel it's not needed, then it's not needed.
-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com
||
"You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important
| [reply] |
Re: New hints....
by shotgunefx (Parson) on Feb 28, 2002 at 22:11 UTC
|
What about
- Have you tried Searching to see if your question has been answered before?
Or something similar.
-Lee
"To be civilized is to deny one's nature." | [reply] |
Re: New hints....
by gav^ (Curate) on Feb 28, 2002 at 23:51 UTC
|
What about:
- using strict and warnings might be a good idea.
gav^ | [reply] |
Re: New hints.... (launching super search on the posts title)
by little (Curate) on Mar 02, 2002 at 07:20 UTC
|
just my .02
When one wants to post to SOPW wouldn't it be possible that when he hits the preview button to start a (super) search on the chosen title of his post and to return the top ten most relevant matches from former posts to SOPW entitled as: "Have you had a look at these previos Questions/ Threads?" on top of the preview page.
But those results shall only be root nodes and not replies as it happens to be when you actually do a search.
In this case one could still hold finishing his post while examining those results and in case cancel his post or proceed if he didn't find an answer.
Have a nice day
All decision is left to your taste
| [reply] |
|
|
Big ++ to demerphq!! I hope it gets approved!
I would also like to give a thumbs up to little's idea. I remember a time when I used to have no idea that I should search before I post.
--
Yes, I am a criminal.
My crime is that of defyance.
| [reply] |
(tye)Re: New hints....
by tye (Sage) on Mar 08, 2002 at 23:16 UTC
|
ar0n made a patch to clean up the HTML to be in line with our desire to be XHTML clean. This includes putting the tags in lower case. Unfortunately, the small font makes <tt> harder to read than <TT> so I dropped the <s and >s and then decided to save some space, giving this:
-
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: a, b, big, blockquote, br, code, dd, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, li, nbsp, ol, p, pre, 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 editor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
Note also that the list of tags is now pulled from the official list so it will automatically stay in sync with what is really allowed.
Feedback welcome.
-
tye
(but my friends call me "Tye")
| [reply]
[d/l]
[select] |
|
|
| [reply] |
Re: New hints....
by funky_aunt (Acolyte) on Mar 01, 2002 at 02:05 UTC
|
I would like to thank DeMerphq. As a perl neophyte any road signs pointing in the right direction are helpful. | [reply] |
Re: New hints....
by dws (Chancellor) on Mar 08, 2002 at 20:49 UTC
|
The patch is show up sporadically, and when is shows up when viewing a node, it appears to be a signature. I think it should only apply when actively posting or replying. | [reply] |
|
|
When I get time Ill go through and try to standardize where it shows up. But it could be a lot of patching, I make no promises.
Yves / DeMerphq
| [reply] |
