You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm in the process of writing a tool which produces an Android Manifest (mostly) based on an appstream upstream metadata component. On android you have to explicitly specify an action for which mimetypes should be handled. I specifically want to differentiate between applications that only have the ability to "view" a file of a specific mimetype and applications that can also "edit" those.
Functionality like this is also not limited to Android, as for example GLib/GIO has a hint parameter in its Gio.Application.open which might allow an application to determine what it is supposed to do.
The text was updated successfully, but these errors were encountered:
sp1ritCS
added a commit
to sp1ritCS/gtk-android-builder
that referenced
this issue
Dec 26, 2024
By adding actions="view|edit" to mime/mediatype pixiewood will also add
the EDIT action to the intent handler for that particular mimetype.
This is not specified in the appstream metadata format, but appstreamcli
doesn't check for parameters so it works for now.
I hope to have that behviour codified in appstream at some point.
See ximion/appstream#689
I'm in the process of writing a tool which produces an Android Manifest (mostly) based on an appstream upstream metadata component. On android you have to explicitly specify an action for which mimetypes should be handled. I specifically want to differentiate between applications that only have the ability to "view" a file of a specific mimetype and applications that can also "edit" those.
Functionality like this is also not limited to Android, as for example GLib/GIO has a
hint
parameter in its Gio.Application.open which might allow an application to determine what it is supposed to do.The text was updated successfully, but these errors were encountered: