nextcloud / files_lock

GNU Affero General Public License v3.0
25 stars 8 forks source link

UX review #141

Open juliusknorr opened 1 year ago

juliusknorr commented 1 year ago

File locking design review

25.04.2023:

Overall

Overview of the different scenarios -> ideal behavior

Lock State Action Behavior for lock owner ? Behavior for others
Locked by text (someone is working on this file) Open the fileOpen file ✅ Edit collaboratively ✅ Edit collaboratively
Alter file on the backend (e.g. restore a version, delete the file) Currently: blocked❌ n/a Currently: blocked- confirmation dialogue for person doing the action
- confirmation dialogue for person who has the tab open
- only acquire lock once someone makes a change?
- generally reduce the time that files are locked? Release lock after inactivity for x amount of time
- distinction between file which is open and file which is actively edited. inactive files are ok for deletion
- communicate with clients?
- Is file hasn't been autosaved for x mins, release lock
Upload from mobile/desktop clients Currently: blocked Currently: blocked
Locked by user Open file ❗ Edit alone ✅ Read only ✅ message that it is locked ❗ option to ask for access / break lock
Alter file on the backend (e.g. restore a version, delete the file) ✅ all allowedllowed ✅ ✅ Currently: blockedno actions allowed ✅
Upload from mobile/desktop clients all allowedallowed ✅