Stability and consistency is paramount in a good framework - delete.
Jonathan Locke wrote: > > > Our Wiki describes the wicket:component tag as follows: > > "<wicket:component> - Creates a Wicket component on the fly. Needs a class > attribute. Though this has been in wicket for a long time, it is still > kind of an unsupported feature, as most of the core developers believe > that this may lead to misuse of the framework. Before heavily relying on > this feature, you might want to contact the user list to discuss > alternative strategies." > > It's unclear to me that anyone is using this. The utility is limited and > unimportant. And for anyone creating tooling support for wicket, this > will be a tripping point. I can't see any good reason to keep this > feature as it is a way to instantiate a component in the markup and might > server as the beginning of a bunch of requests to add component > configuration or other code logic where we should only have nice clean > markup. > > VOTE: > > [ ] Delete this unimportant and generally unsupported feature > [ ] Keep <wicket:component>, but define its limits, document it on the > wiki as fully supported and commit to supporting it in the future > > > > -- View this message in context: http://www.nabble.com/VOTE-on-wicket%3Acomponent-tf3221780.html#a8967701 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
