[Shale] Questions and suggestion to Clay

Some questions and suggestions that may need further discussion: - Is there a reason why validators and converters (actionListeners and valueChangeListeners too?) are not inherited by elements and extending components? - There is a problem with properties. A component is possibly based on the

dev@struts.apache.org

>>> - There is a problem with properties. A component is possibly based on the >>> generic attribute map and has no setter for a property. e.g. function Name >>> property in ValidatorScript. >>> >>> At the moment Clay has no knowledge about such attributes and it's >>> impossible >>> to do

[Shale] Questions and suggestion to Clay

Gary, >> - Is there a reason why validators and converters (actionListeners and >> valueChangeListeners too?) are not inherited by elements and extending >> components? > > The significance of the name is only for enumeration. I took this approach > rather than adding another attribute to dist

Re: [Shale] Questions and suggestion to Clay

Gary - Is there a reason why validators and converters (actionListeners and valueChangeListeners too?) are not inherited by elements and extending components? Good that you have found the problem. - There is a problem with properties. A component is possibly based on the

Re: [Shale] Questions and suggestion to Clay

>> - There is a problem with properties. A component is possibly based >> on the generic attribute map and has no setter for a property. e.g. >> functionName property in ValidatorScript. >> >> At the moment Clay has no knowledge about such attributes and it's >> impossible t

Re: [shale][clay] Component attributes overriding. Proposals

> [snip] > > PROBLEMS > > [snip] > > ### 3. ### Undesirable overriding. > > As I mentioned above, in case of > > the 'value' is passed to the component overriding the 'value' in the > component declaration. > > Scenario: > web designer has created a mockup that contains some buttons and want

Re: [shale][clay] Reusing the components declaring in the snippet body. Proposal

> > PROBLEM > > I have found that the content on > the hrolodex.html is totally mock, the the contactTable component build its > content from the scratch inside the clay config file. > From the first sight, I used to expect that the content of the result > panelGrid can be also taken from the h

Re: [shale][clay] Component attributes overriding. Proposals

>> [snip] >> >> Another possible solution is that the component always overwrites the >> values in the html template. >> >> Examples: >> >> Use the value of the component >> >> >> >> >> >> >> >> >> >> >> >> Use the value of the template >> >> >> >> >> >>

Re: [shale][clay] Component attributes overriding. Proposals

> [snip] > I would prefer to see the html attributes always override the xml > definitions. I say that because it favors the web designer > instead of the developer. > However, this new proposed attribute (allowOverriding="false") would give > the developer the final decision. The same as

Re: [shale][clay] Component attributes overriding. Proposals

Re: [shale][clay] Component attributes overriding. Proposals >>> [snip] >>> I would prefer to see the html attributes always override the xml >>> definitions. I say that because it favors the web designer >>> instead of the developer. >>> However, this new proposed attribute (allowOverriding=

Re: [shale][clay] Reusing the components declaring in the snippet body. Proposal

Re: [shale][clay] Reusing the components declaring in the snippet body. Proposal > This proposal is not about the way how to magically force existing component > to do what they can do. It is only about maximizing reusing of the html > elements. > > Look at the hrolodex.html . There are two main

Re: [shale][clay] jsfid and base html tag. Proposal

Sergey> PROPOSAL Sergey> Sergey> To make it possible to provide jsfid attribute for any html tag. +1 I think it would be very useful to be able to customize any tag. In this context it may be useful to have a component that has the capability to render any HTML tag. Maybe something like this:

Re: [ANNOUNCEMENT] New Struts Committer: Gary vanMatre

Congratulations Gary! Manfred Craig McClanahan wrote: > > Please join me in welcoming Gary vanMatre as a new Struts committer. > Gary has been quite busy proposing code for the "Clay" plug-in on > Shale, and has also been supportive on the dev and user mailing lists > (for both Struts and MyFac

[shale] Inconsistent end-of-line markers

Currently shale use both, Windows (CRLF) and Unix (LF) line endings. My suggestion is to set the svn:eol-style property to native. This will result in consistent line endings across all platforms. Manfred __ Verschicken Sie romantisch

Re: svn commit: r278619 - in /struts/shale/trunk: use-cases/src/java/org/apache/shale/usecases/rolodex/dex.xml xdocs/navigation.xml

> > Author: wsmoak > > Date: Sun Sep 4 11:14:38 2005 > > New Revision: 278619 > > > > URL: http://svn.apache.org/viewcvs?rev=278619&view=rev > > Log: > > Fix typo, correct link to Struts home page > > > > Modified: > > > > struts/shale/trunk/use-cases/src/java/org/apache/shale/usecases/rolodex/d

Re: Unable to move files in repository

From: "Wendy Smoak" <[EMAIL PROTECTED]> > From: "Martin Cooper" <[EMAIL PROTECTED]> > > > You should send a message to infrastructure@ about this and / or bring it > > up > > on #asfinfra. This seems like something that needs fixing in the repo. ;-( > > Maybe not... I found that the core dump