Decision needed for "Move to Trash"

Lukas 1lukas1 at gmail.com
Wed Jan 20 08:09:00 CET 2010


2010/1/20 Casey Link <unnamedrambler at gmail.com>:
> Here's a quick recap of both sides points:
>
> For "Move to Trash" from playlist:
> * needed to delete files that are not in the collection
> * more convenient than using the file browser or collection browser
>
> Against:
> * Deleting is a collection/file management action - the playlist is
> _not_ a file/collection manager
> * Adding it to the context menu of the playlist would make an
> already-pretty-big context menu even bigger. (Slippery slope!)
>
> That about sums up the discussion at the merge request and the bug
> report: https://bugs.kde.org/show_bug.cgi?id=170999
>
> Personally, I am against the inclusion of this feature. Deleting
> files/tracks is not an action that belongs in the playlist, because it
> is a collection management action.
>
> Another point along the same lines is that it is difficult to tell the
> source of a track in the playlist.. it may be a file in your
> collection, it might be online, it might be a duplicate of another
> track you already have. This is intentional, we treat all tracks the
> same in the playlist. If the Trash action was in the playlist, there
> would be ambiguity as to which actual file is being deleted.
>
> The solution is to do as Bart and Nikolaj have suggested: Add a "Show
> in Collection/File Browser" action to the playlist context menu.
> Initiating this action will show the selected track in the file or
> collection browser, where *ALL* the collection/file management actions
> can be accessed not just Trash.
>
> Casey
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>

What about "Actions" menu node in the playlist, having all functions
not realted to playing music. This could include "Mave to trash",
"copy to collection", "Edit track details". As we already have "Edit
track details" action, moving them all to a single node wont add any
more clutter.

And for deleting "wrong" copy, I think most uses is smart enought to
know what they want to delete.

Off topic, but not being able to copy playlist to portable mp3 player
is one of the most missing features my friends has been talking about.
Especialy when there is a need to copy tracks from variuos artist
(doing this from collection manager is not comforable, also it couses
slow paralel copying)


More information about the Amarok-devel mailing list