Porting some features from my old fork

[micw]

Hello Freifunk Community,

I'm glad to see that Meshviewer found a new home. Back in 2022 It looked quite abandoned, so I created a fork for our own community and added a bunch of features. With a new official home, I'd prefer to share my work and have everything upstream. Some have already been implemented independently, other features not. So let me know if you are interested in the following features:

1. Alphanumeric node-ids
   We used this for older parts of our network. Not sure if it's still relevant but the code change is simple and has no side effects

2. More tolerant json parsing. Allow missing attributes, ignore invalid routes

3. Extended IFrame embedding.
   IFrame and Meshviewer exchange via "post message". Meshviewer navigation is exposed to the IFrame's URL and vice versa. Allows Deep links to an embedded Meshviewer. Example: https://freifunk-leipzig.de/map/#!/de/map/1468

Best regards,
Michael.

[maurerle]

Hi @micw - sounds good! I also did take a look at different forks at some point and tried to integrate features. But I forgot smaller ones.

For 1. and 2. I wonder if this is still needed..? But I am very open to merge such improvements.
3. also sounds very nice if it does not add too much complexity!

If you could open a PR or just point to the relevant commits of your fork, that would be really good!
Thanks for reaching out and contributing back :)

[micw]

Hello,

I'm starting with #361 to get a shared set of test data so than I (and you) can verify my features. I will also think about how we can unit-test my changes.

1. is indeed needed, see https://karte.freifunk-leipzig.de. we have numeric node IDs.
2. is good because the map will not break if a link is broken
3. can be easy on the map's side - it just needs to fire cross-frame events on route changes

[maurerle]

@micw anything left to do here? :)

[micw]

No, all our custom features are now either ported or have already been implemented.