Skip to content
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

Ability to set permissions before sharing #13229

Open
4 tasks
jancborchardt opened this issue Dec 22, 2018 · 11 comments
Open
4 tasks

Ability to set permissions before sharing #13229

jancborchardt opened this issue Dec 22, 2018 · 11 comments

Comments

@jancborchardt
Copy link
Member

jancborchardt commented Dec 22, 2018

Done

  • Android
  • iOS
  • Desktop
  • Web UI

In the past we often talked about one of the core issues of our very easy share flow: You basically share with edit permissions always, and have to adjust later. This results in a small window where people could change or delete stuff.

This proposal fixes this very simply by adding an indicator of the current setting in the sharing input:

  • ✏ Allow editing (default)
  • 👁️ Read-only

Now when you change this current setting, it could be remembered. Either for the session only, per file/folder or simply globally. We can discuss what’s best and most feasible.
sharing permissions

This is the code I used in the mockup (based on Personal settings federation dropdown ;), if anyone wants to start implementing it:


<div class="">
    <span class="icon-rename">
    	<span class="icon-triangle-s"></span>
    </span>
    <div class="popovermenu bubble menu menu-right">
        <ul>
        	<li>
        		<a href="#" class="menuitem permanent">
        				<span class="icon-rename"></span>
        			<p>
        				<strong class="menuitem-text">Allow editing</strong><br>
        				<span class="menuitem-text-detail">Recipients will be able to edit and reshare</span>
        			</p>
        		</a>
        	</li>
        	<li>
        		<a href="#" class="menuitem permanent">
        				<span class="icon-toggle"></span>
        			<p>
        				<strong class="menuitem-text">Read-only</strong><br>
        				<span class="menuitem-text-detail">Recipients will not be able to change anything</span>
        			</p>
        		</a>
        	</li>
        </ul>
    </div>
</div>

What do you think @nextcloud/designers @MorrisJobke @rullzer?

If we go forward with this, it’s also something we need to align in the desktop client and mobile apps: @nextcloud/ios @nextcloud/desktop @nextcloud/android

@rullzer
Copy link
Member

rullzer commented Dec 22, 2018

This looks surprisingly similar to a discussion I once had with @LukasReschke ;)

I think it is a huge step forward. In general even like the more explicit flow. (like dropbox/google have, where you can fine tune it even more in a modal etc. But other discussion).

Anyway. Yes please! Being able to set the permissions beforehand would be awesome!

@violoncelloCH
Copy link
Member

violoncelloCH commented Dec 22, 2018

This is the code I used in the mockup (based on Personal settings federation dropdown ;), if anyone wants to start implementing it:

shouldn't we use Vue.js for this popup? We have the PopoverMenu component for this. cc @nextcloud/vue

@juliusknorr
Copy link
Member

@violoncelloCH I don't like the idea of putting in vue just for the popover menu, this adds quite some overhead if we don't just migrate the whole sharing tab to vue.

@violoncelloCH
Copy link
Member

@juliushaertl ah, I see... so this could be a reason to switch the whole sharing tab/sidepanel to vue... don't we want to switch to vue and get rid of jquery completely anyway? (this would be one step then as mentioned in #12980)

@jancborchardt
Copy link
Member Author

@violoncelloCH The federation popup is also implemented without Vue.js, so let’s discuss this separately. :) This is tracked in the sidebar standardization at #10289

@ronivaldo
Copy link

ronivaldo commented Dec 26, 2018

BTW, @jancborchardt the default option is checked for "Can Edit" checkbox. It would be great if we could have a setting for this in order to change the default behavior of the entire application. I searched for this but I could not find it.

@jancborchardt
Copy link
Member Author

jancborchardt commented Dec 26, 2018

@ronivaldo this is accounted for in the specification in the first post:

Now when you change this current setting, it could be remembered. Either for the session only, per file/folder or simply globally. We can discuss what’s best and most feasible.

And I’d say it should be remembered globally: Much simpler, and then it would be a setting without people needing to change a specific setting, but it just being based on their workflow.

@jospoortvliet
Copy link
Member

FWIW I think it is a brilliant solution!

@jancborchardt jancborchardt added this to the Nextcloud 17 milestone Feb 22, 2019
@jancborchardt
Copy link
Member Author

@rullzer @MorrisJobke FYI I tentantively set this to the 17 milestone so it doesn’t get forgotten. :) We wanted to tackle it for a long time, and now there’s a good spec and mockup.

@tobiasKaminsky
Copy link
Member

Now when you change this current setting, it could be remembered. Either for the session only, per file/folder or simply globally. We can discuss what’s best and most feasible.

Here I vote for "global". In opposite of grid vs list view decision, I think this is not that much folder based, so having the last set configuration available again is good enough…

@tobiasKaminsky
Copy link
Member

As decided on hackweek: always switch to "edit" as default, like it is now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants