Hi Adam! > That is possible, although it gets pretty tricky in anything but the > simple cases. Part of the problem is that your decorator is acting on a > function before it is bound to the class, so you can't really look up > what the function belongs to. At least that is what I think I ran into. > The real problem is that, say you have a heirarchy like this:
I understand, and there is no way to configure this without pass an argument to the decorator (at least I don't find any method or attribute on the func argument :D), and this way we aren't saving typing... > Anyways, this should do it for you if you are still interested. I > didn't have much time to test it, just to confirm that it provides the > expected behavior. If it breaks any of the other features of expose I > would not be suprised. Hum, it seems to work ok, but in a flat hierachy :), the name clashing is inevitable. Thanks for your code, this helped me to understand how to make a custom expose method. I think I need to dig up more deeper to understand the way to work with turbogears. In webware world I work with servlets, object orientation and inheritance. Thanks for all help! -- Michel Thadeu Sabchuk Curitiba - Brasil --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
