03-20-2014, 07:47 AM
I have added the API export to the APIDump plugin. It now creates a file, mcserver.lua, right next to the MCS executable; the file contains the basic API description for ZBS.
I'm not sure now what to do with it now. It's no use committing it to the main ZBS repo, as the API changes too often; also the file is some 220 KiB and everyone with MCS can generate it. However, the generator cannot place the file at the correct place, because there's no way for MCS to know if and where ZBS is installed. Maybe we could integrate it somehow with the ZBS-Plugin doing the MCS integration - it knows where MCS is (relative to the project) so it could process that file and perhaps apply it directly into ZBS after each debugging session. Paul, what do you think, is that reasonable? And is that doable?
I'm not sure now what to do with it now. It's no use committing it to the main ZBS repo, as the API changes too often; also the file is some 220 KiB and everyone with MCS can generate it. However, the generator cannot place the file at the correct place, because there's no way for MCS to know if and where ZBS is installed. Maybe we could integrate it somehow with the ZBS-Plugin doing the MCS integration - it knows where MCS is (relative to the project) so it could process that file and perhaps apply it directly into ZBS after each debugging session. Paul, what do you think, is that reasonable? And is that doable?