Open Nelde95 opened 2 years ago
This is a big feature implementation, and should be done in its own branch.
Will definitely want to do this in indexeddb as well (see #3). Especially seeing as the config seams easier to store in nosql.
Need an intuitive way to define which database to use when it's not in a config file. Was considering using the name of the project folder, but I'm not sure how intuitive that is, and not quite sure how to get the folder name in html/javascript either.
Found a way to get the name of the parent folder, but still not sure how intuitive this is.
Perhaps the best approach is to eliminate the need of using multiple copies of the application altogether. I'm thinking maybe move to a system that tags videos and lets the user display videos based on tags.
To make the application it would be nice to get rid of the auth and config files in favor of a subpage that submits to another set of sql tables. Prefferably with an easy to use graphical user interface that displays logic operators in nested tabbed in html elements. Scripted dropdown menus that add and remove text fields as well as further dropdown menus seams like a good aproach at the moment.