"Steve Bergman" <[EMAIL PROTECTED]> writes:
Can I take the lack of response on this to mean that no one would have
any objections to my submitting a patch?
I was waiting for someone else to answer, but I don't see a need for that.
And in fact, I'm a bit against that.
For small datagrids it doesn't matter "traffic-wise", but for big ones it is
more information to transfer, more structures for the browser to deal with,
more details depending on what we're doing at the DOM tree, etc.
Actually, it seems to me that there are more places that classes and
ids need to be applied wrt widgets. e.g. label fields don't get an id.
They don't.
What if I want to hide a text field and its label, and then only
display them depending upon what a user selects in another form field?
You'd have to wrap then on a DIV or SPAN with an ID and hide those. There's
another problem here: depending if you're using a form widget (either listform
or tableform) you'd have to adopt a different approach.
Here using sibling nodes and parent/child nodes on the JavaScript makes the
job easier.
It's easy enough to hide/display the textfield. But not the label that
goes with it.
This can be done with more elaborate JavaScript (and asking for sibling nodes
of the field you're going to hide), without any change on the actual widgets.
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
