Em Wednesday 06 February 2008 18:00:07 Christoph Zwerschke escreveu:
> Jorge Godoy schrieb:
> > It would be more interesting if this change was based on another
> > attribute or something like that... Having it on the name of the widget
> > might require too many changes on the code.
> >
> > What about, for example, some "auto=True" attribute instead?
>
> You mean, as an attribute to the default TextField? But that would blow
No. At your new widget... You created one, right?
> up the TextField too much, and we need to keep the old AutoCompleteField
> for compatibility anyway. And I think it's even easier and clearer to
> replace "TextField" with "AutoCompleteTextField".
Me too. I thought that you had somehow made that so that if I do:
my_widget = AutoCompleteTextField(...)
I'd get a TextField and if I did:
auto_my_widget = AutoCompleteTextField(...)
I'd get the auto complete behavior.
(...)
I agree with the names for classes you created.
> In the widget browser, the AutoCompleteField should do something that
> requires its additional functionality, so you understand why there are
> these two different flavors.
I use the hidden id so little that I can't even remember one case where it
helps me more than it annoys me...
--
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
-~----------~----~----~----~------~----~------~--~---
