yeah, me too.
we could provide an option to convert <wicket> to whatever tag the user wants on rendering.
in fact, in most cases, they could be removed from the output. we could control that via setStripComponentTags or something in ApplicationSettings.
Juergen Donnerstag wrote:
I get more and more convinced that <wicket> is the right way to go.
But, which browsers (old one's) support xhtml? Or are we going to provide an option to remove wicket-tags from output (which is send to the browser) and convert the doctype to html.
Juergen
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
