@Christoph-Hart said in File system allow for binary write/load:
Yeah, just create the JSON file on your server and query it on load (or if you let the user click a refresh button if you don't want it to call home automatically). This way you will always have an up to date list of expansions (otherwise you need to update the main plugin for each expansion that comes out after release). Then merge it (or use a separate JSON file) with the favorite property (or anything that comes from the user).
well--- this is a bit confusing. I'm pretty sure I dont need a new plug-in each time I have a new expansion.
All I need do is get the plug-in to read the list of installed expansions with:
const var appDataFolder = FileSystem.getFolder(FileSystem.AppData);
const var metaDataFolder = appDataFolder.getChildFile("ExpansionMetaData");
const var fileList = FileSystem.findFiles(metaDataFolder, "*_expansion.json", true);
This gives me a list of all the currently installed expansions, which is actually what I care about, and each *_expansion.json file tells me all about the "stuff" in the expansion e.g:
{
"EName":"Substrate",
"ELoadState": 0,
"EPresetData" :
[
{"PName" : "AccBass",
"PTags" : ["Bass", "Analogue"]
},
{"PName" : "ArtBass",
"PTags" : ["Bass","Analogue","Metalic","Guitar"]
}
],
"ESampleMapData" :
[
{"SName" : "Acoustic",
"STags" : ["Analogue","Smooth"]
},
{"SName" : "Attakus",
"STags" : ["Metalic","Grind"]
}
]
};
so to read this file (which is substrate_expansion.json) I just need to say:
const var myData = fileList[0].loadAsObject();
I admit I will nee dot ship this *_expansion.json file with each expansion, but I will be storing it in a pre-known folder (the AppData folder)
or am I missing something ?
