-Igor
On 11/6/05, Ralf Ebert <[EMAIL PROTECTED]> wrote:
Hi,
> :) Np. Maybe the behaviour idea would be more generalized than
> attribute modifiers. Let's see where that discussion leads us.
just had to write the thing which made me angry about it again, so I
thought I should provide the use case in code:
someCheckBox.add(new AttributeModifier("disabled", true, new Model
("disabled")) {
public boolean isEnabled() {
return ((QueryPosition) getModelObject()).isAllowedForDocument
(getDocument());
}
});
This code definitely is too many lines of code just for disabling a
component according to some model data but to my knowledge there is
no better way to do it... Actually the AttributeModifier is
completely innocent; its just not very suitable for disabling
components :)
Regards,
Ralf
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
