Add a public receiver for Tasker, Automate, etc.

[NatKarmios]

This is a recreation of my pull request for the original respository, orgzly/orgzly-android#878.

I'm a big fan of Automate, and I (along with many others, it seems) would love to be able to use it - or Tasker, etc. - with Orgzly.

In the spirit of being the change I want to see the world, I've got to work on implementing a publicly-accessible intent receiver to this end :)

Just a few issues relevant to this (most of which are more or less already implemented):

• Intent receivers for creating new notes within a notebook orgzly/orgzly-android#299
• Dynamic filters based on locations orgzly/orgzly-android#373
• In the receiver for the “share” intent, allow passing ID of the parent node in extra data (for sharing via Tasker and such apps) orgzly/orgzly-android#435

These "endpoints" (i.e. actions) have currently been implemented, and tested to be working on an emulated Pixel 4 (edit: and on my S21 Ultra, on which I have been daily driving these changes for the past 2 years 🙃):

• GET_BOOKS
• GET_SAVED_SEARCHES
• GET_NOTE
• ADD_NOTE
• EDIT_NOTE
• REFILE_NOTE / REFILE_NOTES
• MOVE_NOTE / MOVE_NOTES
• DELETE_NOTE / DELETE_NOTES
• ADD_SAVED_SEARCH
• EDIT_SAVED_SEARCH
• MOVE_SAVED_SEARCH
• DELETE_SAVED_SEARCH
• SEARCH (runs the same kind of query a saved search would use, and returns the result)
• GET_WIDETS
• SET_WIDGET (sets the saved search that a widget displays)

Where relevant, a note can be selected by:

• Its note ID from Orgzly's internal database - accessible via GET_BOOKS, SEARCH, etc.
• The "path" to the note
• An Orgzly search query; errors if the query yields more than one note (though perhaps this should be configurable)

[alensiljak]

Thank you for the contribution. While I do not currently use task automation, I find this to be a good addition. Intents can be sent from other apps or Termux.
This opens up some extensibility options.

[NatKarmios]

Perhaps it should be a separate issue, but this might be good time to fork the documentation repo alongside this one.

I'm more than happy to write up documentation on how to use this addition 🙂

[amberin]

Perhaps it should be a separate issue, but this might be good time to fork the documentation repo alongside this one.

I'm more than happy to write up documentation on how to use this addition 🙂

That sounds terrific!

I will look into creating a fork in this organization, and ping you when it's done.

[amberin]

@NatKarmios The forked documentation repo can be found here: https://github.com/orgzly-revived/documentation. I haven't touched anything yet -- feel free to open any kind of PRs.