I did it with a custom view handler via the Java API, I never bothered
with registering it.
org.apache.myfaces.trinidadinternal.ui.RendererFactoryImpl factory =
(org.apache.myfaces.trinidadinternal.ui.RendererFactoryImpl)org.apache.myfaces.trinidadinternal.ui.RendererManager
.getDefaultRendererManager()
.getFactory(
org.apache.myfaces.trinidadinternal.ui.UIConstants.MARLIN_NAMESPACE);
factory.registerRenderer(
org.apache.myfaces.trinidadinternal.ui.UIConstants.SUB_TAB_BAR_NAME,
new SubTabBarRenderer());
On 10/9/07, Cristi Toth <[EMAIL PROTECTED]> wrote:
> Hi Andrew!
>
> Sounds good, but can you tell me how can I override the default
> SubTabBarRenderer?
> I have no idea where the mapping is done for 'sub renderers' from the uix/ui
> packages.
> I hope this can be done without me needing to overwrite the default renderer
> in the trinidad sources and build them myself.
>
> thanks
>
>
> On 10/8/07, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> > I have submitted such an issue that keeps the existing tabs and adds
> > the new ones. This way it is backwards compatible.
> >
> > https://issues.apache.org/jira/browse/TRINIDAD-632
> >
> > On 10/8/07, Cristi Toth <[EMAIL PROTECTED]> wrote:
> > > Hi!
> > >
> > > The skinning of the pannelTabbed component could be improved
> > > so that it can have round cornered tabs (like in most of the
> applications),
> > > similar to navigationPanel with hint=tabs but simpler.
> > >
> > > My opinion is to have the following selectors:
> > > af:panelTabbed::
> > > - beforeCell (-selected)
> > > - cell (-selected)
> > > - afterCell (-selected)
> > > - separatorCell
> > >
> > > This way it would be skinnable very nice.
> > >
> > > BUT... what to do for backwards compatibillity?
> > >
> > > --
> > > Cristi Toth
> > >
> > > -------------
> > > Codebeat
> > > www.codebeat.ro
> >
>
>
>
> --
>
> Cristi Toth
>
> -------------
> Codebeat
> www.codebeat.ro