Thank for your post. initHead() will be very helpful here. I have voted for this issue.
-- Daniel On Fri, May 30, 2008 at 9:23 AM, Roland Huss <[EMAIL PROTECTED]> wrote: > > Hi Daniel, > > > Daniel Stoch-2 wrote: >> >> The main >> problem is that the AutoCompleteTextField and related classes >> (behavior, renderer) are not easily to extend (eg. it is necessary to >> make a few modifications in wicket-autocomplete.js but in >> AbstractAutoCompleteBehavior the standard js is added in renderHead >> method, so there is no way to replace it, etc.). So I must made a copy >> of these standard classes and then made modifications in them. >> > > I had the same problem with extending AbstractAutoCompleteBehavior while > working on wicketstuff-objectautocomplete and I already > opened a Jira issue for that. You might want to vote for > https://issues.apache.org/jira/browse/WICKET-1651 which provides a patch for > putting AACB's renderHead() logic into a protected initHead() method, which > then > can be overwritten by a subclass and AACB.super.renderHead() is still > called. > > ...roland > -- > View this message in context: > http://www.nabble.com/AutoCompleteTextField---autocomplete-multiple-fields-tp17500271p17553097.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
