-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "publicly-accessible" receiver #878
base: master
Are you sure you want to change the base?
Conversation
8917bfc
to
63442e1
Compare
I've pushed a bunch more actions; see the edited main post |
There isn't already a search Intent using
Anyway, thank you for all the effort! |
Thanks for getting back to me! R.E. queries, this is a different kind of query; the |
Great work, @NatKarmios! I was about to start working on this myself (I desperately need to integrate Orgzly with Tasker), so I'm grateful to see the work has already been done! Is there any way to help to fast-track merging in these changes? This is the missing bit to make Orgzly a fully-featured Emacs companion for org-based productivity systems, allowing users to customize the workflow to individual needs, without burdening Orgzly itself with supporting a zillion switches and integrations. |
- Move Intent parsing to separate file - Support finding note by query (instead of selecting by ID or path) - Give properties in note info
479e6d4
to
a5d3b96
Compare
Just to bump this (@nevenz), I've rebased on master and spruced it up a little more. |
Hey, I would like to try this out (I've compiled the app from your branch) but I don't know how is supposed to work For example, in this editNote function, I see there is a note id and a note content but I don't know what's that |
It's an internal ID used by Orgzly, useful if you're editing a note based on a previous query. If you take a look at
|
For anyone still holding their breath for these changes, I've just popped a PR for it on the |
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):
These "endpoints" (i.e. actions) have currently been implemented, and tested to be working on an emulated Pixel 4:
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)Any instance where a note or multiple notes are selected, both note IDs and book/path combos are supported.
P.S.: Might I compliment you on your implementation of the
DataRepository
- developing this was a breeze because of it!