lol.
Maybe this should wait until 2.1? :-)
-Matej
Martijn Dashorst wrote:
+1
I also propose that all committers start writing books, then they
wouldn't change this type of stuff so damn often. :-D
Martijn
On 10/8/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
+1
Eelco
On 10/8/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
> Today I wanted to implement disabled state on all link components,
>
> e.g. even Ajax links and submit links. But that would be a hell lot of
> copy and paste code, I'm not really fond of that.
>
> setBeforeDisabledLink, setAfterDisabledLink, etc. these all would have
> to be repeated.
>
> So I though of having AbstractLink with these methods (as well as
> onComponentTagBody).
>
> But the problem is AjaxSubmitLink and SubmitLink. They are derived from
> Button. This is necessary for set/getDefaultFormProcessing as well as
> finding submitting button.
>
> So perhaps we could introduce an interface IFormSubmitComponent with
> getDefaultFormProcessing method that could form use to find submitting
> button? And all links would be derived from AbstractLink, while
> SubmitLink and AjaxSubmitLink would implement IFormSubmitComponent too.
>
> What do you think?
>
> -Matej
>
