Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New format .dbfactory #12

Closed
JekSun97 opened this issue Apr 16, 2024 · 6 comments
Closed

New format .dbfactory #12

JekSun97 opened this issue Apr 16, 2024 · 6 comments
Labels
help wanted Extra attention is needed

Comments

@JekSun97
Copy link

I wanted to update the version, but I didn’t see anything new except the new format (.dbfactory), can you tell me more about it, what is it for, when exactly does it appear, and why not JSON?

@Daylily-Zeleen
Copy link
Owner

Please refer to Readme or Release Note.

@Daylily-Zeleen Daylily-Zeleen added the help wanted Extra attention is needed label Apr 16, 2024
@JekSun97
Copy link
Author

Please refer to Readme or Release Note.

I read this and that, but I still didn’t understand the meaning of this format. =\

@JekSun97
Copy link
Author

all I understood is that if there is a json file, it will create a dbfactory file next to it, but why and for what purpose is still not clear.

@Daylily-Zeleen
Copy link
Owner

This plugin is not import .json anymore, a resource file with extension .dbfactory will be generated if there have xxx_ske.json/dbbin and xxx_tex.json.

You should delete .import files of .json now.

The reasom of this change is that .json is not resource file by default, and may be neglected when exporting, generate a new resource file to solve this problem.
In order to recognize the DragonBonesFactory resource file more easier, I use a new format dbfactory instead of res/tres.
That's all.

@JekSun97
Copy link
Author

This plugin is not import .json anymore, a resource file with extension .dbfactory will be generated if there have xxx_ske.json/dbbin and xxx_tex.json.

You should delete .import files of .json now.

The reasom of this change is that .json is not resource file by default, and may be neglected when exporting, generate a new resource file to solve this problem. In order to recognize the DragonBonesFactory resource file more easier, I use a new format dbfactory instead of res/tres. That's all.

That is, after each creation of the dbfactory file, the parent json file can be deleted?

@Daylily-Zeleen
Copy link
Owner

Daylily-Zeleen commented Apr 16, 2024

That is, after each creation of the dbfactory file, the parent json file can be deleted?

No,they should be keeped for VCS and exporting.

dbfactory just hold paths of DragonBones file (.json/.dbbin), and these files will be copy to .godot folder for exporting.

To get rid of .json after exporting, DragonBonesFactory will search the true path (.json/.dbbin) first, if not exists, it will find the files in .godot.

Please refer source code for more details.

You should delete .import files of .json now.

Just delete the .import file which are generated by importing .json by the old version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants