Share Dialog with QR Code

[mjaschen]

This pull-request implements sharing a route by QRCode, external services or by using the clipboard

• add a new button "Share" to the main navigation
• when clicked, a new modal dialog opens and shows share options for the planned route, which are currently:
  • a button to copy the URL of the current route to the clipboard
  • share buttons for 3rd party services, such as Facebook, Whatsapp, Email (and Mastodon, but currently disabled via config[^1])
  • a QRCode
• the QRCode is a representation of the current route (i.e. the current URL) with an added query parameter to the URL: ?export=dialog
• when BRouter-Web is loaded with the export=dialog query parameter, the export dialog is shown instantly (as discussed in #370)
  • using a query parameter (export) and a value (dialog) instead of only a paramater is required, because URLSearchParams needs both when adding a new parameter
  • we've the opportunity to add further options in the future (download, gpx etc.)
• add a new keyboard shortcut 'A' (“action”) which opens the share dialog (would have used 'S', but that's already taken)
• add 3rd-party QRCode library
• add URLSearchParams polyfill for ancient browsers as Husky didn't allow me to commit otherwise …
• add license information to README
• TODO: Translations

[^1]: Mastodon instances respond with HTTP 502 when the submitted text (= the route URL in our case) is longer than the maximum post character limit on that instance. That will probably confuse users. I decided to keep the code here as this bug will probably be fixed in the future.

[mjaschen]

• I've added a check so that the button is enabled only if at least 2 route points are set.
• URLSearchParams polyfill was removed.
• the share icon in the navbar was changed to a nicer one.

[nrenner]

I've added a check so that the button is enabled only if at least 2 route points are set.

No strong opinions, we can merge as is, but there might be use cases where it makes sense to only share the current map view or a single route point. Therefore I meant to still allow sharing, just not to open the export dialog at the receiving end by adding that check to index.js.

Don't know if my comment was misleading or if you prefer to disable the share dialog instead?

[mjaschen]

Just a misunderstanding – you're absolutely right. I'll push an update later.

[nrenner]

Thanks!