Martijn Dashorst schrieb:
 - constructor refactor

Wow, that's a /major/ change and will probably effect every custom component and every application written using Wicket.

I see the benefit of having a complete component hierarchy availably right at the initialization of a class.

But wouldn't it suffice to just make the new constructors available, and put a clear statement in the API docs? Then maybe deprecate the public add() in the next major version, and drop it in 2.0 or something like that?


        This opens up a lot of better markup parsing strategies for the
        core.

Just get rid of markup, it sucks anyway ;)


 - java 5 support

+1






-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to