Patrick Moore wrote:
you could always put a MyLabel subclass in the
"org.apache.tapestry5.corelib.components"
package and then derive from that. Java does let classes be in different
source directories and still be in the same package...
Its a little ugly ... but a whole lot better than the cut-
you could always put a MyLabel subclass in the
"org.apache.tapestry5.corelib.components"
package and then derive from that. Java does let classes be in different
source directories and still be in the same package...
Its a little ugly ... but a whole lot better than the cut-and-paste that you
are
Em Fri, 27 Jun 2008 04:21:47 -0300, Francois Armand <[EMAIL PROTECTED]>
escreveu:
I faced exactly the same problem when I was playing with a personnal
beaneditor : at the end, the only solution I found was to copy&paste the
beanEditor class, change visibility to protected and add one or two
Thiago H. de Paula Figueiredo wrote:
[...]
Question to Howard: instead of having package visibility, could the
core components have methods with protected visibility? And could
their fields hava protected getters, so component subclasses can
access superclass' parameter values? Or the current
I have same pain with you, Thiago. It's not easy for subclasses to
access parameters in parent classes.
Delegation works perfectly, but you have to copy all parameters from
parent component.
Yunhua
On Tue, Jun 24, 2008 at 11:05 PM, Thiago H. de Paula Figueiredo
<[EMAIL PROTECTED]> wrote:
> I've
I've faced the same situation more than once trying to build my own
components that extend or slightly changes some existing T5-core
component. For example, subclassing the Label component so it always
ignores its body and generates the label name from the corresponding field
id. That could
