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 facelets bug [1]. due to this bug it seems that partial page navigation works in special constellations. anyway, with the upcoming facelets version it will be a problem in special constellations, if a ppr enabled command component is used for navigation. since there is no advantage and it might lead to problems in the future, it's better to avoid it. regards, gerhard [1] https://facelets.dev.java.net/issues/show_bug.cgi?id=296 2008/12/5 Andrew Robinson <[EMAIL PROTECTED]> > 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. > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
