11-04-2018, 08:36 PM
Hi,
The JSON format Curvy uses is a JSON based format that I made up for usage only inside Curvy, to share splines easily between different users, or to save/load them at runtime, or even as a way to batch process splines in the text format. So it's not a format that was made to be compatible with external tools as Adobe Illustrator. This being said, I tried to make it as easy as possible for any user to make Curvy compatible with any other JSON based format:
If you go to Curvy\ImportExport\Wrappers.cs, you will see two classes that represent the JSON equivalents of CurvySpline (namely SerializedCurvySpline) and CurvySplineSegement (namely SerializedCurvySplineSegment). By renaming, adding or removing fields in these classes, you control what Curvy seeks when reading or writing JSON files.
Curvy expects a file that is an array of splines. Your file is an array of layers, which in turn are arrays of splines. So you will have to handle this difference either at the file level (by putting all the splines at the same layer) or at the code level (by modifying Curvy's code reading the JSON files to add the notion of layers, in Curvy\Base\Editor\Wizards\ImportExportWizard.cs)
I know I dumped a lot of information here, so don't hesitate if you need me to explain further some point that might be not clear.
I hope this helped.
The JSON format Curvy uses is a JSON based format that I made up for usage only inside Curvy, to share splines easily between different users, or to save/load them at runtime, or even as a way to batch process splines in the text format. So it's not a format that was made to be compatible with external tools as Adobe Illustrator. This being said, I tried to make it as easy as possible for any user to make Curvy compatible with any other JSON based format:
If you go to Curvy\ImportExport\Wrappers.cs, you will see two classes that represent the JSON equivalents of CurvySpline (namely SerializedCurvySpline) and CurvySplineSegement (namely SerializedCurvySplineSegment). By renaming, adding or removing fields in these classes, you control what Curvy seeks when reading or writing JSON files.
Curvy expects a file that is an array of splines. Your file is an array of layers, which in turn are arrays of splines. So you will have to handle this difference either at the file level (by putting all the splines at the same layer) or at the code level (by modifying Curvy's code reading the JSON files to add the notion of layers, in Curvy\Base\Editor\Wizards\ImportExportWizard.cs)
I know I dumped a lot of information here, so don't hesitate if you need me to explain further some point that might be not clear.
I hope this helped.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.