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 applies. If you look at how Trinidad properties
behave, they are looked up statically in a map. So for:
af|tree{
-tr-show-lines:true;
}
The code is skin.getProperty('af|tree-tr-show-lines'). Therefore, the
renderers only ask the skin for a property. Nothing of the component
is related to the skin, so I am not sure how you would code exceptions
into the skin using something like "selectorId". Since there is
potentially more than one property per component, I think using
attributes would be more intuitive.
>
> in your page:
> <tr:tree/> ... uses default selector
>
> for exceptional usages:
> <tr:tree selectorId="myId"/> ... uses selector with "myId" to use a
> different selector
>
> @your tr:commandLink comment:
> does that mean that you have more links which perform ppr requests than
> links for navigation within your pages?
There is no reason why PPR requests cannot navigate, and that was how
I was developing my application. I also had most of my navigation as
partial page navigation, so there is one page loaded and different
areas of the page would navigate, so the user was never subjected to a
full page load after the first page (so all page "chrome" was only
loaded once), kind of like gmail if you will.
