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

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

Sorry for the rtfm question.  I'll look for that! Thank you so very much.  This is fairly daunting to get into, but I'm enjoying muddling!

jsl

I'm attempting to compile simple.cpp using crystalspace1.2.

At first, I had difficulty getting it to begin compiling, I changed the line to <crystalspace-1.2/crystalspace> from <crystalspace>

then it began compiling, but it didn't find a whole slew of headers.

So, i'm a little confused.  It seems like I should set the environmental variable for crystal space to include /usr/local/include/crystalspace-1.2/, but it doesn't seem evident from the documentation.

i'm developing on an Ubuntu Linux system, CrystalSpace 1.2, Kernel 2.6.24-19, g++ 4.2.3, glibc 2.7

Walktest works fine.  I can't get gcc to dump it's output to a file to attach it here.  (>> isn't working right now...)

jsl