with the approach I mentioned, you wouldn't be forced as
<wicket:extend> is removed by default. I think that answer all your
remaining point as well, correct?
I didn't mean that it was a chore to strip away <wicket:extend> tags. I
meant that we don't *want* to do it.
In my view, the entire point of debug mode is that you should be able
to see *all* the tags. Now you're telling me that if I choose to enable
this behavior (don't strip away wicket:extend) then suddenly my page
will render different from production mode. That is the fundamental
problem here... stripping the tags by default is pretending the problem
does not exist instead of actually.
Instead of taking this approach maybe we can do the opposite: add a
setOverrideDoctype() method. Thinking out loud, here is what I had in mind:
- To my knowledge, doctype is the only tag we can't wrap with <wicket>
tags. All other tags may be wrapped and the browser will ignore them
with no loss of previewability.
- We can define <wicket:extend> like <wicket:border> -- that is, it
wraps the *body* of the page we want to inject, not the entire page.
This means that doctype does not belong inside <wicket:extend>.
- When the user sets setOverrideDoctype() the doctype from the extending
document clobbers the one in the parent document.
I think more-often-than-not you do not want to override the parent
doctype and furthermore when one extends a page, you mean to extend its
body not its metadata information.
Here is an example from an online shop I am building...
I might have a parent page CustomizeProduct.html that is viewed when
the user chooses a product to order and wishes to specify its size,
color, etc...
I then extend this page with say CustomizeMug.html,
CustomizeShirt.html, etc... which injects HTML into the body of the
parent HTML specific to the product being sold. Regardless of the
product being sold, I expect the same page header, colors, and maybe
even meta-keywords. The only thing being modified is the image used and
the kind of options you might have. For example, if you order a Mug
you'd have "small, large" as an option. If you order a poster, you will
have many possible dimensions to order from. If you order a cup, you
might have the ability to choose it's color, etc...
What do you think?
Gili
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
