> i suggest the scheme of questions and answers; such as:
> 1- how to display a message box
> answer: a complete small example with notes.
> 2- how to write text on a text box
> 3- how to retrieve text from a text box
> 4- how to color a word in a rich text box
> 5- how to retrieve the index of an item in a ListBox
> 6- how to use the trackbar, and the scrollbars
> 7- how to plot a pixel, a Line, ... , on a form or a picture box.
I think that's a good idea. People can propose questions to a
coordinator, and a volunteer can answer the question, including code
Of course, we could probably also harvest a bunch of the most frequently
asked questions from the mailing list to start with.
I agree that an answer should, whenever possible, be a complete working
example. (Preferably one that is as small as possible while still
completely answering the question).
> and up to 1001 questions or more, with full answers, and notes.
> with sections for the totally beginners.
I would suggest a from-the-ground-up tutorial. The documentation doesn't
provide much help there. When I was first learning, I had to spend hours
looking through the source code and researching on MSDN to figure out
how things work.
(I have not looked at the current wiki - perhaps it has already
addressed this concern.)
Also, since wiki-spam has apparently been a problem in the past, I would
recommend requiring registration to edit the wiki. I know that some
wikis provide that option, although I don't know whether MediaWiki does
so, since it was designed for the anybody-can-edit approach of Wikipedia.
If we do require registration to edit the wiki, we'll need a question
submission form for those without editor rights.
Anyway, I am willing to provide some answers. I am a student with a
heavy schedule this semester, but I'll do what I can. Exams will be in
mid-January, and after that the next semester is supposed to be lighter
on classes (although I'll have a major project I'll be working on from