Summary: | filter tracks by XML tags in description field | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Miles Stevenson <miles> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Miles Stevenson
2005-01-10 19:14:07 UTC
Oh, I forgot to mention. I realize that constantly scanning the Comments field of a large collection DB, and parsing for XML tags could prove to be a performance nightmare. Instead, I would recommend some way (possibly even flat text config file) to allow the user to "register" their own customs tags with amarok. This way, when amarok has to build a list of searchable fields, it can simply look in this config file for what custom fields have been "registered" by the user, and everything else can be ignored. A trickier part to solve would be how to create tags that are more complex than simple 1:1 mappings (I used simple nesting in my example). Such as who is playing what instruments. This would be something like Player - Artist Name - Instrument(s). At any rate, the goal would be able to create Smart Playlist such as "show me every tune where Miles Davis plays Flugelhorn, as opposed to Trumpet". This should be done by a script - no need to put it into amarok. we will have tags/labels soon. |