all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
-Set up a master corp id for adilas news and updates. This may also require a mapping to a template id or template list. This data should be recorded on the main top-secret application page. That is where all of the other universe settings are currently held. -Finish one project at a time. A fox that chases two rabbits catches neither. Sometimes that is hard advice to follow. -Maybe have the database store the configuration pieces vs. in-line hardcoded values. Make the configurations more dynamic. Instead of just holding settings… think clear out to the configuration level. Maybe even use JSON objects to hold those settings. That is a way to store pieces without forcing every little thing into a perfect database column or row. Store the whole configuration object. -On a different note, have the configuration files use defaults if params are not present. We could also use a dump to show a more visually interpreted display of the data. We could also use a basic hardcoded form to help people repopulate and create their configuration settings and files. -What if you had a configuration file – stored in the database as an object – for each main section. This could really be used to help with in-line custom code. The hardcoded human readable form could help users interpret the settings and results. -Your Data, Your World, Your Way! – New tag line for adilas. -Go get it! Game on! |