Please use this topic to suggest Wiki improvements and report issues with Wiki content.
2 Likes
Improvement:
It would be very helpful if it could be done? A flow chart(same as program been converted into flow chart) explaining general functions and basic concepts been used in a simple cocos2d-x game.
Issues:
This one is TBD since long time.
http://cocos2d-x.org/wiki/Node
1 Like
A complete hierarchy diagram of all the classes used in cocos2d-x as a whole.
Now we get (say) MoveBy is an action so we get only the hierarchy diagram in pieces.
I need to have a full hierarchy diagram of the entire cocos2d-x and these are present within them.
It would create a generalized idea.
Please do it. 
Thanks
1 Like
Hi, I’m new to cocos and every version I download I see setup cocos and create new project workflow is changing and the doc for that is outdated some folder doesnt exist in doc. please make an updated doc for installing with each release.
thanks.
You should follow the tutorials on the Wiki: http://www.cocos2d-x.org/wiki/Getting_Started_with_Cocos2d-x
Usage of Container Layer is outdated. Everywhere where it uses LAYOUT_LINEAR_VERTICAL as the enum format, it should be Layout::Type::VERTICAL.
Another thing I’ve noticed is instead of prefixed class names (UILayout), it’s now handled by namespace (ui::Layout).
http://www.cocos2d-x.org/wiki/How_to_use_CCHttpClient
cocos2d::network::HttpClient::getInstance()->send(request);
wont work:
- undefined reference to ‘cocos2d::network::HttpClient::getInstance()’
- undefined reference to
‘cocos2d::network::HttpClient::send(cocos2d::network::HttpRequest*)’
- undefined reference to
also I must use
#include "network/HttpClient.h"
using namespace cocos2d::network;
to make some error messages go away.
I know you’re probably already on it, but for Plugin-X I think the code snippet
jint JNI_OnLoad
{
JniHelper::setJavaVM;
PluginJniHelper::setJavaVM; // for plugins
return JNI_VERSION_1_4;
}
should be
jint JNI_OnLoad(JavaVM *vm, void *reserved)
{
JniHelper::setJavaVM(vm);
PluginJniHelper::setJavaVM(vm); // for plugins
return JNI_VERSION_1_4;
}
I think you are correct. I’ll pass it along, just in case. Thanks!
It needs to be clear on every Wiki which versino it applies to
I notice that
http://www.cocos2d-x.org/wiki/How_to_create_a_multi-platform_project_in_one_command_line
is outdated (I presume for V2.x) but also some of the text is crossed out - very confusing especially as this is one of the first pages a new user may come across.
If possible I would adopt a similar process to microsoft, where the documentation shows which version it applies to, but also allows the user to drop down a list of other version to see the appropriate page for that version
SUGGESTION ON IMPROVEMENT OF API
Please integrate the description of the physics classes, member functions etc in the api documentation by the final release of the cocos2d-x 3.2.
REQUEST TO -
@pabitrapadhy Can you tell me which classes you are seeing no description for? I just looked at PhysicsBody, PhysicsWorld, PhysicsContact, PhysicsShape and so far all of those are documented.
.cc @walzer
I’ll put this in the queue.
no i was talking about the description of the methods in the physics engine classes…
but i find it to be fixed by now.
but last time i saw… it wasn’t there… so i posted in a hurry…
thanks @slackmoehrle for responding to my post…
Is it possible to add some dropdown items to the forum reply ??
like cocos2d-x version.
platform
IDE
most of the problems in the forums are clueless which delays the help delivered to them
however we cannot make people to adopt this habbit any soon.
why not have this in the forum as an added functionality.
Sounds fair… ??