Support for basic API calls like `ACTION_OPEN_DOCUMENT`

[NastyFlytrap]

Is your feature request related to a problem? Please describe.

Im trying to use amaze with keepassDX but according to it, Amaze doesnt support certain functions and calls.

Describe the solution you'd like

For Amaze to support these calls so that i can use it with other applications that rely on those calls

Describe alternatives you've considered

Material files exists, i guess. Amaze is better.

Additional context

I tried asking the keepassDX devs for help and they told me to bug you about this: https://github.com/Kunzisoft/KeePassDX/issues/1626

[TranceLove]

Developer's note:

Support for OPEN_DOCUMENT is not hard - sounds like reusing the ringtone picker logic without saying ringtone stuff already worked. 957839b above already supports opening KeePassDX database files either on internal storage and SD card.

But for CREATE_DOCUMENT intent is another story.

• Easy answer is to construct a content://com.android.externalstorage.documents URI and let DocumentsUI do the rest. Since we expect end users' device must have DocumentsUI bundled (or else SD card access won't work at all) this shouldn't be difficult
• if not we'll expect Android will ask us for the OutputStream eventually (as the content:// URI will contain our package ID and we are expected to handle this), and we need to write the logic to construct the OutputStream

[NastyFlytrap]

Developer's note:

Support for OPEN_DOCUMENT is not hard - sounds like reusing the ringtone picker logic without saying ringtone stuff already worked. 957839b above already supports opening KeePassDX database files either on internal storage and SD card.

But for CREATE_DOCUMENT intent is another story.

* Easy answer is to construct a `content://com.android.externalstorage.documents` URI and let DocumentsUI do the rest. Since we expect end users' device must have DocumentsUI bundled (or else SD card access won't work at all) this shouldn't be difficult

* if not we'll expect Android will ask us for the `OutputStream` eventually (as the `content://` URI will contain our package ID and we are expected to handle this), and we need to write the logic to construct the `OutputStream`

I understand, but i dont have any clue how to write the code for that, im only familiar with basic C# and basic Python

[TranceLove]

@NastyFlytrap That's ok, will work on it at our side anyway 🙂

[NastyFlytrap]

@NastyFlytrap That's ok, will work on it at our side anyway 🙂

Thank you for your hard work