>>Have you tried implementing that as another mixin, say NiceAutcomplete,
subclassing from Autocomplete?

I considered that approach, however it seemed that I would need to modify
the autocomplete javascript in order to insert an element to contain the
greyed out text, which would then pose even more challenges with regard to
making sure it was all visually consistent when designers start adding CSS.
I'm doing my best to avoid re-writing the jQuery stuff, that's why I took
the approach of stacking text fields and wiring it together. However this
is proving to be yet another challenge as far as making it all behave
exactly the way it should.


On Wed, May 22, 2013 at 12:30 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:

> 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-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org>
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Reply via email to