i agree. there are reasons to subclass form components that have been brought up that make sense, such as creating subclasses with default validation. one can imagine there being a convenience to PhoneNumberField or DigitField. however, i think we should make all the methods final in each class until we come up with reasons to want to override those (if there are reasons now, we can omit final from select methods). we're not doing this to annoy people. the development team just wants to understand how things are being extended so we can avoid breaking people in ugly ways after the 1.0 release.


i'm +1 on letting people extend these classes.

Maurice Marrink wrote:

Non final +1

-----Oorspronkelijk bericht-----
Van: Jonathan Locke [mailto:[EMAIL PROTECTED] Verzonden: maandag 31 januari 2005 6:42
Aan: [email protected]
Onderwerp: Re: [Wicket-develop] Making form component implementations
non final




Gili wrote:



        Regardless of whether you go for a black-box framework or
white-box one, it should always be made as extensible as possible. The




as long as this goal is subordinate to the goal to control and direct growth for the good of the commons, i agree. extensibility without forethought and for its own sake often leads to disaster.



problem with Swing (and Wicket to a certain degree) is that it was
designed to only be extended by its original authors and suffers from
high coupling. It might be a powerful framework, highly reusable, but
extremely difficult to extend. Please ensure that Wicket doesn't suffer


from the same problem.


Gili

On Mon, 31 Jan 2005 00:25:19 +0100, Martijn Dashorst wrote:





Eelco Hillenius wrote:





And don't forget I propose to finalize the methods that let a component be a specific one, so the '/It makes it harder to change things later' /argument won't apply here.




Sure it does. Since you /still/ publish that interface which can be overridden. Are you intending to make TextField abstract, so it /communicates/ extensibility? There are enough people (also in the javalobby discussion) that find that either a class is abstract and intended for extensibility or final.

Calling people OO Zealots is going too far imho. Having a strong


opinion

(most of them have legitimate reasons for doing so) doesn't make them 'zealots'.
http://www.javalobby.com/forums/thread.jspa?threadID=16487&messageID=9


1822173&tstart=0


http://www.javalobby.com/forums/thread.jspa?threadID=16487&messageID=9


1822197&tstart=0


Gives a nice description on why one should favor composition above inheritance.

I think the /real/ question is: are we delivering a whitebox framework





(allowing people to extend whatever, whenever they want) or are we delivering a blackbox framework (giving people a very powerfull tool which they can use and extend using some very carefull thought through





concepts)?
http://www.javalobby.com/forums/thread.jspa?threadID=16487&messageID=9


1822192&tstart=0


Martijn



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive


Reporting


Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop







-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop







-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop


------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop





-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to