I agree with Maurice. I'm not sure whether I would use it much, but it
is a good feature for when you create layered component libraries.
Eelco
Maurice Marrink wrote:
Of course we should give the developer the option to lock certain
attributes.
It will help him prevent the user from messing up the internal working
of the component.
Much like final is now used in wicket code itself.
I'm not a big fan of final myself but I recognize the use/ need for it.
Besides if there are many request made to the developer to open up a
attribute (make it more extensible) he can do so himself.
Just my 2 cents
Maurice
-----Oorspronkelijk bericht-----
Van: Gili [mailto:[EMAIL PROTECTED]
Verzonden: woensdag 16 maart 2005 16:47
Aan: [email protected]
Onderwerp: Re: [Wicket-develop] [ wicket-Feature Requests-1164355 ]
possibility to lock attributes on components
I'm -1 on this one. We should document markup contributions but
not prevent the user from doing anything he wants. Alternatively, if we
implment this, it should be possible to subclass the class and
explicitly remove this lock.
Gili
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
