Looks like the Guidelines should be added to a couple of the other forums, esp MFC...

__________________

The 3 Laws of the Procrastination Society:
1) Never do today that which can be put off until tomorrow
2) Tomorrow never comes

Yes. I agree with that.

The first thing should be of: Which questions should be posted in Visual C++ forum and which in C/C++ forum.

Some always post C/C++ questions in Visual C++ forum because they use visual C++.


Paramesh.

__________________

Don't walk in front of me, I may not follow.
Don't walk behind me, I may not lead.
Just walk beside me and be my friend.

Thank you for the suggestion. If you would like to suggest what to include in the guidelines itself, that would be great (like the one you did for the C/CPP forums).

I plan to upgrade the forum soon; they went and released a new version of the script recently , so I intend to work on it at gidforums.net for a few days before making the changes.

__________________
J de Silva
Learning Journal | GIDForums™ | GIDNetwork™ | GIDWebhosts™ | GIDSearch™

I can't think of anything specific for other forums. MFC could take the guidelines as weitten I suppose. PHP might only need the code tag changed. Other forums I'd leave additions/changes to those that know the forum better.

__________________

The 3 Laws of the Procrastination Society:
1) Never do today that which can be put off until tomorrow
2) Tomorrow never comes

I am thinking of NOT putting the guidelines in a thread, even a sticky one.

I'd like to add it to the top of the forum(display) pages. To view an example, you'd have to log out and go to, say: http://www.gidforums.com/f-36.html.

The paragraphs introducing the topic for the forum is only displayed to Guests and Members: Level 1. I can write these forum-specific "welcome" messages to include the really important guidelines, if any.

__________________
J de Silva
Learning Journal | GIDForums™ | GIDNetwork™ | GIDWebhosts™ | GIDSearch™

Excellent! I like this idea. Or just click a link in the introduction, right?

__________________

The 3 Laws of the Procrastination Society:
1) Never do today that which can be put off until tomorrow
2) Tomorrow never comes

Looks good. I personal think that it would look better that way. It may just be the color but either way I like it.

__________________
If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.

RE: http://www.gidforums.com/t-9584.html

A few suggestions.

Summarize with a list at the top. Shorten intro. Use hyperlinks so someone can read the relevant descriptive section(site admin work). Be specific and complete in the descriptions.
e.g.,
REnumber and combine the body text to the new list.
1: (link to #5)
2: (link to #2 & #4)
3: (link to #1)
4: (link to #3)
5: (link to #7)
* (link to #6, #8, #9 & #10)

The document needs a conclusion. Use part of the intro:

And add
-- GID Staff & Moderators
at the bottom, presuming the staff & moderators all agree, of course.
It makes it a more "official" document.

Also:
The section on using code tags is not complete because it does not mention "other" so add what to do with those to 1.A.d. section.

As mentioned elsewhere, before I found this thread, I suggest changing the title of the "Guidelines" post to just:
BEFORE POSTING, Please Read This!

I spent a lot of years managing people for writing and managing documents called "planning" for electronic assemblies. I learned quite a few things about getting people to actually read the document BEFORE doing the work. It ain't easy...
You might want to add [BLINK] to the post title's html code...

I had difficulty with the document because of the "tagindicator" info. After a few posts, it appears that what you really want someone to do is use the PHP and HTML tags wraps but substitute c or cpp, JAVA, CSS, etc... for the "CODE" word in the CODE wrap block( at least until such time as the CODE tags wrap can be enhanced to include c, cpp, css, java, xml, etc... wraps as a clickable widget ).

You can call me a Herbert but I like the rules since most of them cover what I keep having trouble with for posts in other forums. Thanks for taking the time to make them. Good Luck enforcing them.... you're going to need it.

And, since I'll probably forget later, I want to also say Thanks for all the effort to parse the code and add highlighting as well as other things you admins and moderators do here at GID!

c-ya