On 6/14/07, Leonardo Uribe <[EMAIL PROTECTED]> wrote:
Yes, the Trinidad Agent code detects IE and do other things.
I'm not an expert, but actually I'm working in
use trinidad css capabilities to non trinidad components.
There are some points to consider first:
1. If you want to do a component for trinidad, you can take full advantage
of trinidad capabilities,
but you have to write this component with the rules of trinidad (for create
components that inherit form
UIXComponentBase and renderers that extends from XhtmlRenderer or
CoreRenderer, use FacesBean
to get attributes from components, and other stuff).
No, not really. For skinning, you can definitely use an ordinary
renderer, extend from UIComponentBase.
What *is* true is that the code that boots up skinning is
the CoreRenderKit and the Trinidad ViewHandlerImpl, in addition
to the trh:styleSheet component (which is automatically
rendered by both trh:head and tr:document).
The problem is when you
want to mix this component
with basic html components (Ex: <h:outputText/>). Instead, you have to use
the trinidad counterpart components (<tr:outputText/>).
That's not true at all. You can use h:outputText, etc. etc. You
can use h:form instead of tr:form. And so forth. All of the spec
tags work fine with Trinidad. Tomahawk components also generally
should work with Trinidad, though there I believe there are some
incompatibilities that we can more aggressively target now that
Trinidad is out of the incubator.
-- Adam
You can put your custom css code in a custom skin file like this:
@agent ie
{
/* Here put css code for ie */
af|panelBox::header
{
text-overflow: ellipsis;
}
/*......*/
}
2. If you want to do a component for tomahawk sandbox, then I found a
workaroud to add trinidad
capabilities and use it with non trinidad components. It's a work in
progress, but I think you can use
this with minimal efford. I'm not probe its agent capabilities, but I
believe that this should work (I want
to probe this too).
Leonardo Uribe
