On Monday 06 April 2009 05:41:59 chris_g wrote: > Hi, > > I am following the example for TurboGears 1.0 Unified Form Data > Validation : > > http://docs.turbogears.org/1.0/UnifiedControllers
Which is a rather uninformed and heavily opinionated recipe - to say the least. The 6 reasons given for adopting it are mostly nonsense - and the resulting code is nothing more readable or anything. Instead it goes against what the usual practice of creating form-pageflows is in TG. For example, """You can't use dynamically created forms - the form has to be created ahead of time to be passed to the @validate decorator.""" is either an outright lie, or the poster has no deeper knowledge of TG and thus doesn't know that it's perfectly fine to pass a callable to @validate-decorator so that you can choose or create a form based on runtime-criteria. >From your post I have troubles seeing what the dynamicity is you require and if there isn't a better way to work with that. Maybe if you could elaborate on that, we could provide better help. Diez --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
