Tutorial Rating

[Robin]

Thanks to Cruzn's fantastic work, threads created in the tutorial section are now open to ratings from users.

To rate a tutorial topic, you can find a small combo box in the bottom right (subsilver2) or the top right (prosilver). Using these ratings, it should give people a better idea of how good a tutorial actually is, without having to read through the entire topic.

Here's some simple guidelines for when rating a topic. They're more 'general' guidelines than technical ones:

• Is the tutorial properly explained? A good tutorial will always explain why it's doing something.
  
• Does the tutorial give a full description of it's features? A good tutorial will always give a full feature list.
  
• Is the tutorial layed out in a sensible and intuitive way? A good tutorial will always be easy to read, and scan for information.

If you're writing out a tutorial, and you get some negative feedback or poor ratings, try and read through your tutorial as if you'd never seen the code before. Remember, the community here aren't all completely fluent in VB6 and Mirage's project structure, so help them along and try and explain anything which you've done out of the ordinary.

eg, if you're declaring something as a variant, as it's being used in a function which can be referenced with any data type, then explain this. A simple comment or two briefly saying why something is done, is much, much more useful than a few comments which just say 'Declare as variant.'

Also, if your tutorial has received a lot of poor ratings, and you have re-written or fix the tutorial, please send a PM to a moderator or administrator with a link to the topic and a request to reset the rating, so they reset the ratings of your topic. If you've spent the time to re-write the tutorial, or fix its faults, then it's only fair that you get a fresh batch of ratings and feedback.

Yours,
Robin