yep - the description was written for 5.0.13.
for 5.0.14 the approach is the same, but needs some adaption
i'll also update the page when i get the time.
c)hristian
Hi,
That page is not quite going to get you there. I'm actually working on
converting my site to XHTML, and so far I've had to modify a few
things here and there to make it work. But it's possible.
I'll post my findings to the wiki when I get the time.
-Filip
On 2008-09-01 15:28, Luther Baker wrote:
I have not!
If that's what I think it is - that is great! That's just what I was
looking
for.
-Luther
On Mon, Sep 1, 2008 at 1:03 AM, Carl Crowder <[EMAIL PROTECTED]>
wrote:
Have you already looked at
http://wiki.apache.org/tapestry/Tapestry5HowToXhtml ? (apologies if you
have :) )
Luther Baker wrote:
Is there a way to adjust the html that is generated - especially in
the
header?
Specifically, the generated head section does not appear to be xhtml
compliant.
Here is what I'm including in my own custom "wrapping" component:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
<html xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";
lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8"/>
<title>${pageTitle}</title>
<link rel="stylesheet" href="css/styles.css" type="text/css"/>
</head>
*A few points:
*
a) The xhtml strict DOCTYPE should be pretty straightforward
b) I want the Content-Type first in the <head> tag
c) The meta tag *MUST* have a closing slash - otherwise the
document is
not
well formed.
d) The same goes for the two <link tags. XHTML dictates that all tags
must
be well formed.
*Unfortunately, my application ends up generating
*
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
<html lang="en" xmlns="http://www.w3.org/1999/xhtml";>
<head>
<link href="assets/tapestry/5.0.14/default.css" rel="stylesheet"
type="text/css">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title>Home</title>
<link href="css/styles.css" rel="stylesheet" type="text/css">
</head>
For the most part - this is fine ... but in the details, I believe my
problem is two fold:
1) I would really like the "Content-Type" to be the first tag in head.
2) The link and meta tags are not properly closed. Unfortunately, this
code-gen is just not valid xhtml.
I do have one last (not so terrible) issue with the EXTRA <link tag
(tapestry specific css) that is showing up in the head as well. I'm
sure
it
is nice for exceptions (which the final user should never see) but
it has
a
few more problems:
1) It tells everyone what version of a particular library I am
using. I'd
rather not do that.
2) The tag appears before my Content-Type tag - which as I
mentioned, I'd
prefer FIRST in the hierarchy.
3) Finally, the tapestry stylesheet is not well formed. Again, proper
xhtml
demands that tags be balanced/closed.
I know Code Gen is hard -- but I generally pay extra attention to
ensure
I
produce valid, well formed xhtml documents and the codegen going on
behind
the scenes here is making that a bit hard.
Thoughts?
I'm not sure how to close the tags - maybe I can set a flag or pass
something else in as an xml attribute of the root tag of my templates?
Regarding the extra tapestry css file inserted ... maybe the Tapestry
library has a DEBUG and a RELEASE mode? Maybe there a flag to turn off
the
DEBUG mode and put this library into RELEASE mode? I really don't want
that
tapestry specfiic css page requested everytime I serve up a page. I
understand the filter takes care of it ... but it still shows up in my
request logs, on user pages, in proxies, etc ...
Is it even wise to consider opening up the tapestry JARs and see if
the
components implementeing this section of code can simply be tweaked to
have
proper xhtml balance.
On a positive note, the library is working well and I enjoy the
general
programming model. I think convention is great - but it needs to be
valid
in
this case. Thanks again in advance for any thoughts.
-Luther
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
