curtisullerich
commented
12 years ago Adding things to the app settings object is a decent idea, but in our case I think it would serve almost the same purpose as keeping a list in this issue. On Jul 24, 2012 10:23 AM, "Daniel Stiner" < reply@reply.github.com> wrote:
Either continue to add settings to the app settings object, or create a per-school file with a variety of settings that should never change for that school.
Quote from curtis: Agree about the per-school setting file, obviously for a later milestone. We could define a bunch of fields if we wanted with a simple file format and have a way to upload (or paste) a new settings file for parsing, maybe. Just a thought. there are a few things that would be obvious from school to school, but I kinda think it would be best to see what changes are necessary when/if we do port to another school, because we won't think of everything on the way.
Reply to this email directly or view it on GitHub: https://github.com/curtisullerich/attendance/issues/96
Edit: Tracking all required settings in this issue for now, decide what to do with them later.
Needed Settings:
Either continue to add settings to the app settings object, or create a per-school file with a variety of settings that should never change for that school.
Quote from curtis: Agree about the per-school setting file, obviously for a later milestone. We could define a bunch of fields if we wanted with a simple file format and have a way to upload (or paste) a new settings file for parsing, maybe. Just a thought. there are a few things that would be obvious from school to school, but I kinda think it would be best to see what changes are necessary when/if we do port to another school, because we won't think of everything on the way.