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

Delete (and archive) a bin from within the bin #1000

Closed
remy opened this issue Jan 8, 2014 · 7 comments
Closed

Delete (and archive) a bin from within the bin #1000

remy opened this issue Jan 8, 2014 · 7 comments

Comments

@remy
Copy link
Member

remy commented Jan 8, 2014

Rather than having to go to your "homepage" to archive the bin.

Big question: what happens when you delete (or achieve) - do you get a new bin? Do you remain where you are? What about if you hit "save"?

@ghost ghost assigned dannyhope Jan 8, 2014
@remy
Copy link
Member Author

remy commented Jan 8, 2014

Could have "archive & next" or just "archive" - ala Flickr's organise "save & next" or "save".

@dannyhope
Copy link
Member

Our first step should be to introduce an “Archive” option to the “Bins” menu:

  • The user should not be moved to a different page – they should stay in the bin they’re in
  • Selecting this should cause a flash message should be shown, explaining that the bin has been archived.
  • Pressing ⌘Y should activate the command

screen shot 2014-01-09 at 10 01 15

Later we could provide options to automatically take you to the next bin and to show/hide a persistant archive control (which would work in a similar way

screen shot 2014-01-09 at 11 23 12

@remy
Copy link
Member Author

remy commented Jan 9, 2014

In addition, cmd+shift+del should delete the bin (and flash a message), but not reload the page - just tell you that the bin is deleted and won't be retrievable after you've left. I can do this inside of jsbin, and it's a way of creating (or converting) to an anonymous/deleted bin. Very, very useful to me.

@remy
Copy link
Member Author

remy commented Jan 9, 2014

Doing archiving/organisation of my existing bins, with 1,600 of them, isn't really something I'd do right now - I'd be keen to see the implicit structuring in place somehow (that's not to say that I don't think we should do this - I think your proposal also works).

@remy
Copy link
Member Author

remy commented Jan 23, 2014

Duplicate of #756 (though this #1000 issue has much more detail).

@remy
Copy link
Member Author

remy commented Jun 9, 2014

Implemented.

Discussion of "next" should be opened in a new issue (though already discussed in #1520 - should we copy this across or contininue in #1520?)

@remy remy closed this as completed Jun 9, 2014
@dannyhope
Copy link
Member

Perhaps "Automatically go to next bin after archiving" should be it’s own issue. Maybe we could tag these technically difficult issues as "revisit" or some such.

What do you think?

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

2 participants