-
Notifications
You must be signed in to change notification settings - Fork 156
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
File actions API #149
Comments
|
some file actions will be about viewing and editing files, see #215 |
As discussed with @pvincent: Optionally, we can have multiple file-actions registered and let the user choose the default app as it's common in windows. (The preferred app should be saved to the user setting) All those file-actions will also be available in the context-menu (right-click and the dot-dot-dot-menu) |
@PVince81 Is there already a core API that exposes what actions are available for a file? (actions from core or apps) Clients want to use this as well. Imagine a server app that shows up in the "three-dot-menu" in the web UI, but also in the "right-click-menu" of the desktop app for example. (would open the web UI with the selected app open in a defined state) |
The current core API is neither HTTP nor PHP. It's pure JS. |
I would not allow to change the behavior of the default action. I find this very confusing. Furthermore in case two apps register the default action: who wins? Furthermore: registered actions can be rather heavy weigthed: collabore, only office, office online. |
file actions are somehow tied to the file list: ex trashbin has different actions |
please take a look at the screenshots from #324 (comment) |
yes. the above is only the "open with" action. |
It is possible to register multiple actions on a per-filetype basis since #356 is merged. The app can additionally enable editing feature for it's own filetypes, so they will appear in ActionLauncher if you edit a file instead of just showing it; The App could react accordingly. As discussed while UX workshop, other actions like share, rename, delete, etc. are not globally available, and therefore not exposed via 'phoenix app registration API' So it seems, that all requirements of this issue are fulfilled. |
A Phoenix app must be able to register custom file actions with handlers.
See the FileActions JS class in core to get an idea:
FileActions
, the registry for all file acitons: https://github.com/owncloud/core/blob/master/apps/files/js/fileactions.js#L29FileAction
the object to specify actions: https://github.com/owncloud/core/blob/master/apps/files/js/fileactions.js#L717@felixheidecke we might want to chat about this at some point
The text was updated successfully, but these errors were encountered: