11 Commits (5cd1880daa048a685da689c7f41a2e50486494de)

Author	SHA1	Message	Date
Julius Härtl	5e4eda1ae0	Remove deprecated legacy file actions ... Signed-off-by: Julius Härtl <jus@bitgrid.net>	6 years ago
John Molakvoæ (skjnldsv)	bd1929a3b1	Fixed tests ... Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>	8 years ago
Daniel Calviño Sánchez	7760f16521	Trigger events before and after a file action is executed ... In the same way that other elements can know when a FileAction is registered or a default action is set this commit makes possible to be notified before and after a FileAction is executed. This is achieved by wrapping the registered action handler in a custom function that notifies the listeners before and after executing the handler itself. Due to this approach only FileActions registered through "registerAction" trigger the events, although that is not a problem as this is how the actions should be added to the FileActions anyway. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>	8 years ago
Vincent Petry	254576e1f7	Do not encode slashes in "dir" URL param in files JS	10 years ago
Vincent Petry	fdeafef6a0	Auto-add fileid in URL for currently displayed folder	10 years ago
Vincent Petry	05cf940983	Tentative fix for legacy file actions unit test side effect ... Sometimes the JS unit test with legacy file actions fail. This fix runs the legacy file actions tests on a dummy instead of the real one.	11 years ago
Vincent Petry	22653e21a2	Propagate file action changes to the file lists ... Whenever an app needs to register an event late, it does that on the original file actions object. Since the file actions that the file list work on is a merged list, not the original one, the registration event needs to be propagated there as well.	12 years ago
Joas Schilling	1d0ac9a2c5	Fix tests	12 years ago
Vincent Petry	ef59c69dc8	Distinguish legacy file actions from regular file actions ... Legacy file actions are registered by legacy apps through window.FileActions.register(). These actions can only be used by the main file list ("all files") because legacy apps can only deal with a single list / container. New file actions of compatible apps must be registered through OCA.Files.fileActions. These will be used for other lists like the sharing overview. Fixed versions and sharing actions to use OCA.Files.fileActions, which makes them available in the sharing overview list.	12 years ago
Vincent Petry	6fd084243b	Fixed many issues, clean up ... - fixed upload and storage statistics - fixed infinite scroll to use the correct contain for scroll detection - fixed unit test that sometimes fail for rename case - controls are now sticky again - fixed selection overlay to be aligned with the table - fixed "select all" checkbox that had id conflicts - fixed public page - fixed global actions permissions detection - fix when URL contains an invalid view id - viewer mode now hides the sidebar (ex: text editor) - added unit tests for trashbin - clean up storage info in template (most is retrieved via ajax call now)	12 years ago
Vincent Petry	9d38e3602b	Namespacing for FileList, FileActions and trashbin app ... - FileList is now an instantiable class - FileActions is now in namespace - added App class for trashbin app - moved trashbin overrides into classes extending FileList - replaced many static calls with "this." or "self." to make the classes reusable/extendable - new URL parameter "view" to specify which view is shown, for example "files" or "trashbin" - added OC.Util.History utility class in core for handling history - moved URL handling/routing to OCA.Files.App - popstate will correctly update the current view and notify the view of the URL change so it can update the current dir - added JS unitt tests for the trashbin app - fixed public app to work with the new namespaces	12 years ago