]
Subject: Re: [Skinning] Independent skinning myfaces
subproject
To: MyFaces Development dev@myfaces.apache.org
mailto:dev@myfaces.apache.org
Date: Saturday, December 6, 2008, 12:42 PM
hello simon,
no it's just
--- On Tue, 12/9/08, Matthias Wessendorf [EMAIL PROTECTED] wrote:
From: Matthias Wessendorf [EMAIL PROTECTED]
Subject: Re: [Skinning] Independent skinning myfaces subproject
To: MyFaces Development dev@myfaces.apache.org
Date: Tuesday, December 9, 2008, 12:52 AM
On Tue, Dec 9, 2008 at 1:03 AM
/[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]/* wrote:
From: Gerhard Petracek [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Subject: Re: [Skinning] Independent skinning myfaces
subproject
To: MyFaces Development dev
hello leonardo,
it's an interesting idea.
the summary mentions
- trinidad
- tomahawk
- tobago
the details just describe
- trinidad
- tomahawk
is there a special reason for that?
regards,
gerhard
2008/12/1 Leonardo Uribe [EMAIL PROTECTED]
Hi
I would like put on consideration this
On Fri, Dec 5, 2008 at 5:12 AM, Gerhard Petracek [EMAIL PROTECTED]
wrote:
hello leonardo,
it's an interesting idea.
the summary mentions
- trinidad
- tomahawk
- tobago
the details just describe
- trinidad
- tomahawk
is there a special reason for that?
Hi
Well, the idea, as
hello leonardo,
i prefer one skinning approach for all myfaces component libs.
regards,
gerhard
2008/12/5 Leonardo Uribe [EMAIL PROTECTED]
On Fri, Dec 5, 2008 at 5:12 AM, Gerhard Petracek
[EMAIL PROTECTED] wrote:
hello leonardo,
it's an interesting idea.
the summary mentions
-
for the SkinResourceServlet.
Hope this sheds some more light on the new project. We'd love to hear more
comments from the community. :)
Best Regards,
Paul Rivera
--- On Fri, 12/5/08, Gerhard Petracek [EMAIL PROTECTED] wrote:
From: Gerhard Petracek [EMAIL PROTECTED]
Subject: Re: [Skinning] Independent skinning
Petracek [EMAIL PROTECTED]
Subject: Re: [Skinning] Independent skinning myfaces subproject
To: MyFaces Development dev@myfaces.apache.org
Date: Friday, December 5, 2008, 5:14 AM
hello leonardo,
i prefer one skinning approach for all myfaces component libs.
regards,
gerhard
2008/12/5
Regards,
Paul Rivera
--- On *Fri, 12/5/08, Gerhard Petracek [EMAIL PROTECTED]*wrote:
From: Gerhard Petracek [EMAIL PROTECTED]
Subject: Re: [Skinning] Independent skinning myfaces subproject
To: MyFaces Development dev@myfaces.apache.org
Date: Friday, December 5, 2008, 5:14 AM
hello leonardo
]
Subject: Re: [Skinning] Independent skinning myfaces subproject
To: MyFaces Development dev@myfaces.apache.org
Date: Friday, December 5, 2008, 5:14 AM
hello leonardo,
i prefer one skinning approach for all myfaces component libs.
regards,
gerhard
2008/12/5 Leonardo Uribe [EMAIL PROTECTED
All other frameworks use
component attributes for this, but Trinidad puts it in these
non-intuitive skinning keys.
Sorry, had one more comment right after I hit send again. Maybe just
having default component attributes for a web app would satisfy the
need. Like a way to say 'partialSumbit'
hello andrew,
@true as default value for partialSubmit:
do you mean via a new configuration entry?
regards,
gerhard
2008/12/5 Andrew Robinson [EMAIL PROTECTED]
All other frameworks use
component attributes for this, but Trinidad puts it in these
non-intuitive skinning keys.
Sorry,
Yeah something like that. Right now skinning properties in Trinidad
are used to set behaviors for components for the entire skin
(non-component level control). Since they can only be applied to all
or no components, there is no way to say for a given set of
components, use this behavior. So
hello andrew,
just to avoid misunderstandings:
do you have a concrete use-case in mind?
regards,
gerhard
2008/12/5 Andrew Robinson [EMAIL PROTECTED]
Yeah something like that. Right now skinning properties in Trinidad
are used to set behaviors for components for the entire skin
Use case:
Show lines in the Trinidad tree, except for a tree on one page.
This is currently not possible. This can be done:
af|tree{
-tr-show-lines:true;
}
But there is no way to make an exception. What would be better is to
have tr:tree showLines=true/ as the default and then use tr:tree
hello andrew,
so far i haven't thought about details.
however, what's about an additional id concept for exceptional usages?
so you have multiple af|tree selectors + a new syntax to reference them.
in your page:
tr:tree/ ... uses default selector
for exceptional usages:
tr:tree selectorId=myId/
I agree with most of these statements, but I would start even higher than
that, like defining the base interfaces and access classes.
For instance, I think it's safe to assume that a Skin class or interface
should exists. Let assume all interfaces for now as it takes less
characters. Now, from
Whatever we do we need to be backward compatible because there are a lot
of skins out there, and we don't want to break them.
We should start first on all the clean up code, like getting rid of the
XSS code. We need to convert the current XSS into CSS and to do that,
we'll need to make sure all
Andrew, is this a made up use case or one that someone has asked for? We
usually decide whether or not a UI feature of a component should be an
attribute on the component or a skinning property by how likely it is
that someone will want to change it on a component basis or a
application wide
On Fri, Dec 5, 2008 at 3:02 PM, Jeanne Waldman
[EMAIL PROTECTED] wrote:
Andrew, is this a made up use case or one that someone has asked for?
No, these are problems that I had when using Trinidad
We
usually decide whether or not a UI feature of a component should be an
attribute on the
On Fri, Dec 5, 2008 at 10:17 AM, Gerhard Petracek
[EMAIL PROTECTED] wrote:
hello andrew,
so far i haven't thought about details.
however, what's about an additional id concept for exceptional usages?
so you have multiple af|tree selectors + a new syntax to reference them.
I am not sure this
Hi Simon,
I'm a little unclear on the process. Can you explain? Like did you come
up with these ideas and then we all discuss them or is there an Expert
Group you will send these to ( you say that at the end) and they will be
the primary owner of this project? Is the idea that we would someday
Hi Jeanne,
Skinning is part of the scope of JSF 2.0, see under Adoption at
http://jcp.org/en/jsr/detail?id=314. However, so far skinning is not part of
the spec, see the public review for reference. Also, time is running short
and I fear that skinning might not be part of the final spec if I
hello andrew,
i suggest to postpone the discussion. once we know details about skinning in
jsf 2.0 we should continue.
@ppr and navigation:
there is nothing like partial page navigation. if you navigate via a ppr
enabled command component, you get a full page refresh.
furthermore, there is a
Hi
I would like put on consideration this proposal for a myfaces subproject.
The idea is simple: create a independent skinning module for skin all
myfaces jsf components libraries, taking as base trinidad skinning code.
In other words, the long term objective is build a single skinning api that
25 matches
Mail list logo
