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 On Wed, 16 Mar 2005 02:22:14 -0800, SourceForge.net wrote: >Feature Requests item #1164355, was opened at 2005-03-16 11:22 >Message generated for change (Tracker Item Submitted) made by Item Submitter >You can respond by visiting: >https://sourceforge.net/tracker/?func=detail&atid=684978&aid=1164355&gr oup_id=119783 > >Category: None >Group: None >Status: Open >Priority: 5 >Submitted By: Maurice Marrink (mrmean) >Assigned to: Nobody/Anonymous (nobody) >Summary: possibility to lock attributes on components > >Initial Comment: >Say a developer makes a custom component with a >mouseOver attributemodifier. He should be able to >prevent users of his component to override the >mouseOver attribute. Basicly locking the attribute. >when an attributemodifier is added to a component it >should first check if the attribute is not locked. > >Although we could add more levels here like : >-Open >-Append only >-Prepend only >-Locked > >I think it would be best to leave it to the developer if he >wants to lock an attribute but still give users the option >to add something like an extra JS function that gets >called in addition to the developers code. Since the >insertion of user code will be very difficult to handle in a >generic way. > >---------------------------------------------------------------------- > >You can respond by visiting: >https://sourceforge.net/tracker/?func=detail&atid=684978&aid=1164355&gr oup_id=119783 > > >------------------------------------------------------- >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 > ------------------------------------------------------- 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 ------------------------------------------------------- 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_ide95&alloc_id396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
