Show in Media sources

[Dan Meltzer]

On Mon, Feb 8, 2010 at 12:54 PM, Casey Link <unnamedrambler at gmail.com> wrote:
>> This solution seems a hell of a lot more complicated and convoluted
>> than simply having another entry in the context menu, and I still
>> havn't heard a good reason against it.
>
> This has been discussed at excessive length.
> See: http://marc.info/?l=amarok-devel&w=2&r=1&s=Decision+needed+for+%22Move+to+Trash%22&q=b

I already addressed one point (The lenght of context menu) and it's
moot because it's a silly arguement.

The other point (not a playlist action) could be said about edit track
details as well, it could be said about the album cover actions.
Should we remove those for the same reason?

The ambiguity (where is the soruce coming from) isn't really a valid
arguement, because you are going to be deleting the file that is being
played, not another copy somewhere else.  If we show the path of the
file (and don't have an option at all for http streams, obviously).
This should probably even be implemented via a capability of some sort
perhaps, so that deleting from media devices can be handled properly.

Mark made the point in that thread that we should try and keep menus
consistant.  "Show in media source" is not only completely ambiguous
in it's naming, it doesn't appear anywhere else in amarok
(consistancy? I think not).

That "excessive length" discussion certainly didn't end in any sort of
agreement, so I'm not exactly certain why we consider it solved,
especially now that we are seeing some of the problems involved with
"Show in source".

The other thing to think about: As a user, if you wanted to delete a
track that was in your playlist, would you think to yourself: "Okay, I
need to right click on the track in the playlist, then choose show in
media source, then move my mouse over and right click on the track,
then choose delete, then accept the dialog?"  I certainly wouldn't,
I'd probably just check the playlist, and when I didn't see a delete
action I'd go to the edit track details and open it in dolphin (yuck),
give up (yuck), or manually search in the collection and hope
magically that the delete file option appeared there.

Other Food for thought:  Why should I assume that delete file in the
collection browser is any more likely to delete it from the hard disk?
 If it's in the collection pane, than wouldn't it be equally as
reasonable to expect pressing delete there to remove it from the
collection?  Maybe we should limit all file interactions to the file
browser--for consistancy, of course.


> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>