On Sep 24, 2006, at 11:18 AM, Alberto Valverde wrote: > I'd rather "fix" this without using request-scoped storage altogether > as I believe it would simplify the code in a great deal (let's see if > it's true once I get my hands dirty on it) and achieve better > performance (this storage is accessed many times when rendering a > form).
My view is this... if TG users are *always* passing the same thing to display(), then they shouldn't have to pass that. better to have a little complexity in TG than a lot of extra work on the part of the users. I agree that the path stuff is complex and if that can be simplified I'm all for that, as long as the user API remains easy. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk -~----------~----~----~----~------~----~------~--~---
