[news.eclipse.webtools.jsf] Re: enable design time only css external res

[ian.trimble@xxxxxxxxxx (Ian Trimble)]

Eclipsian (if that is, in fact, your real name :) ),

We're currently looking at requirements for supporting "skinning" (such as 
Trinidad allows) at design-time. One requirement will be the ability to 
somehow register one or more stylesheets and image sets (i.e. "skins"), 
and ultimately select any one at any time. This feature will need to 
provide some method to specify design-time CSS, which may be the solution 
your are looking for. But, I suspect you're looking for an 
already-existing solution, and frankly, I can't see one right now. If you 
do find a solution, please share your experience here - it may just be 
what is required for skinning support.

- Ian

Eclipsian wrote:

> External css can be enabled by link tag as normal HTML. But for custom 
> components, their default css resources are packed in jar file and they 
> can be accessed in component renderer. So even there is no link tag in 
> faces page to define external css, the renderers have problem to render 
> component in runtime. But for Web Page Designer, they cannot be resolved 
>   unless you have link tag and have those css resources copied in web 
> root. If I create a plugin bundled with those css resources, how can I 
> manipulate design time dom via an (?) extension point. Or if there is 
> better solution?

> Thanks ahead.