You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "hv @ Fashion Content" <in...@fashioncontent.com> on 2006/06/17 20:58:53 UTC

Shell Component & JavaScript

Have anyone thought about supporting classic JavaScript include statements 
in the <head> when using the Shell component in Tap 4.0/5.0 ?

I wouldn't mind doing some work on supporting it, but I am not quite sure 
how it would be done best.

<html jwcid="@Shell" script="js/script.js">
<head jwcid="$remove$">
 ...
</head>
<body jwcid="@Body">
...

Would work nicely, but only support a single script file

<html jwcid="@Shell" script="js/script.js">
<head jwcid="@ShellAdditions">
<meta jwcid="$remove$" http-equiv="Content-Type" content="text/html; 
charset=utf-8" />

<link jwcid="$remove$" rel="stylesheet" type="text/css" 
href="css/full.css"/>

<link rel="stylesheet" type="text/css" href="css/additional.css"/>
<script src="script/prototype.js" type="text/javascript"></script>

 ...
</head>
<body jwcid="@Body">
...

Would allow the html to look and work nearly the same wether loaded from 
server or from file, but would require the Shell to one more buffering 
writer like the Body tag.

I would also imagine defining global links in the .application file.

Any thoughts ?

Henrik 




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Shell Component & JavaScript

Posted by Jesse Kuhnert <jk...@gmail.com>.
The @Shell component supports a "delegate" parameter, which will allow you
to render anything you want.

On 6/17/06, hv @ Fashion Content <in...@fashioncontent.com> wrote:
>
> Have anyone thought about supporting classic JavaScript include statements
> in the <head> when using the Shell component in Tap 4.0/5.0 ?
>
> I wouldn't mind doing some work on supporting it, but I am not quite sure
> how it would be done best.
>
> <html jwcid="@Shell" script="js/script.js">
> <head jwcid="$remove$">
> ...
> </head>
> <body jwcid="@Body">
> ...
>
> Would work nicely, but only support a single script file
>
> <html jwcid="@Shell" script="js/script.js">
> <head jwcid="@ShellAdditions">
> <meta jwcid="$remove$" http-equiv="Content-Type" content="text/html;
> charset=utf-8" />
>
> <link jwcid="$remove$" rel="stylesheet" type="text/css"
> href="css/full.css"/>
>
> <link rel="stylesheet" type="text/css" href="css/additional.css"/>
> <script src="script/prototype.js" type="text/javascript"></script>
>
> ...
> </head>
> <body jwcid="@Body">
> ...
>
> Would allow the html to look and work nearly the same wether loaded from
> server or from file, but would require the Shell to one more buffering
> writer like the Body tag.
>
> I would also imagine defining global links in the .application file.
>
> Any thoughts ?
>
> Henrik
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Jesse Kuhnert
Tacos/Tapestry, team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.