On Apr 7, 1:01 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> Secondly, I sense a design-smell here. Most cases of dynamicsm should be > handleable by forms and schemas for validation - because the variance is > constrained by what you can save to your model, which isn't subject of > runtime-changes. > > If you'd disclose more of your actual use-case, we might be able to make > proper suggestions. There are two instances of "dynamism" that are there right now. 0. I need to be able to create a couple of fields based on the current user. ie. Retrieve some rows from my tables which are tied up with the user id. and populate the defaults for some fields from there. 1. I have some tables that serve as enums. I don't want to statically put them into my code since I want the whole thing to be controllable from a web based admin page. These tables contain valid values for various SingleSelect widgets. Please let me know if I'm not clear enough. Thanks for the help. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
