we dont need to deprecate the existing one. it does something that object-autocomplete does not - lets you enter free-form-text with some assistance.
-igor On Tue, Jun 14, 2011 at 6:55 PM, Jeremy Thomerson <[email protected]> wrote: > I'd be up for at least moving the ObjectAutoComplete into core and adding > @Deprecated to the existing one before 1.5.0 if there is consensus on it. > > -- > Jeremy Thomerson > http://wickettraining.com > *Need a CMS for Wicket? Use Brix! http://brixcms.org* > > On Tue, Jun 14, 2011 at 11:27 AM, James Carman > <[email protected]>wrote: > >> On Tue, Jun 14, 2011 at 11:25 AM, Clint Checketts <[email protected]> >> wrote: >> > Is there a good reason (besides backwards compatiblity) that the >> > objectautocomplete hasn't replaced the broken string based one in >> > wicket-extensions? >> > >> > It seems like AutoComplete should behave as similarly to DropDownChoice >> as >> > possible. As it currently is, IChoiceRenderer feels broken with it. >> > >> >> I would think it should have at least made its way into the "core" or >> "extension" by now. There have been enough requests for it. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
