Brian Enigma wrote:
> Hello, all!
Ho
> I thought a good refresher course might be to update some of the
> documentation to reflect what the code actually does. Since some of
> the XML metadata Wiki documentation (DocumentationPage, section 7 and
> UsageInfo) seemed to be missing or incomplete, I decided to start
> there. Now, I think I know what is going on here, but I would really
> like to bounce my assumptions/questions off of the rest of the group
> in order to be certain (this is all based on the HEAD of the main
> trunk of CVS, and I did not see anything in recent mailing list
> archives):
Good. Ask any question you like and than add it to the WiKi.
> 1) The DTD in /Docs does not quite seem to jive with some sample files
> (which work) and the documentation. I am going to guess that the
> documentation is incorrect--or more likely just missing a layer of
> tags. The DTD shows the doctype (and, hence, outermost element) is
> <freevo>...</freevo>, but the documentation shows examples of
> <movie>...</movie> as being the root element. I am going to guess
> that a code change sometime recent pushed the "movie" tag down one
> level so that everything can be an fxd file (because everything below
> the <freevo/> matches up fine.
Everything is between <freevo> and </freevo>. The fxd files can
contain more than just movie informations, also skin and directory
settings (more on that later)
> 2) The DTD's root element is freevo (disc-set|movie)+, but one of the
> examples (in fact, one I modified to reach my favorite net radio
> stations) has a great number of things under the "freevo" element.
> Classical.fxd's "freevo" node has children for tag, logo, audio, and
> info. I am guessing that the DTD did not get updated to reflect this.
I don't know the fxd extention for audio urls, sorry.
> 3) Some of the code (I believe it was in directory.py) refers to
> "album.xml." Is this the same as a movie.xsd style file?
No, album.xml and xml files for images are from a program called
'bins'.
> 4) The folder, movie, and skin fxd's "basically" interchangeable,
> right? (I realize that not every element is parsed and used
> everywhere, but in a basic context, they share the same DTD and
> general data elements.)
Yes, for movies you can have disc_set, movie and skin inside the
freevo root tag, for directories folder and skin and the skin files
only contain skin. There is a skin called 'image'. You can't use it
directly, but you can inherit from it in your movie or folder fxd file
to add background picture support.
> 5) .password files (which look to contain a plaintext password locking
> access to a directory) are not in the documentation. Should they be?
Yes. There are lot of things missing. Some people ask questions here
and noone put answers into the WiKi :-(. Someone should go through the
list archive and ad all the cool stuff into the WiKi.
> 6) There do not seem to be any good references for what the <setvar/>
> names/value and a few of the other tags are used for. What parts of
> the code should I focus on for this?
It's in directory.py. Some variables can have a different value for
some directories. You can override them with <setvar>
> I think that just about covers it for now. I am slowly trying to
> wrap my brain around the code. There is a lot of it, but it seems to
> have some pretty good internal documentation, which helps a lot!
But outside the code, some important stuff is missing in the
docs. Small brainstorm what may be missing: image skin for background
images in folders, inherit a folder.fxd from a movie.fxd (user mailing
list a week ago), all the nice deactivated plugins like usb and
camera...
Dischi
--
He didn't look mad, but they never did.
-- (Terry Pratchett, Strata)
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
