15 minutes ago, MattGrandis said:
We've been mulling over whether it would be a good idea to be able to put the manifest.json OUTSIDE the zip file, but before you do any work in that direction (unless you want to), I'll try rewriting our code so it adds the manifest.json directly to the zip file. One thing though: it looks like the "old" way doesn't work anymore. It's throwing an error: "
Unable to read manifest. Check the manifest http parameter". See here:
https://www.commanderx16.com/emulator/x16emu.html?manifest=/emulator/9-chase-vault/ The manifest.json file still exists like before.
I am fixing that now... copy&paste bug. I wish I had some unit-tests that could have caught that.
In regards to the manifest.json separate from the zip, i thought about this too. Then inside the manifest we could have a link to the .zip file. also another thought if we do this, do we then really need the resources section or do we just load any file that is inside the zip the manifest is pointing to. That would make it easier to not have to maintain the list of resources to be loaded.
so the manifest could just be
{
...
start_prg: FILE.PRG
resource:
https://x16repos.s3.amazonaws.com/chase.zip }
I don't know, i kind of like that everything could be self-contained in one zip, but on the other hand it would simplify things. the developer would just upload a zip with all his x16 assets and just say what is the start_prg and don't worry about the resources section in the manifest