Puppeteer
Emperor
After thinking about and researching APIs and RESTful APIs I think I see how this app will look from where it nearly is now and into the future as features get added:
In: Civ3 save game file(s)
Out: REST API of various info from the game
Then the UI(s) is (are) fungible.
So for now I have threebits of information for each file:
And as I am able to extract more info from the file I can add a new return value in the API. And when I learn to associate related sav files by same-map and/or same-game I can have /game/<id> and /map/<id> API trees.
One of the best parts about this architecture for today is that I can make it work now with static files and folders and refactor the back end without affecting the front end as I modify how the game data is parsed and stored.
Another random thought: since the SVGs are sourced from the same API, I can now allow themable maps by requesting a different tile definition SVG file.
In: Civ3 save game file(s)
Out: REST API of various info from the game
Then the UI(s) is (are) fungible.
So for now I have threebits of information for each file:
- Save game file itself: /sav/<id>/savefile
- Original filename: /sav/<id>/savefilename
- svg map: /sav/<id>/map/svg
And as I am able to extract more info from the file I can add a new return value in the API. And when I learn to associate related sav files by same-map and/or same-game I can have /game/<id> and /map/<id> API trees.
One of the best parts about this architecture for today is that I can make it work now with static files and folders and refactor the back end without affecting the front end as I modify how the game data is parsed and stored.
Another random thought: since the SVGs are sourced from the same API, I can now allow themable maps by requesting a different tile definition SVG file.