4training / genmapper-angular Goto Github PK

Directly go to "Church Circles", we don't need any of the rest

Our goal is that people edit their generational map and then export and save it on their computer.

First for clarification: It seems like the genmapper is storing the work in the browser - what and how exactly?

Then let's explain that better to the user and probably introduce a warning when a user is about to leave the page without having exported his tree. (via event listener for beforeunload)

Currently let's not implement the login to avoid saving any sensitive data on the server. So this shouldn't be shown at all at the beginning (directly "continue without saving")

Currently the tool is already on 4training.net/genmapper. To complete this tasks, following are still missing:

• include genmapper in sidebar
• embeded tool so that navigation in website is not lost

suggested approach: https://www.mediawiki.org/wiki/Extension:Iframe

See https://www.trainingfuertrainer.de/baumzeichner/
This is a very common situation and we should be able to accurately map it.
Probably easiest implementation: Add a dummy root node that isn't shown - see implementation of the German BaumZeichner.

This dialog should have a box "don't show this again" which is ticked by default -> set a cookie so that next time this dialog won't be shown again.
Contents (roughly):

Welcome to the genmapper! You find an introduction to this [here].
Privacy is very important for us and we're not storing any of your data on our server. More specifically, this app is running solely in your browser and no information of it is sent anywhere else. Please export any church tree that you're creating and save it on your computer to make sure it doesn't get losted.
Additionally the data is stored in the local storage of your browser and you can continue when you come back. Caution: When you're deleting cookies / temporary data in your browser, this data gets deleted! Also you won't see your data when you use a different device.

Connect the genmapper texts to the mediawiki system with the translate plugin.
That means creating a mediawiki page with all the messages that need translation (to be decided upon: use a normal page with translation units or use interface messages?)

Then translators can go there and as with any other worksheet they can translate these messages into their language and the translation will be saved in the mediawiki system.

Now these message translations need to be imported and used by the genmapper. For this different approaches are possible:

1. Have the genmapper read directly messages from the mediawiki system

   • Advantage: Translations are immediately available in the genmapper
   • Disadvantage: No caching, slower because every time the relevant pages need to be read

2. Generate a javascript from the translations: on the server
   A script (can also be configured as a daily cronjob) checks for new translations and updates the javascript file with the messages: reads from the mediawiki system, writes into a javascript file on the server that is read by the genmapper

3. Generate a javascript from the translations: via this github repository
   A script (can also be configured as a daily cronjob) checks for new translations and updates the javascript file with the messages in this repository here: reads from the mediawiki system, commits to the repo and possibly via github actions deployment is automatically building everything again and writing it to the server

For performance (and also security) reasons I'd suggest on of the two latter options. The script could be implemented in python as we already have some python scripts. I don't know how much work the third solution would mean, would be an interesting one - when we have automatic deployment working maybe that would be a good choice?