On Wed, 22 May 2013 15:57:29 -0300, George Ludwig <georgelud...@gmail.com>
wrote:
@Thiago: The goal was not to apply a component as a mixin.
I'm sorry for misunderstanding you.
I'm working on a fancy AutocompleteTextfield class that acts like
Google's search text field, i.e. as you type, you get a greyed out
completion of the top result in the autocomplete list. If you open gmail
and type in to the
search field, you'll see exactly what I mean.
Interesting!
It works pretty good, but it still needs some tweaks, which is why I
asked the original question. It occurred to me that I may be able to
simplify the code if I could extend the existing Autocomplete mixin.
Perhpas it's a bad idea, but it was just a thought.
Have you tried implementing that as another mixin, say NiceAutcomplete,
subclassing from Autocomplete?
BTW, I believe I have permission to release this component as open source
once it's completed, so any help would be much appreciated :)
Yay! :)
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
