From 6a8ee53425b4b30c72671d7735d7b2530f2f3639 Mon Sep 17 00:00:00 2001 From: James Miller Date: Tue, 12 Nov 2019 00:10:00 -0600 Subject: [PATCH] update README --- README.md | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 171cf98..a12cde4 100644 --- a/README.md +++ b/README.md @@ -14,19 +14,15 @@ Also, most use cases of this data will likely be read only, so the sqlite limitations on concurrent writes won't be an issue either. Finally, it's permissively licensed. -## Why not JSON? - -Because I'd rather leverage sql's power, than writing internal code to a future -Pathfinder 2 app. Also, because sqlite is pretty much language agnostic at this -point; Pythonistas, Gophers, Rustaceans, and anything in between can access a -sqlite database. - ## Roadmap -1. Design schema; -2. Write script to generate sqlite database from sql code; -3. Write sql code; and -4. Drinks for all when finished! +1. Get data in YAML format (spells are in JSON for the time being; but will + get converted over to YAML in the future). +2. Design schema; +3. Write script to generate sqlite database from YAML data (see + `data/yaml/gendb.py` for work in progress); +4. Metric boatloads of proofreading +5. Drinks for all when finished! # Conventions in the Code