Alberto Valverde <[EMAIL PROTECTED]> writes: > However, if I just need the DOM id of the widget to initialize some > JS structure (like TinyMCE or SelectShuttle) does, I usually use the > "field_id" template variable to refer to it (instead of refering to > the container and looking for it's first child). However, as I've > mentioned many times already, one "limitation" (at least for my > liking) of widgets is that you can only access this variable inside > update_params or inside the template, which makes hard (IMO) to pass > this info around to "connect" different widgets.
This is a problem I was facing and that had to be creative (and count with your help) to solve. The alternative was passing a parameter at instantiation time that allowed me to inform something to the widget so that I can "find" it later. This something usually overrides the auto-generated id... It would be great if the widget id was also available as a class attribute from the widget... :-) -- 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 -~----------~----~----~----~------~----~------~--~---
