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=91822173&tstart=0
http://www.javalobby.com/forums/thread.jspa?threadID=16487&messageID=91822197&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=91822192&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
