Bugzilla – Bug 1980
Add confirm deletion popup for playlists
Last modified: 2008-12-15 11:57:38 UTC
From the forums: I think it would be a good idea to add a "Are you sure?" warning when the Delete Playlist option is pressed in the Browse Playlist screen. It is right next to the Edit Playlist button and over the Browse Playlists, so it is rather easy to hit accidently. (In fact, I just did so). -Steve ---------------------------------------- Steven Kramer
Created attachment 733 [details] confirm delete for Default and Fishbone other skins can be done similarly. strings and EditPlaylist.pm changes are the key part.
That confirmation UI is fine, but I'd like to see the delete and edit buttons farther apart. How about this: change the "Delete this playlist" to just "Delete" Then change "Edit Playlist" to just "Edit" Then change the string "Rename this playlist as:" to "Name:" And put all three "Rename", "Edit" & "Delete" to the right of the name field (in that order). The confirmation checkbox can then be right aligned under the Delete button when it appears. So it would look like this: Name: [Funky Grooves] (Rename) (Edit) (Delete) [] Confirm Delete What do you think of that?
I think you are a pain ;) All doable. I'll get all the skins reworked as well.
Have you been talking to my darling wife? :) You two have some shared opinions. Thanks!
Created attachment 735 [details] replacement browse_playlist.html for Default how does that look?
Created attachment 741 [details] strings, confirm handling, all skins reworked Change the required strings, added handling for the confirmation to EditPlaylist.pm and redid the forms in all the skins that had browse_playlist.html,even the skins that are otherwise out of date :)
committed to trunk at change 3993. reopen if there is anything you'd rather have changed.
Awesome job, KDF!
This bug has been fixed in the latest release of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.