Changing the API documentation to a wiki

[Jelkimantis]

Can we change the API documentation into a wiki format that includes examples? 

I'm contemplating something similar to the PHP documentation where there are examples given in the API page and then you can log in and comment on the examples and give specific examples to a variety of problems.

This might decrease the number of "how do I use..." questions in the forums.

jsl

[jorrit]

The api manual is automatically generated from the source (daily). It is hard to make that a wiki. However, we used to have a comment system in the past so that you could add comments to every generated page. The cronjob that generated the documentation would make sure the comments were not discarded. We had to stop this comment system because it was misused for spam purposes.

Greetings,

[Jelkimantis]

Wow.  That's quite a neat bit of code, pulling the API from source.  Would it be feasible to develop a secondary documentation forum?  I hate to beleaguer the point, but I really want it.

Would it be appropriate to start such a section in the already existing wiki, essentially using the API tree as a starting point and putting in some code with explanations of what the code snippet does?

I know that my knowledge is limited in this respect, but as I gain knowledge I could increase my contribution, and others could contribute as well. 

So, the question stands, would it be appropriate to start building an explanation wiki of the API tree?  Or does the API tree change too dynamically to allow this type of endeavor?

jsl

[Vincent]

I think that topic was discussed in the past already, and the weak point of the wiki is keeping it up-to-date.
Even without API, some of the tutorials on the actual wiki are sometimes quite outdated,
and/or the CS version they cover is not even mentioned, thus leading to confusion.
Maybe some automation could be done, but I'm not sure anyone has time for that.
But the point remains, more examples, and more practictal ones, would be good...