Does anyone know what if anything .cocos-project.json is being used for?
For SDKBOX I would like to keep a record of which packages have been installed for a project, and rather than litter the project folder with more little files, I would like to just add the records into .cocos-project.json.
Of course, some versions of cocos2dx don’t have that file, so in that case I was thinking of creating it, and since SDKBOX knows what type of project it is, I can fill that in too.
Thoughts?
I thought I was told once that this was in use for Cocos Studio or Code IDE, IIRC. But I don’t know if that is true and what it is really used for at this point in time.
We could run fswatch on the file and get notified when it is actually touched.
it’s definitely not CocoStudio, but perhaps the IDE. I am not going to remove anything, so it won’t hurt. I am more concerned that it is deprecated and might disappear in the future.
@mannewalis no idea. but using just one project file makes sense.
UPDATE: on the other hand, if you want to make sdkbox available for other engines it might make sense to have an sdkbox project config file… or not… I guess it depends on how it is going to be implemented.
Technically SDKBOX is a Cocos product, but those that are using SDKBOX with other engines might not know that so perhaps @ricardo idea is best to create a new file. Also, other engines are probably going to have their own way of storing this type of info and SDKBOX probably needs that in a uniform fashion.
@mannewalis
I will ask some one to take a look.
In fact. The file .cocos-project.json is used for command line tools : cocos2d-console.
console will parse the configurations in the file, then use the configurations to compile & run the project.