Em Wednesday 09 January 2008 11:57:24 Christoph Zwerschke escreveu: > > But unfortunately, AutoCompleteField is a CompoundWidget, so it returns > a dictionary with two values. I.e. my validator does not fit any more, > my label does not fit any more (the id is different), and the data I get > back is now a dictionary with two values instead of a string.
It wasn't like that before, but then it changed so that you can have quicker access to the index of the information you are working with. > So I need to rewrite everything just to change a TextField to a > AutoCompleteField? Do I miss anything? This seems to be completely > awkward to me. I thought TurboGears should be easier. Unfortunately yes. You have to. This is one price to pay. You can also change the implementation of the AutoCompleteField and remove this. It isn't hard to do (and you can even get code from the subversion repository prior to that change, something like 14 or 15 months ago, IIRC). > The whole concept of nesting data of CompoundWidgets seems to be > completly awkward to me. Maybe there is something I don't understand? Is > this solved differently in ToscaWidgets? No. Both use the same basis: FormEncode. This is how FormEncode works. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
