Mediatype handlers

[makew0rld]

Currently there is support for using different applications per URL scheme, see the [url-handlers] section of the config. Another section should be made to support defining a list of mediatypes that the specified application would handle. Currently the only option for binary files (images, audio, etc) is to download it or open it in the portal. Adding this would allow more seamless browsing.

The download modal buttons should change to "Open" and "Download". The "Open in Portal" button has always been a bit of a hack.

Example config, using an array of tables

# Explanation here...

[[mediatype-handlers]]
cmd = ["feh"]
types = ["image/jpeg"]


[[mediatype-handlers]]
cmd = ["vlc", "--flag"]
types = ["audio", "video"] # Can capture an entire type by just not specifying the subtype

[[mediatype-handlers]]
cmd = ["some-command"]
types = [
	"application/pdf",
	"*", # Override the default catch-all handler
]

• Put this on the roadmap (also talk about scheme handlers in the same bullet maybe)
• Add way to specify piping/streaming content versus downloading the entire thing first

[makew0rld]

On Unix systems default to using xdg-open for files if no other handler is found. Display an error to the user if there are no handlers and xdg-open does not exist.

For Windows and macOS do the same, but use the commands used for each OS in webbrowser/ instead.

For other OSes just raise the error if there's no handlers.

The user can override this default catch-all handler with the types = ["*"] line as described in the original comment.

[makew0rld]

The download modal would still display until the file is entirely downloaded and the application is launched -- except for piped/streamed mediatypes.

[makew0rld]

The [url-handlers] section of the config has this in it:

# This is a special key that defines the handler for all URL schemes for which
# no handler is defined.
other = 'off'

Maybe when this feature is added, then that key can be removed and ignored. And instead of displaying an error when the user tries to open an unknown scheme, Amfora will fallback to the default opening command for the user's OS, as mentioned above.

If the above happens, there should be a modal that shows up if the user has not explicitly specified a handler, saying "Do you want to try to open a <scheme> URL in your default application?". And of course, an error modal should appear if anything goes wrong, whether the handler was explicit or not.

Edit: I'm going to leave this unchanged for now.

[makew0rld]

This feature has been added in #134 thanks to @sudobash1, in mediatype-handlers branch. Once the streaming part is added on that branch and v1.7.0 is released, then that branch can be merged to master and this issue can be closed.

The CHANGELOG.md file will need to be updated before merging.