It comes close, yes, but on EyeOS we have more than 20 SearchFields and they
increase as you open more apps. So copy-paste this code will not solve the
problem, that's why I created a widget.
I don't want a composit, I need a widget with the same API and functionality
as the TextField, plus a clic
I think you are mixing OO inheritance with composition. You want to
create a composit, but still retain the API as if it were a child class
(which certainly is not what OO inheritance is about).
You might want to look at the implementation of the search field in the
Demobrowser. In demobrowser
Hi Tron, thanks for the response,
Yes, I did it this way because I found no other way to do it. But you think
it's ok to have to wrap (this is create a *getValue* method to call the *
TextField* *getValue* method) all *TextField* methods? There are so many,
why I have to create so many dummy metho
On 10/04/2011 05:50 PM, Seldaiendil D. Flourite wrote:
Hi all,
Time ago I tried to inherit from *qx.ui.form.TextField* to create a
search field with the magnifier icon. The DOM structure I wanted was
like this:
- Container DIV
- Decorator
- Content DIV
- TextF
>
> Hi all,
Time ago I tried to inherit from *qx.ui.form.TextField* to create a search
field with the magnifier icon. The DOM structure I wanted was like this:
- Container DIV
> - Decorator
> - Content DIV
> - TextField INPUT
> - Icon IMG
But it was impossible, *qx.ui.form.Abstract
