You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by worookie <wo...@hotmail.com> on 2003/06/18 01:50:11 UTC

what is the purpose of the Shell component

I have two page components (Registration and Confirmation). The Registration
page uses the Shell component in its html template; the other page
(Confirmation) doesn't. Both html templates have the stylesheet link tag in
their html templates as follows:

......
<link rel="stylesheet" type="text/css" href="css/RegApp.css">
......

The Registration page that uses the Shell component has the following extra
declaration:

Registration.html:
......
<span jwcid="@Shell" title="Registration"
stylesheet="ognl:assets.stylesheet">
......

and

Registration.page:
......
<context-asset name="stylesheet" path="css/RegApp.css"/>
......

Although the Registration page has more declarations than the Confirmation
page has, they both work just fine. So, my question is why we need the Shell
component?

Also, referring to: "http://jakarta.apache.org/tapestry/doc_frame.html ->
Shell", we also need to use a <span jwcid="$content$"> around the actual
body content. I don't understand why we need to do this? My sample page
works just fine without the $content$ stuff. So, when is $content$ really
needed?

I am using Tapestry 3.0 beta.

Thanks in advance for your explanation.

Regards,

Rookie

Re: what is the purpose of the Shell component

Posted by worookie <wo...@hotmail.com>.
> Also, referring to: "http://jakarta.apache.org/tapestry/doc_frame.html ->
> Shell", we also need to use a <span jwcid="$content$"> around the actual

Correction: the link should be:
http://jakarta.apache.org/tapestry/doc_frame.html -> Tapestry Component
Reference -> Shell

> body content. I don't understand why we need to do this? My sample page
> works just fine without the $content$ stuff. So, when is $content$ really
> needed?