Sorry, I shouldn't have suggested subclassing. The preferred way to extend
and/or override a Tapestry component's functionality is to "wrap" it. If you
can't achieve what you want with wrapping then maybe create your own component
by copying DateField? It might not be much work.
As for your las
I should try extedning the datefield component but I have a question, is it
just about my component class "extending" tapestry's component class and
that's it ? No other wiring needed ?
Just a plain java "extends" and referring to my component instead ?
A question to the developers, why isn't tap
> This may help:
>
> http://localhost:8080/jumpstart/examples/component/eventbubbling
Wrong. I meant this:
http://jumpstart.doublenegative.com.au/jumpstart/examples/component/eventbubbling
On 16/12/2012, at 10:14 AM, Muhammad Gelbana wrote:
> Some tapestry components do fire ajax events and reach out to the server
> and it get's handy sometimes to listen to those events. For instance the
> datefield event fired to format the selected date. Side question, why does
> the date field h
Some tapestry components do fire ajax events and reach out to the server
and it get's handy sometimes to listen to those events. For instance the
datefield event fired to format the selected date. Side question, why does
the date field have to reach out to the server to format the selected date,
ca
