Mercurial > gemma
view client/docs/developers.md @ 4962:1b309a8e7673 fairway-marks-import
Distinguish more clearly between BCNLAT HYDRO and IENC features
This allows importing them from different sources while keeping
the history of data intact. Additionally, storing them in different
tables also allows to have different attributes (here only
dirimp via an m:n-table) and different constraints (currently
not implemented) according to the IENC feature catalogue.
Since both new tables inherit from a table with the same name as the old
table, all entries still can be accessed via a table of the same name.
Thus, no changes to GeoServer layers are necessary.
ToDo: solve layout problems in the client SPA.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Thu, 27 Feb 2020 21:05:09 +0100 |
parents | d6439e7c8b1c |
children |
line wrap: on
line source
When developing wamos, check out * [How translations are handled](dev-translations.md) * [Rationale of some choices](dev-generalconsiderations.md) ## Hints ### svg2pdf https://github.com/yWorks/svg2pdf.js has known shortcomings, which we work around. Not all layout possibilities of webbrowser are not supported! Our tactics is to report the problems, but work around them, if we can, some examples: * https://github.com/yWorks/svg2pdf.js/issues/82 (Unsupported features/Known issues) * https://github.com/yWorks/svg2pdf.js/issues/109 (alignment-baseline attribute does not work) * https://github.com/yWorks/svg2pdf.js/issues/100 (Font-size in `em` unit does not work) ### Testing diagram layout and pdf export When testing the vuex store object can be accessed from the webbrowsers console like ```javascript store = document.getElementsByTagName('a')[0].__vue__.$store ``` This allows for setting test values where getting real test data is complicated. For example testing the diagramm for the fairwayavailability (tested with Chromium 73 und gemma-2019-09-04): ```javascript data = store.state.fairwayavailability.csv // see current data data=`#time,# < LDC (164.0) [d],# >= LDC (164.0) [d],# < 230.0 [d],# >= 230.0 [d],# >= 250.0 [d] 01-2019, 0,31, 0, 0,31 02-2019,14,14, 6, 8,14 03-2019, 1,30, 3, 2, 2 04-2019, 5,25, 1, 1,28 05-2019, 6,25, 3, 2, 3 06-2019, 0, 0, 0, 0, 0 07-2019, 0,16, 0, 0, 0 08-2019, 0, 0,31, 0, 0 09-2019, 0, 9, 0, 3, 9 ` store.commit("fairwayavailability/setAvailableFairwayDepthData", data) ``` Or for the AvailableFairwayDepthLNWLDiagram: ```javascript data = store.state.fairwayavailability.csv // see current data data=`#time,# < LDC (162.0) [h],# >= LDC (162.0) [h],#d < 230.0 [%],#d >= 230.0 [%],#d >= 250.0 [%] 09-2018,100, 0,100 , 0, 0 10-2018,100, 0, 80 , 20, 0 11-2018,100, 0, 0 , 100, 0 12-2018, 80, 20, 50 , 50, 0 01-2019, 70, 30, 15 , 60, 25 02-2019, 65, 35, 40 , 40, 20 03-2019, 55, 45, 42 , 42, 16 04-2019, 42, 58, 40 , 20 , 40 05-2019, 30, 70, 2 , 30 , 68 06-2019, 30, 70, 0 , 25 , 75 07-2019, 20, 80, 25 , 0 , 75 08-2019, 0,100, 10.1, 1.5, 88.4 09-2019, 0,100, 23.5, 2.4, 74.1 ` store.commit("fairwayavailability/setAvailableFairwayDepthLNWLData", data) ``` (Depends on the code structure in store/fairwayavailability.js.)