Is 1.4 even worth doing if we can't break the API? I thought we decided that the best way to do generics was to get rid of the "default" model and rethink that coupling. So, do we drop back and punt on 1.4? Or, do we just genericize IModel for 1.4? What's the plan, now?
On Fri, Jun 20, 2008 at 10:46 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > in 1.4 we are not supposed to break the api so much, so its waiting for 1.5 > > -igor > > On Fri, Jun 20, 2008 at 7:17 AM, Stefan Lindner <[EMAIL PROTECTED]> wrote: >> Wicket 2.0 had a Class called "wicket.ajax.ClientEvent" where all the >> event names like "onchange" where defined in an enum. This enum class >> was used as Parameter for e.g. the Constructor "new >> AjaxFormComponentUpdatingBehavior(ClientEvent.CHANGE)". >> Are there plans for implementing this in Wicket 1.4 again? >> >> Stefan >> >
