Thank you for clarifying that. The problem with the docs is not that they are misleading, or overly ambiguous. The problem is that many sections are too brief. Much confusion could possibly be avoided by making them more verbose and explicit, as well as providing more examples. I understand that the samples provided in the source package serve to show how to use the framework, but I'm sure that including some bits of example code in the programming guide would provide a much better context for understanding the individual functions, as they are presented.
The official python library reference does an excellent job of this, by providing small usage examples with each entry. This makes it easy to understand a function without having to decypher a whole program. In conclusion, the current presentation is by no means bad, and I'm learning a lot by going through all the examples and seeing stuff work as a whole. However, there is much potential for improvement. I perceive the main weakness of cocos being that its community is so small. Unless you are working with the cocos iphone stuff (and even then) it's difficult to get anything from stackexchange. Making the docs more newbie friendly may help grow the community, who knows. -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cocos-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
