Certainly! How high do you deem the 'break risk' for this change? Big enough to put it in 1.2. (the initial plan), or is it that robust that we might put it in 1.1? The latter could help enormously in our marketing push.
Eelco On 10/22/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > One of the reqs around for ajax was to be able to re-render on > component rather than page level. I've got a working draft for that on > my laptop which require minimal changes to wicket-core only and does > not modify wickets current api, except that it is extended by one > public (but not for user use) method. Is that of any interest for > someone? > > Juergen > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
