DSP Parser is currently under a work-in-progress to be turned into a library that can be installed.
The goal is for tools to be able to include dsp-parser into their build pipeline.
Most prominently for dsp-ratios & factoriolabs.
Originally dsp-parser was setup as standalone scripts that would be executed manually.
I need to think of a good API that would work, probably start with pseudo code of what a good interface might be and then work backwards to make it a reality. Rather than writing to files directly, it should be able to return data.
Help users be able to a) export icons, b) generate spritesheets and/or c) handle the raw textures to do whatever themselves.
Need to reshuffle the internals again after the major upgrade in handling the Desc/Config objects. Would be good for users to be able to import game constants and maybe have details on the type shapes.
Also maybe could re-use type shapes as makeshift TypeScript types via JSDoc?
DSP Parser is currently under a work-in-progress to be turned into a library that can be installed.
The goal is for tools to be able to include dsp-parser into their build pipeline. Most prominently for dsp-ratios & factoriolabs.
Originally dsp-parser was setup as standalone scripts that would be executed manually.
I need to think of a good API that would work, probably start with pseudo code of what a good interface might be and then work backwards to make it a reality. Rather than writing to files directly, it should be able to return data.
Help users be able to a) export icons, b) generate spritesheets and/or c) handle the raw textures to do whatever themselves.
Need to reshuffle the internals again after the major upgrade in handling the Desc/Config objects. Would be good for users to be able to import game constants and maybe have details on the type shapes. Also maybe could re-use type shapes as makeshift TypeScript types via JSDoc?