On Donnerstag 02 Oktober 2008, Dirk Meyer wrote: > > 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, [...]
Exactly. That's what I was thinking. Let beacon cache/index the information
and update it's db when the .fxd change, but let the .fxd be the
authoritative place.
> 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.
Good point. So there are actually at least three kinds of information:
- Duplicated/index information
- Lossless duplicates (e.g. thumbnails)
- Not-important user information (e.g. play counts)
- Information explicitly generated by the user (cover images, custom titles,
file grouping/composition, rating, ...)
> So maybe beacon should be able
> to read fxd files. Maybe fxd files is not the right solution, maybe
> something else.
Yes. For now, fxds seem to be the obvious solution, since they're there
already (data + code) and provide for all features we need. (OTOH, using
RDF-based semantic desktop formats in the future may be another option?)
--
Ciao, / / .o.
/--/ ..o
/ / ANS ooo
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- 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 Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
