Hi Jack and all the Ext Community,
Firstable, congratulations for your great work.
Now a question. Is there any plan for autocomplete text form fields?
Kind regards,
Fernando
Firstable, congratulations for your great work.
Now a question. Is there any plan for autocomplete text form fields?
Kind regards,
Fernando

#2
![]() |
![]() This would be HOT!!
![]() |
#3
![]() |
![]() More specifically, I would like to add dinamically (by javascript) autocomplete behaviour to certain (selected by class) text fields of a form created by simple HTML markup in the server side (JSP).
Fernando ![]() |
#4
![]() |
![]() Jack,
We would also like to have a control like this. In fact you may recall you helped us to implement such a beast based on the YUI AutoComplete back in December. Our requirements may be slightly different from Fernando's. Specifically, we want to:
Thanks, Gordon p.s. I've got a read-only grid largely working with Ext 1.0. Now for the editable version! ![]() |
#5
![]() |
![]() That's fantastic Gordon. I'm glad to hear it.
I have question for you guys. How would you feel if the AC required a data store for loading? This way it supported all of the options (http, in memory, xml, json, array, etc) and added support for complex types (which I know you need Gordon). Obviously implementing a store is a little more long winded than implementing a simple json loader - but imagine how much power there could be. If the store is ok, then it makes it easier for me. Let me know what you guys think. ![]() |
#6
![]() | |
![]() Quote:
Another question, Will it be possible to provide AC behaviour to a text field previously created by HTML markup? Thanks in advance Jack. "Un admirador" of your work. Fernando. ![]() |
#7
![]() |
![]() I definitely agree that a data store is the most desirable solution.
![]() |
#8
![]() |
![]() I'd like to add that I think it'd be nice if the autocomplete results were just a simple grid component so there was client-side sorting, column resizing (maybe), etc. It *might* be handy if it supported paging as well.
![]() |
#9
![]() |
![]() As someone who went through the pain of implementing an autocomplete based of yui a while ago (without ext), I'll vote for this- and for the datastore option. There are so many parts where having this in Ext makes sense since a lot of it is built already. My own implementation took a lot of time, which was part rendering bugs and positioning.
The options I would like to see: 1. the templating of the return html / the same fantastic themeing we see in other ext items. 2. configurable time delay after last keypress before sending the request. 3. configurable max number of displayable results 4. shim so it works over select 5. effects configuration, (how it renders and destroys) sounds like a lot, but considering how much low-level stuff Ext has taken care of already, it should be not so bad at all. ![]() |
#10
![]() | |
![]() Quote:
![]() |