[Kdenlive-devel] <screen> 's turn for an inspection now :-)

[Jason Wood]

Hi,

Ok, whilst I am still coding up the parsing into a dialog classes (will commit 
later tonight if all goes well) I have been thinking about the <screen> 
description.

First, in the same way that we have seperate video/audio codec sections for 
file formats, I think the same should apply for the screen as well. 
Currently, there may only be one audio output, but we can assume that in the 
future we might support oss, alsa, esd, aRts, mas, etc

I would prefer a more generic term than X11 for the screen descriptions - I 
cannot guess at what screen types might be available in the future, but the 
possibility of a framebuffer in a second monitor sounds quite convincing. In 
other words, a display does not necessarily need the X server (and would 
return a winID of 0 when created in this case). I think a more generic tag 
name like <display> or <graphics> might be better.

For the sound, as I already mentioned I think that it should have it's own 
tag, so that it can be set seperately.

Something like this ?

<screen>
	<visual name="xv" fallback="rgb"/>
	<visual name="rgb" />
	<audio name="arts" fallback="alsa"/>
	<audio name="alsa" fallback="oss"/>
	<audio name ="oss"/>
</screen>

Or perhaps, to honour the grouping of codecs, this is more appropriate :

<screen>
	<visuals>
		<visual name="xv" fallback="rgb"/>
		<visual name="rgb" />
	</visuals>
	<audios>
		<audio name="arts" fallback="alsa"/>
		<audio name="alsa" fallback="oss"/>
		<audio name ="oss"/>
	</audios>
</screen>

I'm not entirely happy with the names, but what do you think?

Cheers,
Jason

-- 
Jason Wood
Homepage : www.uchian.pwp.blueyonder.co.uk