Re: [Wicket-develop] [ wicket-Bugs-1383714 ] Enabled properties for Component/AttributeModifier not versi

[Igor Vaynberg]

im -1 on final. i prefer pull models to push models as they help tie things together cleaner imho.

-Igor

On 12/17/05, Johan Compagner < [EMAIL PROTECTED]> wrote:

ofcourse it is up to the user what to do there.
But if you would ask certain persons i think they would say make it final ;)
The final keyword is again discussed at  JavaPolis (ofcourse :))

johan

On 12/17/05, Igor Vaynberg <[EMAIL PROTECTED] > wrote:

What do you mean rename isEnabled ot isVisible() and remove setEnabled?
But what would that solve?
Because now if you override isVisible() on component then you also bypass the version manager.
(this would be a candidate to be final because of that!, but it is to damn handy to be able to override it)

when you override isVisible() or isEnabled() or any is method, does that value really need to be versioned? they are pull functions now instead of push, you are calculating their value every request so why version it? if the calculation depends on some properties that need to be versioned then it is the user's responsibility to version those properties whenever they change imho.

-Igor