Reread the thread. The result is roughly that <wicket:extend> will
disapear from the output.
About doctype, I think it's developer's responsibility to ensure that
the parent and child doctypes are the same.
I think special treatment of this would only bloat wicket, while not
introducing any really useful feature. IMHO the wicket core should aim
to stay as clean and simple as possible.
-Matej
Gili wrote:
Hi,
I never got feedback to my last comment on markup inheritance. Why
can't we simply ensure that all Pages along the markup inheritance use
the same doctype? As I explained in the email, when you think about it
it doesn't make much sense for the parent doctype to differ from the
child doctype hence this entire discussion about doctype and
<wicket:extend> is meaningless.
Can you please read my previous email in wicket-user and let me know
if you agree or disagree?
Thank you,
Gili
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
