Hi!
Sorry for the lenghty mail.
I would like to get rid of the ExtensionFilter when it comes to buffer
and parse the response.
Now there are a couple of methods how to archive this:
1) documentTag
Having something like
f:view
t:document
t:documentHead
/t:documentHead
I believe that the problem is that
the panelLayout and HTML is incompatible
in HTML you have HTML, HEAD, BODY
in panelLayout you have HTML, HEAD, BODY, FOOT (ok, you get my point ;)
So in fact, the panelLayout is wrong, wrong, wrong.
regards,
Martin
On 2/27/06, Mario Ivankovits [EMAIL
Martin Marinschek schrieb:
in panelLayout you have HTML, HEAD, BODY, FOOT (ok, you get my point ;)
Yes, this is why I put a inc/header.jsp (and footer for sure) outside of
panelLayout.
So I have a header/footer for the content outside of BODY (but for sure,
including the body) and use
I think we might end up wanting both - the document based approach,
_and_ your scripts-tag.
what do you think?
maybe we should start off with the scripts tag, and then add document
tags as we go?
regards,
Martin
On 2/27/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Martin Marinschek schrieb:
Hi!
I think we might end up wanting both - the document based approach,
_and_ your scripts-tag.
What if we implement the state attribute, but having the state optional.
So these tags can work with both scenarios.
We should only make sure, that no one tries to instrument the children
in one
o-k.
let's do it like this!
+1
regards,
Martin
On 2/27/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
I think we might end up wanting both - the document based approach,
_and_ your scripts-tag.
What if we implement the state attribute, but having the state optional.
So these tags
