I'm not sure the whole of Iscript support is needed. One of the primary
reasons for the @Script component is so that Tapestry generated id's can be
used in a JavaScript. Is that really needed for CSS?

Richard 

-----Original Message-----
From: Fernando Padilla [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 26, 2005 4:17 PM
To: Tapestry users
Subject: Re: Questions about Components and StyleSheets

Could someone with more time and hunger just spend a week to duplicate
and adapt the IScript support for stylesheets?  It's a minor oversight
to not have done it from the beginning, but I think it's time to bring
this kind of support into the core Tapestry.

It seems possible, or am I missing something.  It looks to be the same
ideas as the IScript support, just IStyle, and instead of the @Body
injecting javascript, the @Shell would inject css into the head.

but then again, I could just be naive.


Hensley, Richard wrote:
> Patrick,
> 
> I used a little trick where I have my shell use a delegate that searches
for
> stylesheet assets with special names.
> 
> Here is the article I wrote a while ago:
> 
> http://article.gmane.org/gmane.comp.java.tapestry.user/16092
> 
> This makes it as simple as putting an asset declarations in your
component.
> 
> Richard 
> 
> -----Original Message-----
> From: Patrick Casey [mailto:[EMAIL PROTECTED] 
> Sent: Friday, August 26, 2005 3:38 PM
> To: 'Tapestry users'
> Subject: Questions about Components and StyleSheets
> 
>  
> 
>             What's the textbook/preferred/whatever way that a component
> gets
> its CSS onto a page? So far as I can tell, I can:
> 
>  
> 
>             Put it in a @Shell component, but that Shell only takes one
> CSS,
> so if a page requires > 1 css file, the shell doesn't work, does it?
> 
>             Manually link them in via any tags, which seems to work for
> me.
> 
>             Manually add a <script></script> block to your .html file
> and
> cut/paste the css in.
> 
>             Cut/Paste all component styles into one "master" CSS file
> and
> then link that one file via the @Shell.
> 
>  
> 
>             All of these approaches though require that the programmer
> (that's me), not only embed the component on the page, but also use one
> of
> the aforementioned methods to embed that components .css as well
> (assuming
> the component like contrib.:Palette uses its own CSS). 
> 
>  
> 
>             Is there a way I can set up my page such that the component
> can
> embed its own css? Or is using a component that has its own css always
> going
> to be a two step process?
> 
>  
> 
>             --- Pat
> 
>  
> 
>             PS Tapestry 3.0.3.
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to