I can't find the message that contained the link to the most current version. Can you send that again (I see the one on your website isn't the most up-to-date).
On 5/17/07 3:05 PM, "Jörn Zaefferer" <[EMAIL PROTECTED]> wrote: > > Hi Brian and Shelane, > > the quietness isn't really a bad thing. Most of the stuff that we got > requests for has been implemented. And those that come in more slowly > give us the foundation for further improvments that need more time. In > the meantime I've been heavily busy with other stuff, and I've also > released a new version of the validation plugin. >> I'm essentially trying to replicate a "combobox". >> > Ext's combobox widget is a nice reference. It seems to do all you need, > though you'd have to live with a 150k+ overhead. Please take at least a > look at it and let me know if that is close to what you need. I'm sure > we can get it working with less pounds of code. >> I'm almost certainly going to use a fairly limited set of local data. Not >> that I want to rule remote data out, mind you. Basically, I want a >> "pulldown" control that will show the entire list (preferably with >> scrolling, which I think is not presently implemented). Then, the user >> can click on the option that they want. Or, if they start typing into the >> input, they get the normal autocomplete behavior - except that the >> non-selected choices are still clickable, and the first close match is >> auto-selected. And, the user must be able to enter a value that isn't one >> of the choices. >> > Scrolling was on our todo list anyway. Adding a clickable button > shouldn't be too hard either, and thats it, isn't it? >> It's amazing how many widgets out there have gotten *close* to what I >> need, without actually arriving there. :) If I had a good enough grasp >> of how the plugin currently works, I'd take a whack at it myself. It's >> *so* almost there! >> > It would help a lot if you could provide a patch that adds the button > (using a nice graphic?) and a click-event-handler. The positioning of > the button would be the more serious issue to me. > > Any investigations on how to implement scrolling would help a lot, too. > Setting a height and overflow-y: auto doesn't do the trick yet, because > the list has to scroll also when using the keyboard. That was what > stopped my first naive two-minute approach to tackle scrolling.
