Thanks. It works great. I'm not sure it suits my case, though.

El Ven, 11-11-2005 a las 12:08 -0100, Ron Piterman escribió:
> If browser compatibility of IE >= 6.0 is not an issue, you can use 
> scriptaculous's autocomplete (which is the one used by tacos).
> 
> 
 <ציטוט Pedro Abelleira Seco:
> > Our problem is that we have to go to production with 3.0.3, so tacos is
> > not an option
> > 
> > But I'm going to take a look at dojotoolkit. Thank you very much
> > 
> > El Ven, 11-11-2005 a las 11:26 +0100, Norbert Sándor escribió:
> > 
> >>- http://archive.dojotoolkit.org/nightly/tests/widget/test_ComboBox.html
> >>- I think tacos's Autocompleter does something similar (although I haven't 
> >>used it yet)
> >>
> >>BR,
> >>Norbi
> >>
> >>----- Original Message ----- 
> >>From: "Pedro Abelleira Seco" <[EMAIL PROTECTED]>
> >>To: "Tapestry users" <[email protected]>
> >>Sent: Friday, November 11, 2005 8:29 AM
> >>Subject: Editable combobox
> >>
> >>
> >>
> >>>Hi all!
> >>>
> >>>We are developing an intranet application for an institution and we have
> >>>developed some components. Most of them are not reutilizable outside our
> >>>application (because them are targeted to the app business logic or have
> >>>to wait to some refactoring to be separable from the rest.) So far we
> >>>have only contributed one component to Tassel.
> >>>
> >>>Now we would like to have new component. We can develop it, but perhaps
> >>>they already exist or there is some javascript code to start with.
> >>>
> >>>The component would be a writeable combo. Our users like typing codes
> >>>(because most of the time they know them) but it's good to have a combo
> >>>to choose among the possible values for ocasional users. The problem
> >>>with HTML is that it lacks the possibility of typing into the combo (yes
> >>>browsers position the value and that, but it's not really usable).
> >>>
> >>>We would like to have a text entry with a button with a down arrow. You
> >>>could type text inside (autcompletion would be a bonus, of course, but
> >>>not required) and, if you don't remember the value be able to press the
> >>>button and get a list of values (ideally in two columns: code,
> >>>description). An editable combobox, that is.
> >>>
> >>>Has anybody done something similar? Does anybody think this would be a
> >>>bad solution? I suppose that those of you who are doing web based
> >>>business apps have this kind of problem. Usability of webapps sucks, but
> >>>with things like this we could improve a bit the situation.
> >>>
> >>>If we find something to begin with we could meet our deadline. We would
> >>>contribute back this component, of course.
> >>>
> >>>Thanks in advance.
> >>>
> >>>Pedro Abelleira Seco
> >>>
> >>>
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to