Question about modernizing the frontend scripts

[lanseg]

I was working on the LV95/EPSG:2056 for the DXF exporter and noticed that npm is used only to fetch the dependencies. Because of that some of the nice features are missing, for example it's hard to use typescript-based packages that require compilation, likedxf-writer. Did you think about modernizing the scripting part to get all the nice stuff like easier upgrades, unit tests for the js part, no need to hardcode DXF file, etc?

I started experiments in this area and wanted to know if that change was planned or not.

[yblatti]

Hi @lanseg !

This would be great, but for the last few years we had no major changes in the front-end that would require a switch to a JS Bundlers (webpack or other).

Any PR in this direction would be welcome !

You mention the LV95/EPSG:2056 for the DXF exporter. Is this the DXF button on the map ?

Are you working on replacing the old-fashioned hard-coded export ?

(PS: did you notice that it exports the DXF in the SRS of the map, so if the map is defined in LV95/EPSG:2056, the DXF export will also be LV95/EPSG:2056)

[lanseg]

I wrote a quicker and dirtier fix in our fork: camptocamp#15, it also includes a screenshot of a potential exporting dialog: same popup that shows rule writing hints.
Thanks for note about the map projection. I used the default one (EPSG:3857/WGS84) projection as extract's default and it worked

[yblatti]

I wrote a quicker and dirtier fix in our fork: camptocamp#15, it also includes a screenshot of a potential exporting dialog: same popup that shows rule writing hints.

Thanks for the feedback, I'll have a look :)

Thanks for note about the map projection. I used the default one (EPSG:3857/WGS84) projection as extract's default and it worked

You might still be interested in configuring your map for EPSG:2056, as this would allow you to use Swiss backgrounds (swisstopo etc), add your custom layers (WMTS, WMS, etc...). Doc is here : https://asit-asso.github.io/extract/getting-started/customize/#basemap