David Bernard <[EMAIL PROTECTED]> writes: > Maybe you could try this ugly hack (non-tested) : > > define and use FieldGroup instead of FieldSet in your form. > > class FieldGroup(turbogears.widgets.FieldSet): > template = """ > <div xmlns:py="http://purl.org/kid/ns#"; py:strip="True"> > <span py:for="widget in widgets" py:strip="True"> > <span py:if="widget.label and widget.labeltext" > py:replace="widget.label.insert(widget.labeltext)"/> > <span py:if="not widget.label or not widget.labeltext" > py:strip="True"> </span> > <span py:replace="widget.insert(getattr(self.widget_value, > widget.name, None), input_values, widget_error.get(widget.name, None))"/> > <span> > </div> > """ > sample_code = "widget = FieldGroup(widgets = [TextField()])"
From the code above I don't think it will... But don't worry. It was just cosmetic. > Sorry I can't help you more, I'm working on another Widgets API (proposal) > which avoid those problems. No problem. ;-) I was just trying to see how the FieldSet worked and what it created as output for this case. BTW, in which key server is your PGP/GPG key published? -- Jorge Godoy <[EMAIL PROTECTED]>
pgpr82Pi80D3N.pgp
Description: PGP signature
