| enable design time only css external resource in page designer [message #476037] |
Tue, 21 October 2008 21:57  |
Eclipse User |
|
|
|
Originally posted by: Eclipsian.eclipsian.oti
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.
|
|
|
| Re: enable design time only css external resource in page designer [message #476038 is a reply to message #476037] |
Tue, 21 October 2008 21:59  |
| Eclipse User |
|
|
|
Originally posted by: Eclipsian.eclipsian.oti
sorry!
typo:
> So even there is no link tag in faces page to define external css,
the > renderers have <no> problem to render component in runtime.
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.
|
|
|
| Re: enable design time only css external resource in page designer [message #476039 is a reply to message #476037] |
Thu, 23 October 2008 17:55 |
 Ian Trimble
Messages: 137
Registered: July 2009 |
Senior Member |
|
|
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.
|
|
|
| Re: enable design time only css external resource in page designer [message #618567 is a reply to message #476037] |
Tue, 21 October 2008 21:59 |
| Eclipse User |
|
|
|
Originally posted by: Eclipsian.eclipsian.oti
sorry!
typo:
> So even there is no link tag in faces page to define external css,
the > renderers have <no> problem to render component in runtime.
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.
|
|
|
| Re: enable design time only css external resource in page designer [message #618568 is a reply to message #476037] |
Thu, 23 October 2008 17:55 |
Ian Trimble
Messages: 137
Registered: July 2009 |
Senior Member |
|
|
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.
|
|
|
Powered by
FUDForum. Page generated in 0.04180 seconds
] 
Search
Help
Register
Login
Home
