TIDO merge requestshttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests2021-05-11T10:46:45Zhttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/154style: save space with tabs in contents and metadata2021-05-11T10:46:45ZNils Windischstyle: save space with tabs in contents and metadata# Feature
## Summary
the tabs at contents and metadata take up less space vertically compared to develop.
## Tests
Are we able to test this new feature?
* [x] Yes, you can test by following these steps: …
do the tabs at contents an...# Feature
## Summary
the tabs at contents and metadata take up less space vertically compared to develop.
## Tests
Are we able to test this new feature?
* [x] Yes, you can test by following these steps: …
do the tabs at contents and metadata take up less space vertically compared to develop?
## Related Tickets
#215Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/105WIP: Feature/#65 multilingualism2021-05-19T14:51:22Zschneider210WIP: Feature/#65 multilingualism# Feature
## Summary
This MR provides:
- implementation of multiligualism: easily switch between English and German
- panel headers can be turned off (according to Johannes' proposal)
## Does the result of the MR comply to our "defini...# Feature
## Summary
This MR provides:
- implementation of multiligualism: easily switch between English and German
- panel headers can be turned off (according to Johannes' proposal)
## 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)
* [ ] 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:
- click the language icon in the lower left (footer) and just switch the languages
- to switch off the panel headings, set headers.panels to *false* (index.template.html)
* [ ] No, it is not possible.
## Changelog
* [ ] I added a statement to the CHANGELOG.
No, since it will be done automatically.
## Related Tickets
Add all related issues and especially those to be closed.
### Related
### Closes
[Issue #65](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/issues/65)
## 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)Ahikar Version 0.13.0schneider210dindigalaschneider210https://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/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/184Remove unnecessary config from root dir2021-06-14T12:45:19Zschneider210Remove unnecessary config from root dir- create new folder **.build-scripts** and move **tweak_build.sh** into it
- adjust runner cmd in **package.json** => **npm run tweak:build**- create new folder **.build-scripts** and move **tweak_build.sh** into it
- adjust runner cmd in **package.json** => **npm run tweak:build**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)schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/229fix: dark mode contrast issues2021-10-08T08:37:32ZNils Windischfix: dark mode contrast issuesaffects the annotations panel only
Test it:
* switch your OS to dark mode
* see the floating action button adapt the right colors
* see the list of annotation adapt correct contrasted colors
Please note:
Text in the panel still looks o...affects the annotations panel only
Test it:
* switch your OS to dark mode
* see the floating action button adapt the right colors
* see the list of annotation adapt correct contrasted colors
Please note:
Text in the panel still looks off. This MR is not concerned with that, it's an issue with the support CSS.Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/227make TIDO responsive again2021-10-07T08:39:02ZNils Windischmake TIDO responsive againrelated ticket #342
Test it:
* reduce the width of the viewport to <599px and watch the panels get stacked vertically
* reduce the width of the viewport to <599px and watch the header to get rearrangedrelated ticket #342
Test it:
* reduce the width of the viewport to <599px and watch the panels get stacked vertically
* reduce the width of the viewport to <599px and watch the header to get rearrangedNils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/217make the theme switch configurable2021-08-31T09:52:50Zschneider210make the theme switch configurable# Feature
## Summary
This MR provides the option to configure the "theme switch / color palette" (whether to show it) and deletes the unicorn theme.
Since the unicorn stuff has been deleted, there are only two remaining "color themes"...# Feature
## Summary
This MR provides the option to configure the "theme switch / color palette" (whether to show it) and deletes the unicorn theme.
Since the unicorn stuff has been deleted, there are only two remaining "color themes": the **default** one configured in **quasar.conf.js** and - if a project decides to do so - the **projectcolors** configured in the **index.template.html** file.
If these projectcolors aren't set, it doesn't make sense at all to show the palette, since it would include the default theme only.
hence: in order to show the palette, a project has to
- a) set the **themes** switch to `true` **AND**
- b) configure their respective colors
## 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)
* [ ] 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/#327-make-the-theme-switch-configurable`
- run your local env: `npm run dev`
## 1
- edit the **index.template.html** file:
- set **themes** to `true`
- configure some arbitrary colors: e.g.
```
"colors": {
"primary": "#E7E7E7",
"secondary": "#F9F711",
"accent": "#00CAD9"
}
```
**expected**: color palette shows up and you can switch between the two themes
## 2
- omit one of the two config steps described above, e.g.: stick to `themes: true` and delete the colors you set in the recent step
**expected**: color palette doesn't show up
## 3
- give it a try the other way around: set `themes: false` and reenter the colors you configured in step 1
**expected**: color palette doesn't show up
* [ ] 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
#327
## 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)schneider210dindigalaschneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/215feat: implement config option for the language switch2021-08-26T10:05:35Zschneider210feat: implement config option for the language switch# Feature
## Summary
This MR provides the config option for the language toggle.
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functio...# Feature
## Summary
This MR provides the config option for the language toggle.
## 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
* [x] I updated the README (if applicable)
* [ ] 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 issue/make-language-switch-configurable` and start your local env
- open **index.template.html** and set `language-switch` to `false`
=> **expected**: the switch doesn't show up
* [ ] 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
## 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)schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/212ahiqar-code-in-generic-tido2021-08-19T11:14:43Zschneider210ahiqar-code-in-generic-tido# Feature
## Summary
This MR provides the deletion of project specific code.
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functional ...# Feature
## Summary
This MR provides the deletion of project specific code.
## 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
## Documentation
* [ ] I updated the README (if applicable)
* [ ] 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:
**note:** testing is limited, since the nested motifs aren't merged yet and the icon reproduction is still in place.
- **open** the appropriate **[environment](https://subugoe.pages.gwdg.de/emo/tido/issue--325-ahiqar-code-in-generic-tido/#/)** and **watch** the collection **title** still to be displayed
- **click** the **language toggle** to translate TiDO to German
- expected: the collection title isn't translated anymore
* [ ] 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
#325
## 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)schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/204refactor: probit users selecting text in tree view2021-07-30T10:56:13ZNils Windischrefactor: probit users selecting text in tree viewtest it by trying to select the text of links (items) in the tree view. It shouldn't be possible anymore.
closes #320test it by trying to select the text of links (items) in the tree view. It shouldn't be possible anymore.
closes #320Ahikar Version 0.16.0Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/201feat: provide one more zoom lvl in text panel2021-07-22T11:29:59ZNils Windischfeat: provide one more zoom lvl in text panelzoom to the max using the buttons in the text panel and see, that the font size is now 28px (instead of only 24px before).
closes #316zoom to the max using the buttons in the text panel and see, that the font size is now 28px (instead of only 24px before).
closes #316Nils WindischNils Windischhttps://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/188text-size-optimization2021-06-18T15:45:15Zschneider210text-size-optimization# Feature
## Summary
This MR provides:
the resizing of the text / content in the text panel by button click (+ / -) taking size limits into account
the default fontsize is set to **1em** which corresponds to **16px**.
either click o...# Feature
## Summary
This MR provides:
the resizing of the text / content in the text panel by button click (+ / -) taking size limits into account
the default fontsize is set to **1em** which corresponds to **16px**.
either click on a button in- or rather decreases the fontsize by **0.125em** which corresponds to **2px** per click.
the minimum is set to **0.875em (14px)** and the maximum to **1.5em (24px)**
## 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)
* [ ] 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:
as usual:
- checkout the branch: `git checkout feature/#287-merge-text-size-optimization`
- start your dev env: `npm run dev`
- switch to your browser and point it to **localhost:8080**
- select an arbitrary item of your liking and click on a button at the top of the text panel to in-/decrease the text(-size) therein only
* [ ] 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
#287
### Closes
closes #287
## 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)schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/186move-misc-icons2021-06-21T08:38:08Zschneider210move-misc-icons- refactor **header.vue**
- create new component **@components/tools.vue**
- aggregate **color.vue, language.vue and softwareinfo.vue**
- rename config option **headers** to **header_section** according to @nwindis proposal
- rename...- refactor **header.vue**
- create new component **@components/tools.vue**
- aggregate **color.vue, language.vue and softwareinfo.vue**
- rename config option **headers** to **header_section** according to @nwindis proposal
- rename **headers.all** to **header_section.show**schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/185Remove unnecessary config from root dir2021-06-18T07:55:34Zschneider210Remove unnecessary config from root dir- create new folder **.build-scripts** and move **tweak_build.sh** into it
- adjust runner cmd in **package.json** => **npm run tweak:build**
**How to test (on your local)**
- checkout the branch
- `npm run build` (creates a dist folde...- create new folder **.build-scripts** and move **tweak_build.sh** into it
- adjust runner cmd in **package.json** => **npm run tweak:build**
**How to test (on your local)**
- checkout the branch
- `npm run build` (creates a dist folder in the root dir)
- `npm run tweak:build` (patches the quasar build step)
- take a look at the **dist** folder in the root dir; it should now consist of 2 files: **tido.js** and **index.html**
**note**: the **tweak_build**-script is also called **during ci**, so the only possibility to test it before the merge is done, would / could be to make a **dummy commit** and push it.
thereafter you can take a look at the pipeline (gitlab) and watch the job succeed.
=> please revert your changes (dummy commit)schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/182Feature/#284 ci add docs2021-06-17T09:43:19ZMichelle WeidlingFeature/#284 ci add docs# Feature
## Summary
This MR provides a more extensive documentation of all things CI.
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] F...# Feature
## Summary
This MR provides a more extensive documentation of all things CI.
## 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
* [x] I adjusted other parts of the documentation (if applicable)
## Tests
* [x] No, it is not possible.
## Closes
Closes #284
/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/172project header2021-07-07T12:29:43ZNils Windischproject headerThis MR is realated to this epic: https://gitlab.gwdg.de/groups/subugoe/emo/-/epics/8This MR is realated to this epic: https://gitlab.gwdg.de/groups/subugoe/emo/-/epics/8https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/171style: improve icon spacing of annotations in text panel2021-06-04T07:55:48ZNils Windischstyle: improve icon spacing of annotations in text panelBefore:
![Screenshot_2021-06-04_at_09.01.26](/uploads/1bdf25055a1d62be76e316def54b2429/Screenshot_2021-06-04_at_09.01.26.jpg)
After:
![Screenshot_2021-06-04_at_09.01.00](/uploads/b58752d66481c738d4a2ed087c596b44/Screenshot_2021-06-04_...Before:
![Screenshot_2021-06-04_at_09.01.26](/uploads/1bdf25055a1d62be76e316def54b2429/Screenshot_2021-06-04_at_09.01.26.jpg)
After:
![Screenshot_2021-06-04_at_09.01.00](/uploads/b58752d66481c738d4a2ed087c596b44/Screenshot_2021-06-04_at_09.01.00.jpg)
…works for ltr and rtl text.Nils WindischNils Windisch