oeps..
already done... (had to refactor the constructors anyway...)
Eelco Hillenius wrote:
As the implementation of AbstractChoice (and all classes that descend
from it) rely to at least some extend/ some situations on the index of
a options in a given choice collection, I think choices should really
be a List, as that is the only way we can guarantee order. I further
think it wouldn't be a large problem for users even if they would like
to use e.g. Sets, as they can simply wrap them in List implementations
or use the Collections class for this.
Agreed?
Eelco
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar
happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted
by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
