Hi,

I just finished a file called metadata.py. This file includes a basic
Info class, all items should use as item.info. This Info includes
mmpython info, not saved variables (like variables parsed from fxd
files) and saved variables for this item. Right, you can now save any
kind of information for an item, as long as it's based on a file or a
disc. It's not possible to store informations for created items like
movies from fxd files. I will think about how to add it.

How does it work? Similar to the mmpython cache (which is now inside
freevo), the data will be stored in the parent directory in the
overlay in a file called freevo.cache. This is pickled data, you can't
read it. 

As example I converted the AudioParser. It now doesn't write
folder.fxd files, it adds the info the the freevo.cache file. This is
a better solution, because now you can have two kinds of audio
information: one in the cache written by the parser and the second in
the folder.fxd. In most cases, you don't need the folder.fxd
anymore. Delete it (makes it faster). If e.g. the album information is
wrong, you can set the information in a folder.fxd to the correct
value. So basicly: folder.fxd for something I write, the cache file
for something a script writes. Simple as that.

But there is more: two more examples are the auto bookmark (adding
resume to the video item menu) and the video variable
'deinterlace'. This informations are now stored inside the
freevo.cache. So if you like, you can also store 'last played'.


Test it and send comments please.


Dischi

-- 
A day without sun shine is like, you know, night.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to