Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <408FFE18.9050904@reverycodes.com>
Date: Wed, 28 Apr 2004 14:55:20 -0400
From: Vadim Gritsenko <vadim@reverycodes.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7b) Gecko/20040316
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: fi:booleanfield[fi:styling/@type='output']
References: <1083013091.21555.47.camel@23.13 	yum.ot 	yum
In-Reply-To: <1083013091.21555.47.camel@23.13 	yum.ot 	yum
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Bruno Dumon wrote:

>I saw the following template in forms-field-styling.xsl:
>
>  <!--+
>      | fi:booleanfield with @type 'output' : rendered as text
>      +-->
>  <xsl:template match="fi:booleanfield[fi:styling/@type='output']">
>    <xsl:choose>
>      <xsl:when test="fi:value = 'true'">
>        yes
>      </xsl:when>
>      <xsl:otherwise>
>        no
>      </xsl:otherwise>
>    </xsl:choose>
>  </xsl:template>
>
>And was wondering what people are using this for? Or how this can
>possibly do something meaningful?
>
>The problem I see is that if a booleanfield is not present on the
>request, it will always be reset to false. So I'd rather remove this
>template then giving people the false impression this might work.
>

It worked just fine for all those pages were you just need to output 
value of the widget and don't need to read it. Also, this template works 
in combination with i18n:

    <i18n:text>foo.bar.<wt:widget id="myboolean"><wi:styling 
type="output" /></wt:widget></i:text>


Vadim