I'm again at a sorta -0.5 on this; in JSF 1.2, I'd rather provide
EL functions to do formatting, since that gives you format
functionality in all components instead of just one. (ADF Faces
does just this in JDev 11). That still leaves JSF 1.1 users with
just h:outputFormat, which isn't great.
-- Adam
On 9/4/07, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> What about tr:outputFormat? This would be a direct extension of the
> core h:outputFormat with the skinning, partialTriggers and other
> functionality that Trinidad provides added to it?
>
> On 9/4/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> > -0.5; outputText performance is really critical to overall performance,
> > and even adding a boolean attribute slows it down a bit.
> >
> > -- Adam
> >
> >
> > On 9/4/07, Danny Robinson <[EMAIL PROTECTED]> wrote:
> > > Should we look at providing this variable replacement functionality into
> > > outputText. Although I'm against just parsing the text by default, as
> > > this
> > > would just add unnecessary parsing in 99% of the cases. Should we instead
> > > look at an extra attribute that forces parsing of the string for variable
> > > substitution.
> > >
> > > Danny
> > >
> > > On 9/4/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> > > > BTW, for all of these examples, you should just use tr:outputText
> > > > instead of tr:outputFormatted.
> > > >
> > > > outputFormatted really has nothing to do with "outputFormat".
> > > > What tr:outputFormatted gives you is support for (a subset of)
> > > > HTML formatting without opening the security hole of
> > > > escape="false".
> > > >
> > > > -- Adam
> > > >
> > > >
> > > >
> > > > On 8/30/07, Andrew Robinson <[EMAIL PROTECTED] > wrote:
> > > > > Well you could do:
> > > > >
> > > > > <tr:outputFormatted value="#{myfunc:format2(str, arg1, arg2)}" />
> > > > >
> > > > > where you could write format1, format2, etc. EL functions to do the
> > > work.
> > > > >
> > > > > You could also do:
> > > > >
> > > > > <t:buffer into="#{formattedString}">
> > > > > <h:outputFormat value="#{message.key}">
> > > > > <f:param value="param1" />
> > > > > </h:outputFormat>
> > > > > </t:buffer>
> > > > >
> > > > > <tr:outputFormatted value="#{formattedString}" />
> > > > >
> > > > > On 8/30/07, Paul Mander < [EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > Andrew Robinson-5 wrote:
> > > > > > >
> > > > > > > Well, that is not localizable
> > > > > > >
> > > > > > > I think the use case that he means is more like:
> > > > > > >
> > > > > > > <tr:outputFormatted value="#{messages.str}">
> > > > > > > <f:param value="#{myarg}" />
> > > > > > > </tr:outputFormatted>
> > > > > > >
> > > > > > > messages.properties
> > > > > > > str = Test {0} param
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > That's a better example.
> > > > > >
> > > > > > --
> > > > > > View this message in context:
> > > http://www.nabble.com/trinidad-outputFormat-and-f%3Aparam-support-tf4347417.html#a12401317
> > > > > > Sent from the MyFaces - Users mailing list archive at Nabble.com.
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Chordiant Software Inc.
> > > www.chordiant.com
> >
>
