Skip to content

Make the file drop feature more obvious #2207

Closed

Description

@jasonbayton

I wasn't aware initially when I installed NC the public filedrop option had been included until I read this article:

https://nextcloud.com/why-open-source-rocks/29

Then it took me a little while longer to actually be able to enable it as Google searches and document hunting on docs.nc led me nowhere.

It was only upon clicking "Allow editing" and "Hide file listing" out of sheer luck that I realised that's what it is..

Can this be made more obvious in a future update? Perhaps promote it as a public filedrop rather than wording it as hiding directory contents?

It'd be a little clearer.

Context:
https://help.nextcloud.com/t/filedrop-can-it-be-a-little-more-obvious/659

Activity

  1. tflidd commented on Nov 20, 2016

    @tflidd
    Contributor

    If you only want to change the wording, the string can be found here:

    hideFileListLabel: t('core', 'Hide file listing'),

    (you can clone the nextcloud-server-repo, create a new branch, make and submit the changes and then create a pull request).

  2. jasonbayton commented on Nov 20, 2016

    @jasonbayton
    MemberAuthor

    I think a discussion needs to be had first as the wording was seemingly chosen for a reason, but I'd hope for a little more logic than just a wording change as outlined in the context thread on help.nc:

    https://help.nextcloud.com/t/filedrop-can-it-be-a-little-more-obvious/659/5?u=jasonbayton

  3. MorrisJobke commented on Nov 21, 2016

    @MorrisJobke
    Member

    @jancborchardt We talked exactly about this during the hackweek ;)

    It's mentioned in the review of 11 as "Think about 'hide file listing'" - see #2134

    @nextcloud/designers Any ideas how to make this more discoverable? Maybe also show this by default (when "Allow edit" is not ticked but then show it disabled?)

  4. jasonbayton commented on Nov 21, 2016

    @jasonbayton
    MemberAuthor

    @MorrisJobke might've been from my original post, as that was June 😄

    I made this suggestion:

    Where clicking allow edit greys out the file drop option, similarly the opposite happens when file drop is clicked.

    and.. err.. this one too, but I make a lot of drop folders for media uploads after gigs, so I'm not sure how often the "normal" userbase would use this:

  5. jancborchardt commented on Nov 21, 2016

    @jancborchardt
    Member

    @jasonbayton that seems good! I’d go first with the rewording in the share menu. Adding it to the »New« menu is a bit too much since the Collabora stuff is also in there.

    @nextcloud/javascript what do you think?

  6. jancborchardt commented on Nov 22, 2016

    @jancborchardt
    Member

    There’s a pull request for the wording at #2243

    In addition, and what I also mentioned there, instead of the greying out which would be a bit confusing I propose:

    • showing both options
    • making them radio buttons
    • with »Allow upload and editing« being the default

    This is probably something for Nextcloud 12 though because of the feature freeze.

  7. added this to the Nextcloud 12.0 milestone on Nov 22, 2016
  8. jasonbayton commented on Nov 22, 2016

    @jasonbayton
    MemberAuthor

    I'm game for radio buttons. But there'd need to be a read-only radio option too, since that's what shares are by default (and radio always defaults to one option)

  9. jancborchardt commented on Nov 24, 2016

    @jancborchardt
    Member

    Right, also as you mentioned in the pull request. We need to go for a 3-option radio button. :)

  10. jasonbayton commented on Nov 24, 2016

    @jasonbayton
    MemberAuthor

    I'm not a big GH user, I may have accidentally commented on the PR and then realised it should be here!

  11. 5 remaining items

  12. added a commit that references this issue on Mar 26, 2017
  13. added a commit that references this issue on Mar 28, 2017
  14. MorrisJobke commented on Apr 30, 2017

    @MorrisJobke
    Member

    @jancborchardt We awaited some help here from you but the PR was closed in the meantime, because of inactivity: #3784

  15. jasonbayton commented on Apr 30, 2017

    @jasonbayton
    MemberAuthor

    Don't leave us hanging @jancborchardt!

  16. Espina2 commented on May 3, 2017

    @Espina2
    Contributor

    I think @eppfel open a pull request with the same improvoment but based on this, #4273

  17. jasonbayton commented on May 3, 2017

    @jasonbayton
    MemberAuthor

    So I don't see the changes in 12 beta for a radio button arrangement. Is it going to make the final?

  18. MorrisJobke commented on May 3, 2017

    @MorrisJobke
    Member

    So I don't see the changes in 12 beta for a radio button arrangement. Is it going to make the final?

    It wasn't finished in time.

  19. jasonbayton commented on May 3, 2017

    @jasonbayton
    MemberAuthor

    Bummer. Bring on 12.1! 🤣

  20. MorrisJobke commented on May 3, 2017

    @MorrisJobke
    Member

    Bummer. Bring on 12.1! 🤣

    I guess we will have no 12.1 ... the next one will be 13. 🤔

  21. added a commit that references this issue on May 3, 2017
  22. MorrisJobke commented on May 4, 2017

    @MorrisJobke
    Member

    Fix for this is in #4681

  23. MorrisJobke commented on May 4, 2017

    @MorrisJobke
    Member

    Merged

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions