First I'd like to point out (what I didn't explain thourough last
mail) that this is just the xml for how to build the menus i.e. on
web. The data supplied in this document is default values, and
user data will be supplied in another file.
During parsing, an object of the proper datatype is created for each
entry in the xml-structure document.
Rob Shortt <[EMAIL PROTECTED]> writes:
> Could we have a special tag for most of the config items?
>
> <major_audio_ctrl value="PCM">
Yes, it's possible, but that would make it harder to make both
a generic parser and the DTD.
OTOH that would move the structure-description to the DTD/XML
Schema. I consider this "future enhancement".
Right now I think I will only let datatypes get their own tag.
Please comment.
> <control_all_audio value="True" />
Right now it is
<variable name="CONTROL_ALL_AUDIO" value="True" />
I think this is a more xml-ish way of doing it. Any comments?
> That stuff doesn't matter a whole lot to me, just some thoughts from a
> non-xml guy.
Thoughts appreciated!
> However, there are some complications with the current configuration
> style that I would like to work around by using xml. For centralizing
> the channel list and frequency table for slave apps, as well as adding
> support for multiple V4L devices - and combinations of devices; I
> have added a class in config.py called VideoGroup and it would
> currently be used in local_conf.py like this (Actually this is my
> running config):
This is almost tao. I've been thinking of asking you about this, but
haven't done anything about it. *zap* there it is :-)
> VIDEO_GROUPS = [
> VideoGroup(vdev='/dev/video0',
> adev=None,
> input_type='tuner',
> tuner_type='external',
> tuner_norm='NTSC',
> tuner_chanlist='us-cable',
> tuner_chan='3',
> external_tuner='tv.irtrans_echostar',
> et_conf='/etc/lircd-transmit.conf',
> et_device='/dev/trans',
> et_remote='JVC_4700',
> desc='Bell ExpressVu',
> recordable=True),
> VideoGroup(vdev='/dev/video1',
> adev='/dev/dsp1',
> input_type='tuner',
> desc='ATI TV-Wonder',
> recordable=True),
> VideoGroup(vdev='/dev/video2',
> adev=None,
> input_type='webcam',
> desc='Logitech Quickcam',
> recordable=False),
> ]
>
> Ok, that is WAY WAY WAY too complicated for users to get their hands
> on. They will have to keep the syntax correct (make sure all commas
> and round / square brackets are in place) and also know how to pass
> contructor values to this class. I think its _nasty_.
Agree, it should be filtered by a configuration interface before the
user sees it.
Since VideoGroup is an object/"datatype", I think it should have its
own tag.
The xml-structure will look something like this:
<list name="VIDEO_GROUPS">
<videogroup>
<path name="vdev">
<description>
video device
</description>
</path>
<path name="adev" implied="True" default="">
<description>
audio device
</description>
</path>
..
..
I will implement this into my draft right away, and post it later today.
> However, by using an xml config file I think it would be great to be
> able to say:
>
> <videogroups>
> <videogroup name="Bell ExpressVu">
> <vdev value="/dev/video0">
> <adev value="/dev/dsp0">
> <input_type value="tuner">
> <tuner_norm value="NTSC">
> <tuner_chanlist value="us-cable>
> <tuner_chan value=3>
> <external_tuner value="tv.irtrans_echostar">
> <recordable value=1>
> </videogroup>
> <videogroup name="ATI TV-Wonder">
> <vdev value="/dev/video1">
> <adev value="/dev/dsp1">
> <input_type value="tuner">
> <recordable value=1>
> </videogroup>
> <videogroup name="Logitech Quickcam">
> <vdev value="/dev/video2">
> <input_type value="webcam">
> <recordable value=0>
> </videogroup>
> </videogroups>
>
> I think that is more user friendly, and I would (as a user) rather do
> it that way myself.
Agree, but I'm not too sure about the tag-naming. Comments
appreciated!
NB:
When this was discussed on the list for the first time, many people
said that the user-friendlyness of xml is overrated. My opinion on
this is that the user shouldn't need to see the xml. XML is only used
to make an easy parsable config. So far I haven't aimed to make the
xml user-friendly. The user-friendly aspect is in the interface.
--
Eirik Meland
A: Top posters.
Q: What is the most annoying thing on Usenet?
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
