Thanks for fixing up the example. Much more clear (for me, anyway:))
Marcos

-----Original Message-----
From: Ian Hickson [mailto:[EMAIL PROTECTED]
Sent: Saturday, 6 January 2007 6:39 AM
To: Marcos Caceres
Cc: [email protected]
Subject: Re: [XBL] Editorial: make example for 3.7.3 easier

On Tue, 7 Nov 2006, Marcos Caceres wrote:
>
> In section 3.7.3, I suggest simplifying the example. It currelny says:
>  "Consider the following completely useless but conveniently simple
> binding:"
>
> I'm sorry, but this example is hardly simple (particulary as you have
> added content inheritance into the mix). It could be made a bit simpler
> if you added id's to the last 2 bindings (call them b and c). And maybe
> add a litte diagram showing that b->a and then when c is added to the
> mix it forms: (ROOT) -> c (implicit) -> b -> a
>
> Here is the new code,
>
> <xbl xmlns="http://www.w3.org/ns/xbl";>
>  <binding id="a">
>   <template> l <inherited> l <content> o </content> - </inherited> W
</template>
>  </binding>
>  <binding element="[X]" extends="#a" id="b">
>   <template> e <inherited> error </inherited> o <content> r </content>
</template>
>  </binding>
>  <binding element="[Y]" id="c">
>   <template> H <inherited> error </inherited> l <content/> ! </template>
>  </binding>
> </xbl>
>
> (note I also changed the last binding, is this correct?)
>
> so, then the reader can see where each bit of content is coming from:
>
> c b a a a a a b b c c c
> ------------------------------
> H e l l o - W o r l d !
>
> (I think the above is right, but might be best to check it over;))

I've done most of your suggested changes, though not the changes to the
templates (which I didn't understand). Please let me know if the new text
is ok or if it is still confusing.

Cheers,
--
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'




--
Marcos Caceres
http://datadriven.com.au

Reply via email to