The server api now stores all it's data in a database instead of json files. It still serves the data to the client as json files, that hasn't changed. I now have all the client utilities in the root directory and the data (chips, configuration, opcodes info) are in a data directory to make it easier to manage. I also made it so that it only queries the server for updates if the files are missing, are manually requested, or an interval has passed, which defaults to weekly in the config.json file.
That's a very nice addition.
I've been sidetracked with a couple of contracts so I've been away from this project.
I had started to make a website to host the API for the vp-tools and instructions for reference and it should be online this weekend.
I'm also using it as a teaching tool since I need a front end junior coder at work for my ERP system and my 19 year old needs a job. I'll try to get it online this weekend but don't be judgy, since it's more functional than pretty! lol.
Since the tools aren't 100% operational yet I might need @nivbot I might need you to answer more questions once I make a deficiency list. When they are finally operational anyone will be able to download them, but until then I will be puting them behind a password for the beta-testers.
It's getting close. It's the first time I'll be putting something out that wasn't a work contract.
@rbourque Oh no worries man, I'm excited to see it but no rush. And I'm the same way. I don't like showing people my code because sometimes I am all over the place and only I know what some things mean. I will usually go back though and clean it up and add comments where appropriate but not always. You might find some local variable named "poop" or whatever, who knows.