>
> > What was the final functionality you were looking for?
>
>A way to dynamically choose/load skins and other config information that was
>particular to a client.
>
>Eventually that'll be driven from a session or cookie setting but I wanted
>to get the snippet in place first, so I thought I co
> Not sure why you would need to do this: if you've hardcoded the value, you
> can hardcode it below.
Agreed. It was not really a useful sample; it was a simplified example as I
was testing to illustrate my question about the nesting. After Vadim's
response, I understand a little more.
> If you'
Not sure why you would need to do this: if you've hardcoded the value, you
can hardcode it below. If you're not (I assume hardcoding was just
temporary) you should have access to the parameter from where it was set -
ie, using a matcher wildcard, or an action, etc. What was the final
functionali
> From: Per Kreipke [mailto:[EMAIL PROTECTED]]
>
> I'm new at C2 but it seems to me from looking at sitemap.xsl that the
> following (valid) sitemap snippet would result in some unintended
code:
>
>
>
>
>
>
>
>
>
>
>
>
>
I'm new at C2 but it seems to me from looking at sitemap.xsl that the
following (valid) sitemap snippet would result in some unintended code:
Every map:parameter generates a section of code that begins wit
