I think in the very rare cases (I myself didn't come accross any yet)
where I would like to change the raw markup and for whatever reason
have no wicket component attached, IMO we can live with the workaround
provided.
Let me ask one questions:
why is it neccessary to remove the <table> and related tags if table
width="100%". Why does it work for 50% and 99.99% but not for 100%.
And what about 120% (in case if makes sense at all). May be you
component should just make sure that width is never exactly 100% but
99.99% or 100.01%.
given the amount of logic and the lack of need for i18n, i think it
would make more sense to put all these tags right in the java code.
there's nothing wrong with that. if there's more logic than html, in
some sense i think the component belongs on the java side. this is
certainly true of AbstractChoice and some of the form components.
Juergen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
