Well, I think code samples should not be in the documentation. The
documentation should provide links to the code samples in, as you say, a
place like the wiki. Code directly with the documentation is clutter. The
current system, where they are by default hidden, is a good one.
hi,
I think our general approach has been to try and make the
documentation better until those FAQs disapear.
Feel free to start a FAQ in the wiki :) That'd be cool. Especially
since then documentation writers could look at the FAQ and figure out
which parts of the docs to improve.
I'm not suc
I agree with a doctrine for syntax in the lists, and a FAQ for pygame.
Since FAQs tend to be updated, I recommend putting on pygame.org first,
until the common questions have been answered there. The FAQ should be
obvious, so that people would see it first, before the link to the pygame
users sub
Years ago, USENET groups and mailing lists would periodically post
Frequently Asked Questions lists to cut down on people repeatedly covering
old topics.
Such a thing might not be a bad idea for pygame-users, as we've had a lot
of similar questions come through over and over again. It might also b