we could just save to and from csv or json files instead of using nedb.
also instead of using $rootScope.variables we should use dependency injection and then call some sort of method. perhaps we could model it after the settings.json:
variables.reload() or something.
and we can just use the index to refer to variables instead of their ids
on second thought... let's not do this because nedb handles disk writes very well (aka minimizing seeks). overwriting an entire json file does not scale.
we could just save to and from csv or json files instead of using nedb.
also instead of using $rootScope.variables we should use dependency injection and then call some sort of method. perhaps we could model it after the settings.json:
variables.reload()
or something.and we can just use the index to refer to variables instead of their ids