Jason Tackaberry wrote:
> Ultimately the question comes down to: where should authoritative
> user-created metadata be stored?
Yes.
> The two obvious responses are 1. keep user-generated metadata in an fxd
> file, and have beacon parse it and duplicate it in its database
> (updating the db when the fxd changes), or 2. store the user-generated
> metadata directly in beacon's db and treat it as authoritative.
The first solution has one big advantage: the user can take care of
stuff. It is easy to edit a fxd, complicated to edit the db. It is
easy to just move both files to a new location, you loose your
metadata if you move while beacon is not running.
There are some information in the db that may not belong to the
fxd. When was the item last played? Nice information for Freevo but if
you loose that, it is not a big deal. So maybe beacon should be able
to read fxd files. Maybe fxd files is not the right solution, maybe
something else.
> Cover images for readonly media would be stored in the overlay
> directory, which beacon does support directly.
That is why I added it. You need a place to put fxd files and images
for read-only media.
Dischi
--
I am a friend of the working man, and I would rather be his friend
than be one.
-- Clarence Darrow
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
