TIDO merge requestshttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests2021-06-16T14:14:32Zhttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/183Annotation list has to be scrollable2021-06-16T14:14:32Zschneider210Annotation list has to be scrollable# Bug fix
## Summary
Apart from what is mentioned in the main ticket you are going to close with this
MR, tell us what you have done to achieve this goal.
- use the same styles (classes **item** and **item-content**) used in all the o...# Bug fix
## Summary
Apart from what is mentioned in the main ticket you are going to close with this
MR, tell us what you have done to achieve this goal.
- use the same styles (classes **item** and **item-content**) used in all the other panels
- reintroduce styles for the annotations that got lost during prior merge
## How to test
**entrypoint => https://ahikar-dev.sub.uni-goettingen.de/api/textapi/ahikar/syriac/collection.json**
select manuscript **Brit. Libr. Or. 2313 / Sheet 173v** and scroll the list
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functional tests passed
* [ ] Non-Functional requirements met
* [x] Product Owner accepts the User Story
### Related
#283
### Closes
Closes #283
## Changelog
* [ ] I added a statement to the CHANGELOG.
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Mathias Goebelschneider210Mathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/180Annotation list has to be scrollable2021-06-14T10:45:12Zschneider210Annotation list has to be scrollable# Bug fix
## Summary
Apart from what is mentioned in the main ticket you are going to close with this
MR, tell us what you have done to achieve this goal.
- use the same styles (classes **item** and **item-content**) used in all the o...# Bug fix
## Summary
Apart from what is mentioned in the main ticket you are going to close with this
MR, tell us what you have done to achieve this goal.
- use the same styles (classes **item** and **item-content**) used in all the other panels
- reintroduce styles for the annotations that got lost during prior merge
## How to test
**entrypoint => https://ahikar-dev.sub.uni-goettingen.de/api/textapi/ahikar/syriac/collection.json**
select manuscript **Brit. Libr. Or. 2313 / Sheet 173v** and scroll the list
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functional tests passed
* [ ] Non-Functional requirements met
* [ ] Product Owner accepts the User Story
### Related
#283
### Closes
Closes #283
## Changelog
* [ ] I added a statement to the CHANGELOG.
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/128bugfix/#118 - Contents in Panels not fully visible2021-04-07T08:45:26Zdindigalabugfix/#118 - Contents in Panels not fully visible# Bug fix
## Summary
Apart from what is mentioned in the main ticket you are going to close with this
MR, tell us what you have done to achieve this goal.
- Panels heights are adjusted according to the screen sizes.
- Contents in Pan...# Bug fix
## Summary
Apart from what is mentioned in the main ticket you are going to close with this
MR, tell us what you have done to achieve this goal.
- Panels heights are adjusted according to the screen sizes.
- Contents in Panels are fully visible.
Entrypoint: https://ahikar-dev.sub.uni-goettingen.de/api/textapi/ahikar/arabic-karshuni/collection.json
Things to do: Make panels responsive work again.
Team: Agreed to open a new ticket related to make panels responsive.
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [x] Code reviewed
* [x] Acceptance criteria met
* [ ] Functional tests passed
* [ ] Non-Functional requirements met
* [x] Product Owner accepts the User Story
### Related
### Closes
## Changelog
* [ ] I added a statement to the CHANGELOG.
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)dindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/192Bugfix/roll back node2021-06-24T09:38:42ZMichelle WeidlingBugfix/roll back node# Bug fix
## Summary
With this MR, we no longer use the latest version of node for our Docker image but `node:12-slim` which doesn't have any problems with libsass.
## Does the result of the MR comply to our "definition of done"?
* [...# Bug fix
## Summary
With this MR, we no longer use the latest version of node for our Docker image but `node:12-slim` which doesn't have any problems with libsass.
## Does the result of the MR comply to our "definition of done"?
* [x] Unit tests passed
* [x] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functional tests passed
* [ ] Non-Functional requirements met
* [x] Product Owner accepts the User Story
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/179Draft: Resolve "Annotation list has to be scrollable"2021-06-09T12:30:49Zschneider210Draft: Resolve "Annotation list has to be scrollable"Closes #283Closes #283schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/175Draft: Resolve "Floating Action Button: Behavior when switching pages"2021-06-07T09:05:50ZMathias GoebelDraft: Resolve "Floating Action Button: Behavior when switching pages"Closes #275Closes #275Mathias GoebelMathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/120fix: provide an empty statics folder2021-03-10T13:17:30Zschneider210fix: provide an empty statics folder# Bug fix
## Summary
Apart from what is mentioned in the main ticket you are going to close with this
MR, tell us what you have done to achieve this goal.
The statics folder has been deleted in the last merge. It was holding a single ...# Bug fix
## Summary
Apart from what is mentioned in the main ticket you are going to close with this
MR, tell us what you have done to achieve this goal.
The statics folder has been deleted in the last merge. It was holding a single file *support.css* which proved to be obsolete.
But the folder is supposed to act as a kind of container for the css resource in ahiqar-tido to be copied to
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functional tests passed
* [] Non-Functional requirements met
* [x] Product Owner accepts the User Story
### Related
### Closes
## Changelog
* [ ] I added a statement to the CHANGELOG.
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/131WIP: feat: change the fontsize consistently by percentage2021-06-18T10:38:25Zschneider210WIP: feat: change the fontsize consistently by percentage# Feature
## Summary
This MR provides the consistent de- and increase of the fontsize in the text panel.
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance cr...# Feature
## Summary
This MR provides the consistent de- and increase of the fontsize in the text panel.
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functional tests passed
* [ ] Non-Functional requirements met
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [x] I provided my functions with appropriate documentation
* [ ] I adjusted other parts of the documentation (if applicable)
## Tests
Are we able to test this new feature?
* [ ] Yes, everything can be done via unit tests.
* [x] Yes, you can test by following these steps:
- checkout the branch: `git checkout feature/#178-change-fontsize-consistently`
- open the **index.template.html** file:
- set an entrypoint: **https://ahikar-dev.sub.uni-goettingen.de/api/textapi/ahikar/syriac/collection.json**
- start your dev environemnt: `npm run dev`
- navigate to: **St. Petersburg Sado no. 9** => **Sheet 1**
- click the buttons at the top of the text panel to watch the fontsize in/decrease by 10% per click (default: 100%, min: 90%, max: 150%)
* [ ] No, it is not possible.
## Changelog
* [ ] I added a statement to the CHANGELOG.
## Related Tickets
Add all related issues and especially those to be closed.
### Related
### Closes
closes
#178
## Logs and Screenshots
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)schneider210schneider210