Hi Paolo,
attempt-to-precise-semantics
Actually, everything is uniform at this moment. The contract for
Component#setEnabled says:
* Sets whether this component is enabled. Specific components may
decide to
* implement special behavior that uses this property, like web form
*
True.
To make it rock solid, I think it should be adaptable and/or extendable.
IMHO it is not fair to expect that the change you propose is done
perfectly from the start and maybe not even ever.
If you go for slightly less rock solid, one can write code for every
component known in the html
: Mittwoch, 13. Dezember 2006 08:33
An: wicket-dev@incubator.apache.org
Betreff: Re: [Wicket-user] Link#setEnabled( false ) does not
disable button element
I disagree about that.
Methods semantics for components should be uniform, this is
the most important rule for API simplicity and coherence
On 12/13/06, Erik van Oosten [EMAIL PROTECTED] wrote:
True.
To make it rock solid, I think it should be adaptable and/or extendable.
IMHO it is not fair to expect that the change you propose is done
perfectly from the start and maybe not even ever.
Oh, common', what fun is playing fair? ;)
: Paolo Di Tommaso [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 13. Dezember 2006 08:33
An: wicket-dev@incubator.apache.org
Betreff: Re: [Wicket-user] Link#setEnabled( false ) does
not disable
button element
I disagree about that.
Methods semantics for components should be uniform
