I started to use wicket some time ago, and I'm really enjoying it. Best framework ever. But I've some suggestions. I think wicket could be better if it had less boiler plate code. This could be reduced by using CoC. Take the FeedBackPanel for example, you always have to add the component on the web page, even if no special handling is requires (which is almost the case). Wicket could have some reserved ids, so if I add a markup with id feedbackPanel, a feedbackpanel component is automatically added to that page. Another example is SubmitLink component. No special handling required, but for wicket sake the developer must add it on the java the page. -- View this message in context: http://www.nabble.com/Wicket-and-CoC-tp20706881p20706881.html Sent from the Wicket - User mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
