Open tjhancocks opened 4 years ago
As an additional note on this. I'll not start work on this until @andrews05's PR has been merged, as its going to involve a fairly major change to the kas/rsrc
directory and contents. Reading these files is slightly more complex than writing them, and as such the reading implementation in Kestrel is more complex.
Further to that, this resource manager implementation will become a fresh basis for the libResourceFork / libResourceManager repository of the @TheDiamondProject. At which point both Kestrel and KDK will reference it instead.
Is your feature request related to a problem? Please describe. As it turns out, this development kit is going to need to read resource files as well as write them. This is also true of Kestrel itself. This means the two should share this implementation.
Describe the solution you'd like The ResourceFile management aspect of the KDK should be made into something that is reusable. It can still exist within this repository, and probably should exist in this repository as to maintain the the MIT License of the development kit. Kestrel will then include the entire development kit as a submodule/dependancy.
Given that the Kestrel engine will potentially need a copy of the development kit at compile time for assembling a bundled scenario, this is an obvious solution (at least for now).
However, it does require that the resource file implementation be completely independent of the rest of the assembler.
Describe alternatives you've considered Resource Manager lives in separate repository or is duplicated across codebases.