not in 1.3 maybe in 1.4 (but i have to look at it more closely, i think this can result in more and more heavier stuff inside componets)
1.5 is fine then we can let it evolve in the milestone cycles johan On Tue, Mar 25, 2008 at 11:02 PM, Timo Rantalaiho <[EMAIL PROTECTED]> wrote: > Devs, > > Have you had time to think about this: > > https://issues.apache.org/jira/browse/WICKET-1312 > > Judging from the interest on this list and in issue > comments, there is demand for an event mechanism in Wicket. > Surely it needs to be developed further from this patch, but > you've got to start from somewhere. (And this is essentially > something that we've used for a few months now with good > results.) > > Would it be a good idea to include the current patch version > already in 1.3.3 (and thus in 1.4), or better let it brew > more? > > Pros: > > - some kind of event mechanism available for 1.3 / 1.4 users > > - possibility to gather feedback on the mechanism to be able > to make a better one in 1.5 without worrying about > breaking the API > > Cons: > > - more new code to maintain in 1.3 / 1.4 branch > > - if the API gets deprecated and/or changed dramatically in > 1.5, it makes sad users anyway (even if there is > "permission" to break the API) > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oy <URL: http://www.ri.fi/ > >
