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 > (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 somewhere it would be good to be > able to set a default behavior, but be able to override it. > > -Andrew > > On Fri, Dec 5, 2008 at 8:50 AM, Gerhard Petracek > <[EMAIL PROTECTED]> wrote: > > 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, 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' should be defaulted to true on > >> all tr:commandLink. Then all the skin properties could be converted to > >> attributes and have their defaults set in a common location (like what > >> the skin does). > >> > >> This would be much more useful and flexible as then page developers > >> can make exceptions to the rule. > > > > > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces