This project is mirrored from https://*****@github.com/iqb-berlin/verona-modules-aspect.git.
Pull mirroring updated .
- Mar 07, 2022
- Mar 03, 2022
- Mar 02, 2022
-
-
rhenck authored
- Units and element are now built via the factory. This ensures only the wanted properties are present. All others are discarded. - Since the sanatizer is supposed to check the unit defintion version it is used by player and editor and therefore put in common. This in turn makes it necessary to put the JSON resolver settings in the root-TSConfig file. - Renamed a couple of properties to have clearer names.
-
jojohoch authored
- Mar 01, 2022
- Feb 28, 2022
-
-
jojohoch authored
-
jojohoch authored
-
jojohoch authored
This was necessary after the surrounding element container with its styles and classes was deleted
-
jojohoch authored
-
jojohoch authored
-
jojohoch authored
-
jojohoch authored
Remove manipulations from elementModel - Refactor drop list component - Use of initial values for audio and video playback time Defining the validators not in the elements anymore, but when creating the forms
-
jojohoch authored
-
jojohoch authored
-
jojohoch authored
This helps to divide the code of the element container into smaller meaningful units. In addition, each element can be given its own form group.
-
- Feb 22, 2022
- Feb 21, 2022
-
-
jojohoch authored
-
- Feb 18, 2022
- Feb 17, 2022
-
-
jojohoch authored
Move required styles and classes to the overlays of player and editor
-
jojohoch authored
-
rhenck authored
This removes all the classes and goes back to simple interfaces for unit, pages etc and all elements. This makes creating them easier and cleaner. Things like specific needs when setting element properties and most importantly compatibility handling is done by a special service module, that knows all the elements and how to repair old their potentially outdated definitions.
-
- Feb 16, 2022
- Feb 14, 2022
- Feb 11, 2022
-
-
jojohoch authored
The previous solution, which uses a top position of 50%, did not work on iPad
-
- Feb 09, 2022
-
-
rhenck authored
This is done according to the Angular best practices and minimizes namespace collisions when using other packages which might use the same selectors. Technically the selectors are not even becessary since we use an Angular component factory to create element components but it is still useful for the DOM element naming, for debugging purposes for example.
-
- Feb 04, 2022