> But you create a new class and instance on each request. > > This might lead to memory leaks. >
yes, but ... the script parameter (that is where this widget should submit its data) is dynamic in my specific use case, and can't be determine before entering the controller. That's why I needed to implement this way. on the other, you must be right in that it is a bad example. If anyone uses this widget in a more academic way, I'll be happy to change my doc example. (I might very well have the need myself soon), but we're a community right? ;) thanks for the comment NiL -- 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.
