@zhangxm Please include the vscode debug extension in the main download zip. It works really great for JSB debugging and including it here will help more people find out about it. Web debugging already worked great with vscode chrome extension.
Looking forward to intellisense and cmd+click support in vscode.
@zhangxm Do you mean that intellisense in vscode works for JS projects made using creator? Which docs does it need? I could only find details on vscode site about adding typescript definitions etc…
By doing command+click on a variable name in IDE, it usually takes the user to definition of that function, class, or object etc… This makes it easier to jump around in code, and also to dig into cocos code to see why cocos is not doing what we need or how to make it do something.
But this works only when intellisense works. I tried webstorm, and it is able to show full auto-complete suggestions and do command+click for “go to definitions” for a cocos2dx 3.12 JS project without needing any configuration. Looks like it is a problem with vscode because it is geared more towards typescript.
@schngrg creator uses another version of cocos2d-js engine, and it uses its own format comment that can be parsed in runtime. And i use the parsed result to generate a typescript declaration which makes intellisense work.
@netunlimited about c++ support for cocos creator and Apple TV support, let’s ask @ShunLin.
@zhangxm OK, thanks for this information. It is really a vscode limitation because webstorm is able to do autocomplete and cmd+click directly from .js files for cocos2d-js, without needing any configuration or TS definitions.
Does the team plan to add similar comments and TS definitions support for the standalone cocos2d-js engine?
I tried to look at the cocos2d-js engine in cocos creator and there are some interesting changes and improvements in the engine, like in the way classes are defined. For a new cocos2d-js project, should we use standalone cocos2d-js engine or the engine in cocos creator (as a standalone engine without creator)?
We are not using Creator due to how we have implemented our project in C++ and we plan to follow similar structure with JS. For example, we need device orientation change support and defining sprite position and sizes based on physical screen size. We dynamically calculate the sprite size/position values using device DPI and screen size, and we change the design resolution to match screen size on orientation change or browser resize. It looks like with cocos creator we will need to choose a fixed design resolution and specify sprite size/position in pixels. In code we can specify things like “sprite.y = winSize.y-10;” or more complicated calculations based on device DPI.
As in our case all size/positions are to be set in code, then I am not sure if using creator will help because we won’t be able to use it for designing etc. I am slightly confused by all the ‘good’ options that cocos2d family gives. Our current project is in cocos2dx c++ and we are reimplementing it in cocos2dx-js for web support using the standalone js engine. Should we instead use the 1) creator or 2) the creator’s js engine (as a standalone engine without using the creator IDE)?
On Android 5+ device, now cocos 3.12 will auto hide the navigation bar, if you use TextField to show a virtual keyboard, then press virtual button to hide the keyboard, the navigation bar will not hide automatically. the other thread
How to use android-studio project with precompiled libs? I’ve generated them using “cocos gen-libs”, then I modified “settings.gradle” and placed absolute path to libcocos2dx project. Next, I modified “build-cfg.json” like this:
@zhangxm Sad to hear that. And …willlcocos creator support windows phone in the future?
Additionally, we are facing this isssue when trying to build android version. Please help us, the isssue is here: https://github.com/cocos2d/cocos2d-x/issues/16169
thanks so much