Hi, The idea is to have a common State class, defined in something like > turbogears.state and one can define the variable needed by subclassing > State (not tested):
This makes some sense to me. I have a few pages that are user-definable views, that remember their settings. These need to: 1) Load values from cookie or URL, with URL taking precendence 2) Set the cookie when URL parameters change settings I've thought it would be neat to have the framework handle this, and I think your suggestion would cover this. Still, I guess this isn't the highest-priority feature - it's pretty easy to roll your own. Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
