RapidQ List Guidelines

Last updated December 8, 2019.

  1. Use English, please.

    This list is an English list. Please try to use English when communicating on this list. Bilingual messages are OK.

  2. Use meaningful subjects.

    Subjects should summarize you message but not be the whole message. Subjects like "RapidQ Crashes" and "HELP!" are not useful at all. They are too generic. More specific subjects like "RapidQ crashes when I call connect on a MySQL object" or "Help using two forms at once" are much better. Also, messages with a subject like "How do I print?" and no body are not helpful. Those messages are like newspaper articles that only have headlines.

  3. Include meaningful information.

    If you are having a problem with RapidQ, include any information that you think may be useful, including, but not limited to, Windows version and bitness (32- or 64-bit), any modified libraries you are using, versions of include files, and versions of other software programs on your computer.

  4. Post Sample Code!

    It is very hard to help you with a specific problem if you do not post sample code. When including sample code, please mark where it starts and stops somehow. For example:

    ' -- Start Code --
    DEFINT i
    FOR i = 0 TO 12
    NEXT i
    ' --- End Code --
  5. Store Source Code in the Files section.

    The Files section of this list is to be used for posting useful files. Materials for which you do not have permission must not be posted. Since it is simple to re-compile programs, only the source code for RapidQ programs may be posted in the Files section. Please try to keep the Files section as organized as possible. There are a number of sub-directories with (hopefully) self-explanatory names. If you don't know where to put the file, put it in the Miscellaneous folder. Someone will sort it for you.

  6. Use plain text e-mail messages.

    Plain text e-mail messages have many advantages over HTML ones. They are smaller, easier to format (especially on programming lists), and cannot cause security problems. The Groups.io platform enforces this, so any HTML formatting you use will get stripped out automatically.

  7. Quote the original message when replying.

    When you reply to a message, it is useful to know what you are replying to. Therefore, you should quote the original message. When replying, bottom posting is preferred over top posting. An example of bottom posting is:

    > How are you today?

    I am doing very well today.

    Bottom posting is preferred because it preserves the natural flow of conversations and reduces excessive quoting (See item 8.):

    Because it is hard to follow.

    > Why shouldn't I top post?

  8. Trim replies to context.

    If you are replying to only part of a message, only quote part of that message. For example, in this message:

    I would like to know how to show a web page in my program. Also, is there any way to change the text of my buttons?

    If you are replying to the first part, only quote it:

    > I would like to know how to show a web page in my program.

    Yes there is...

    If you are replying to both, put your response under the appropriate part. For example:

    > I would like to know how to show a web page in my program.

    Yes. See this URL...

    > Also, is there any way to change the text of my buttons?

    Yes. Just set the property...

  9. Start new threads.

    When composing a new message to the list, always start a new thread. This means that you must use Groups.io or your mail client's New message feature. Simply using its Reply feature and changing the subject does not start a new thread. If you fail to start a new thread, you message will get buried under some other message that probably has no relation to your message. If a user is ignoring that thread, they will not see your message.

  10. Do not use ALL CAPS.

    Refrain from TYPING IN ALL CAPITAL LETTERS. This is known as shouting and should only be use for emphasis. Consider other styles of formatting like:

    • This _word_ is underlined.
    • This **word** is bold.
  11. Keep your signatures short.

    There is nothing wrong with a signature, so long as common sense is used. A forty line signature is absurd. A general rule of thumb is 4--5 lines maximum. Also, using a signature deliminator between your message and you signature is VERY helpful. Those e-mail clients that support signature deliminators remove all text below them when replying, so your signature and the Yahoo Groups ads are not quoted. A proper signature deliminator is "-- " on a line all by itself. That is DASH DASH SPACE RETURN.

  12. Try to stay on-topic.

    This list is primarily for discussing RapidQ and technologies related to it. Off-topic messages are OK if they are kept to a minimum. Please prefix off-topic messages' subjects with "OT."

  13. Arguments will happen; handle them respectfully.

    Due to the nature of communication, arguments will happen. So long as they are constructive, arguments can be beneficial. However, the moment they denigrate in profanity, shouting wars, or insults, they must stop. If you feel the need to send an angry message, queue it in your outbox, wait a day, read over it again, and then decide whether or not to send it. Also, sometimes a topic is discussed so much that we end up going around in circles or not being productive. At that point, the thread will be declared dead and discussion on it should stop.

  14. Have Fun!

    That's enough guidelines! Programming should be fun, and so should this list. However, keep in mind the above guidelines.

Last updated: