On 9/28/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > Well, let me put *my* pragmatic hat on, and state that we better ship > > our final release, instead of playing super hero and fix bugs in other > > frameworks by applying workarounds in our code. > > Imho, that's pragmatic when it comes to our project management, not > when it comes to fixing problems users have.
This particular problem lies with JQuery and other JS frameworks. There are enough problems our users have with Wicket internal bugs before we need to make the rest of the world a better place. And shipping the damned release *IS* important and *VERY* necessary, or are we forgetting that we have still several users on a particular branch with a constructor change and generics? So instead of working around a couple of javascript frameworks' bugs we could fix bugs in our code. Martijn -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
