Re: Issues with Label Components with Tapestry 4.0

2006-07-21 Thread mraible
I ended up overriding the default FieldLabel: http://fisheye5.cenqua.com/qsearch/appfuse/?q=FieldLabel -- View this message in context: http://www.nabble.com/Issues-with-Label-Components-with-Tapestry-4.0-tf1686779.html#a5434006 Sent from the Tapestry - User forum at Nabble.com. -

Re: Issues with Label Components with Tapestry 4.0

2006-06-21 Thread Todd Orr
I have the same need to add a span in the label. Did you ever come up with a complete solution to this? On 6/1/06, mraible <[EMAIL PROTECTED]> wrote: My issue isn't with label, it's with the inputs. I have the following in my custom ValidationDelegate: public void writeAttributes(IMarkupW

Re: Issues with Label Components with Tapestry 4.0

2006-06-01 Thread mraible
My issue isn't with label, it's with the inputs. I have the following in my custom ValidationDelegate: public void writeAttributes(IMarkupWriter writer, IRequestCycle cycle, IFormComponent component, IValidator validator) { if (isInError()) {

Re: Issues with Label Components with Tapestry 4.0

2006-06-01 Thread Jesse Kuhnert
Sure, but at that point you are basically overriding the behaviour provided by the ValidationDelegate when it does before/after field rendering (not talking about FieldLabel). The FieldLabel component already supports informal parameters. I noticed in your first email you mentioned trying to do

Re: Issues with Label Components with Tapestry 4.0

2006-06-01 Thread Matt Raible
Is there an easy way to subclass FieldLabel and override the renderComponent() method to move writeLabelPrefix and writeLabelSuffix to be inside ? Thanks, Matt On May 31, 2006, at 2:51 PM, Ryan Holmes wrote: Your problem getting the span tag where you want it is due to how the FieldLabel

Re: Issues with Label Components with Tapestry 4.0

2006-05-31 Thread Ryan Holmes
Your problem getting the span tag where you want it is due to how the FieldLabel component renders itself. Here's the relevant part of FieldLabel.renderComponent(): delegate.writeLabelPrefix(field, writer, cycle); writer.begin("label"); if (id != null) writer.att

Re: Issues with Label Components with Tapestry 4.0

2006-05-29 Thread Matt Raible
Matt Raible wrote: Andreas Andreou wrote: try component.getBinding("class") if that's not null, do a getObject() on it Thanks. This works, but it also prints out duplicate "class" attributes. class="text large error" class="text large" It'd be nice to have something like: writer.append

Re: Issues with Label Components with Tapestry 4.0

2006-05-29 Thread Matt Raible
Andreas Andreou wrote: try component.getBinding("class") if that's not null, do a getObject() on it Thanks. This works, but it also prints out duplicate "class" attributes. class="text large error" class="text large" It'd be nice to have something like: writer.appendAttribute("class", "va

Re: Issues with Label Components with Tapestry 4.0

2006-05-29 Thread Andreas Andreou
try component.getBinding("class") if that's not null, do a getObject() on it Matt Raible wrote: Hmmm, I'm guessing the answers to my questions below are "no, this isn't possible." ;-) Here's another question - is it possible in my custom Validator to get the existing CSS classes on a componen

Re: Issues with Label Components with Tapestry 4.0

2006-05-29 Thread Matt Raible
Hmmm, I'm guessing the answers to my questions below are "no, this isn't possible." ;-) Here's another question - is it possible in my custom Validator to get the existing CSS classes on a component? For example, I currently have: public void writeLabelAttributes(IMarkupWriter writer, IRe