May be I am wrong but when I needed fields without labels in BeanEditor,
this is what I did
I extended PropertyEditBlocks as
public class PropertyEditBlocksWithoutLabel extends PropertyEditBlocks {
}
and the provided my own template
<div xml:space="default" xmlns:t="
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
<t:block id="tawus_text">
<input t:id="textField"/>
</t:block>
<t:block id="tawus_number">
<input t:id="numberField" class="t-number"/>
</t:block>
....
</div>
and it worked for me. So if I would have added t:errors for individual
fields that would have worked too right ? Isn't this what
Adam needs for now ??
regards
Taha
On Sat, Apr 9, 2011 at 10:10 PM, Howard Lewis Ship <[email protected]> wrote:
> What Adam was getting at is not direclty overridable via block
> parameters; in the BeanEditor and BeanEditForm, the block parameters
> allow you to override the editors for specific properties, but not the
> surrounding content, including the Errors component (in BeanEditForm).
>
> On Sat, Apr 9, 2011 at 8:42 AM, Taha Hafeez <[email protected]>
> wrote:
> > Hi
> >
> > You can provide you own contributions to BeanBlockSource and override the
> > default ones till new release. All you have to
> > do is override the class and use you own template.
> >
> > Checkout http://tapestry.apache.org/beaneditform-guide.html
> >
> > <http://tapestry.apache.org/beaneditform-guide.html>regards
> > taha
> >
> > On Sat, Apr 9, 2011 at 8:57 PM, Adam Zimowski <[email protected]>
> wrote:
> >
> >> Should I then keep my pages backed by BeanEditor and BeanEditForm and
> >> wait for 5.3/5.4 or is this something not on the 2011 horizon?
> >>
> >> Adam
> >>
> >> On Fri, Apr 8, 2011 at 7:28 PM, Howard Lewis Ship <[email protected]>
> >> wrote:
> >> > As we move away from the error bubbles, I think you'll see that errors
> >> > will naturally attach to the fields, and <t:errors/> will just display
> >> > errors not associated with a specific field.
> >> >
> >> > On Fri, Apr 8, 2011 at 5:01 PM, Adam Zimowski <[email protected]>
> >> wrote:
> >> >> By default BeanEditForm includes <t:errors/>.
> >> >>
> >> >> BeanEditor seems to expect that t:errors is placed outside if
> >> >> programmer wants it.
> >> >>
> >> >> Intuitively, I would expect a feature for both to support inline
> errors:
> >> >>
> >> >> <t:beaneditform inlineErrors="literal:true" />
> >> >> <t:beaneditor inlineErrors="literal:true" />
> >> >>
> >> >> with <t:error> rendered next to a field and some CSS class to
> override.
> >> >>
> >> >> That would be nice.
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: [email protected]
> >> >> For additional commands, e-mail: [email protected]
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Howard M. Lewis Ship
> >> >
> >> > Creator of Apache Tapestry
> >> >
> >> > The source for Tapestry training, mentoring and support. Contact me to
> >> > learn how I can get you up and productive in Tapestry fast!
> >> >
> >> > (971) 678-5210
> >> > http://howardlewisship.com
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: [email protected]
> >> > For additional commands, e-mail: [email protected]
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >>
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
