This was totally supposed to be the calendar branch and I ended up writing that but also hacking on the database. Woops.
This was *all* just about calendars, honest
Moved here from 0ec15fbab3f1340fc0ecd277b764214c7bdcfc0c to keep my concerns straight.
There were some changes elsewhere in that commit but I think it was basically all just deleting tablenames on account of I was trying to make it irrelevant.
New notation for table definitions. Concise.
Hey, this is the file to run the thing. That should probably be here.
Redoing parms because dictify_row is just better. Now it's part of popdb seein' as that's all that used it anyway.

I've had occasion to use Journey.schedule(_) in popdb.py. Untested...
about to merge in the changes from the database branch
Merge branch 'database' into parms

Conflicts:
	item.py
	mkdb.py
i think i lost some work
i think it was something like this?
this works again at least
wrappers, and i don't know what happened to state.py, it just vanished or something
well recreated some progress from this morning at least
refixing
well, this
fix some bad data
This is really more a menu related commit than a calendar related commit. But I've established principles for making effectdecks to toggle UI elements, and I think those will come in handy for calendars shortly.
remove extant empty db before creating anew
importing db improvements from calendar branch
tabdict methods to make my work easier writing the savers