Tapestry isn't going to do anything to the HTML template 
automatically. 

What you want is something that previews reasonably, but 
still uses the Shell component.  How about:

Border.html:

<html>
<head> ....  </head>

<body>

<span jwcid="$content$">
<span jwcid="shell">
<span jwcid="body">

....  <span jwcid="insertWrapped"/> ....

</span> <!-- body -->
</span> <!-- shell -->
</span> <!-- $content$ -->

</body>
</html>

The special $content$ tag indicates that Tapestry should 
ignore anything outside the body of the tag.  Thus the 
<html> tags are there for WYSIWYG preview, but are 
removed at runtime, and the Shell component provides 
equivalent tags.

--
[EMAIL PROTECTED]

http://tapestry.sf.net
> Hi,
> 
> you did response, I just needed some time to check that out. In fact, it
> works, there is only one thing I do not like very much. When I add a
> Shell-component to my html-file (like <span jwcid="myShell"> <html>
> ...</html></span>) and I have already a <head> section in my html-file
> then on runtime, I see both css-links in the source code of my page. The
> one from the component and the one from my <head> section. I want to have
> it in the head section, because I like to edit my html document without
> having a servlet container running. What I do now is to remove the head
> section like <head jwcid="$remove$"> ...</head>. This works quite good,
> but couldn't this be done automatically?
> 
> Best regards and thank you,
> 
>   Christian
> 
> > In case I didn't respond to this from work.
> >
> > Use a Shell component to create the <html> and <head> portion of your
> > pages. It includes the necessary <base> tag to make things work properly
> > with the new (and I think, improved) URL format.
> >
> 
> 
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer

Reply via email to