I think this would be of interest but some security features would have to be in place.
I'm building a little component library of my own, and the Autocompleter shold indeed be extended witch I plan to do.
I think a MaxResults is very handy. Is this situation there would be no problem with result size. It would be truncated to the MaxResults.
Also a MinSearchCharacters would be helpfull. In say a large client list finding something with the letter "a" would probably return 90% of the results. Normally someone trying to select a record types at least 2 or 3 characters and this way a large and not needed search would be avoided.
The MaxResults could be added in the listener.
The button you mention, could also be improvised by invoking the JS that the onChange is associated to.
The MinSearchCharacters would also mean intercepting the OnChange or providing our own.
I will look into this soon. If someone does not post some light here I could post what I can find here later on.
I'm not an experienced Tapestry developer, but have been building components for some weeks now so I'll try.
On 5/1/06, Chris Chiappone <[EMAIL PROTECTED]> wrote:
The reason I would like to have a button show the full list is if the user wants to know all of the possibilities in the selection list without having to type anything. Does that make sense?
On 5/1/06, Chris Chiappone <[EMAIL PROTECTED]> wrote:One other question I had is that I notice if the autocompete is wrapped in a conditional it doesn't seem to work. Have others experienced this?On 5/1/06, Chris Chiappone <[EMAIL PROTECTED]> wrote:I have been using the Tacos autocompter with success for some time now and wanted to know how I could add functionality. What I basically want is the ability to press a button next to the textfield that would autofill all values in the completion list. Would this be something easy to implement? Any thoughts or advice would be great. Thanks
--~chris--~chris
--~chris
--
Pedro Viegas
