Re: Whole House Audio schema

[Stuart Booth]

On Sun, 08 Feb 2004 10:05:51 -0000, "mark_harrison_uk2"
<<a
href="/group/xap_automation/post?postID=0ZEvH4Ah7hrwlFT6nq3MmVxzD6B96jYVGMzzllOI8ivDXkuTCSLQCHQjb9NmTd-xTRnJ3qbARr31">mph@a...</a>>
wrote:

>1: The long name
>- "xAP Schema for MP3 Whole House Audio v2.2"

>Proposed name
>- "xAP Schema for Audio Control v2.3"

Works for me. I just picked "Whole House Audio" as that was what
we
were talking in terms of at the time. I can see that that title
extends to other areas though.

>At present, xap-audio.audio contains two allowable blocks:
>- audio.mute
>- audio.mixer

>I would like to add a third

>- audio.sourceselect
>{
>    AVSource= <name>
>}

Since you repeat the "source" (sub)string, why not just call it:

xAP-audio.source
{
Select=<name>
}

Have said that, I like how "xAP-Audio.SourceSelect reads in comparison
to that.

Or how about:

{
Input=<name>
}

...to remove "select" from the message request?

I've no strong preferences either way, just a thought. We all write
differently.

S
--
Stuart Booth <<a
href="/group/xap_automation/post?postID=REt_qpv6qbyQDws-EIhVbeM2QU4_g2NO4b6nJcSoDvMthUqRMmyFsuHAdTS9dfNunNpM-Coxxg7F8K6WHQ">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net

<a href="http://www.xapautomation.org/";>http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>