"Michele Cella" <[EMAIL PROTECTED]> writes: > 1) Removing the ignore_key_missing parameter from our Schema and tweak > thing so that this will work, since we don't let the Schema accept > missing fields the validation will be done by the widget validator and > if not_empty=True you will receive an error otherwise all should work > well.
+1 > 2) Hack our CheckBoxList (and MultipleSelectField) so that they use an > hidden field with the same name and value "tg_empty" then in > NestedFilter we walk c.p.params and search if this paramter is present > and alone, if it's the only one there we replace it with an empty > string '' otherwise we strip it out. > This feels really hackish to me and I would really like to avoid the > need for such a thing. -5 ;-) > The basic problem with 1) is that disabled_fields will not work > anymore, but is this such a big problem? do we really want to support > them if they will make other obvious and more common things not > behaving in the right way if not by using bad hacks? is someone using > disabled_fields? what use case is covered by them? I'm not using them. > PS > I will offline starting today until Monday. :-) have a nice weekend > guys. Nice weekend! Rest a little from all this TG work... ;-) -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
