Adds a repository to remove the logic in the motion domain object
The repository will add a new model layer between the components
and the domain objects
implicitly add a new buttion into the motion detail view
Save those values in a new service, that will also watch for changes in
config variables. UI is not good; this can be done later
Share legal notice and privacy policy
Created some containers for them
- core modules contains core services
- shared module contains "dumb" components (directives, models)
- used by nearly all modules
- site, it's children and projector are now feature modules
- full lazy loading with independent routing
- routing for children (extremely helpful for plugins (later))
- models get other models from DataStore (Relations)
- documentation using Compodoc
- rename and restructure
- http-interceptor makes all http-objections obsolete
- created 'Deserializable model' interface for better mapping of JSON objects
- Supports multiple nested objects
- No foreign dependancies, no magic
- Simple yet efficient deserialize function
- arrays of nested objects
- created more classes for better OOP AOP
-overworked login and logout
-new directive 'appOsPerms'
(former os-perms)
-appOsPerms compares with groups in Operator
-login observes operator for user-information
(also serves as example on how to user observables and subjects)
-operator observes datastore for groups
(so the operators knows it's groups by creation or directly after an
autoupdate)
- Basic construction and datatypes of all objects
- create objects out of websocket response
- autoupdate service
- re-structure core models
- DataStore is easier to use
- Since MaterialUI does not have an equivalent to bootstrap alterts,
the toast service and alert service are marked as deprecated for now.
The functionality has been replaced with the snackbar.
