+1
As for the name, maybe skin-extension? skin-addition is as good however.
About the structure, I would like to see those placed in
trinidad-skins.xmlalong with the skins. I think we should also extends
our lookup to include
.jar files' /META-INF folder if we don't already do it since it'll be
I am sending this again . Please respond if you are facing similar issue
or/and have solution/suggestions.
Note : To test this bug, deploy trinidad-demo WAR file in your server and
open showOneAccordion.jspx or showManyAccordion.jspx. You will have to click
refresh after every click on
I don't think it should be a separate file; it should be a new
element in trinidad-skins.xml. And +1 to Simon's request
for /META-INF support.
This way, you could use a /META-INF/trinidad-skins.xml
file to provide drop-in JARs that provide:
- skin extensions
- new skins
One big bit of fun:
I was thinking about whether we should use the same file, and the pro of
using the same file --
fewer files is really good. The cons, they are aimed at different users.
A custom component developer will want to add to existing skins, not
create new skins.
I'll go with the fewer files is really
Hi there,
I see there are a lot of parsers that I'm 99.9% sure we no longer use.
We used to use them before Trinidad was Trinidad and was UIX.
They are all the parsers in the
org.apache.myfaces.trinidadinternal.ui.laf.xml.parse package.
Is there a reason that these are still around? I
Yep, I don't think those are used anymore.
-- Adam
On 11/6/06, Jeanne Waldman [EMAIL PROTECTED] wrote:
Hi there,
I see there are a lot of parsers that I'm 99.9% sure we no longer use.
We used to use them before Trinidad was Trinidad and was UIX.
They are all the parsers in the
Except for SkinExtensionParser, that's still used, although it will
change some after I do my work.
I'll create an issue for the other ones.
- Jeanne
Adam Winer wrote:
Yep, I don't think those are used anymore.
-- Adam
On 11/6/06, Jeanne Waldman [EMAIL PROTECTED] wrote:
Hi there,
I
