Re: Re: [PEPr] Comment on HTML::HTML_QuickForm_advmultiselect

On 6/14/05, Philippe Jausions <Philippe.Jausions@11abacus.com> wrote: > Laurent Laville wrote: > > > Manage three lists or more seems to me a bit too complex, and i don't > > think it's cases you, or i , should be process > > each days ! > > Agreed, but not that unrealistic. > > BTW: you are in fact already managing 3 select lists ;-p > > > Split the list of values into 2 main lists "selected" and "unselected" > > is the main goal of advmultiselect. > > > > Of course a simple multiple-select is enough if we consider to split a > > list on 2: selection and remainder. > > But in real world, lot of end-user don't know that to select mutiple > > occurs, they have to click on CTRL key when > > they do their selection, item by item. Two lists with add and remove > > buttons solve this main problem. > > > > For examples you told to me, did you have to solve such problem often > > ? i don't think so, but perharps i'm wrong ! > > Could we have others opinion from anybody else please ? > > My main concern, is the way you implemented the element doesn't leave > room for expansion. Using a hidden select is a no-go to me. It > complicates things, it is not really necessary, and it isn't easily made > compatible with JS-impaired web browsers (possibly PDAs and smartphones, > and security freaks) > Sure it is. As has been said before, you use CSS to hide the two which are the "selected" and "unselected" selects and show the normal one. Then use JS to hide the original and show the two new ones. Done, easy. Of course this doesn't help for CSS-impaired browsers but that can easily be fixed with a bit more JS. -- Justin Patrin