Em Thursday 10 January 2008 07:48:04 Christoph Zwerschke escreveu: > > Ok, though I still not fully understand the use of this. It would have > been better to make this a separate widget or controlled by a parameter, > so you can replace a TextField with an AutoCompleteField and have this > additional functionality only when you really want it. If there are > other people who agree with me, I'll create a patch for this. Otherwise > I will just make my private AutoCompleteField.
A change that leaves the current behaviour as default and that disables the extra field with a switch would be less intrusive and break fewer applications now. This wouldn't help you on your migration because you'd have to add this switch to all your widgets (but it is easier than changing widgets and controllers, I admit). I believe that your use case is valid (my comment by the time was "what if I don't have an 'id' and just want to autocomplete on strings?") but with the above restriction... > Ah, right. I forgot about that. Somehow I cannot really make friends > with FormEncode. It's both the nesting and I'm sometimes also confused > about the direction and order of evaluation (from_python, to_python and > compound validators) - it's often the opposite of what I expect ;-) > Maybe it's because I haven't used it much and never systematically read > the documentation, though. Reading documentation *really* helps :-) And as boring as it is, it is better than trial and error programming. -- 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 -~----------~----~----~----~------~----~------~--~---
