Yeah, this is a good one:
'I often see some people subclass JFrame and others create an instance in the same situation, and that's fine. What you don't want to have happen is to end up with 10,000 lines of code that use a JFrame instance and you're jumping through hoops when subclassing would make the whole thing much easier.'
Martijn Dashorst wrote:
A nice discussion on JavaLobby concerning just this subject.
http://www.javalobby.com/forums/thread.jspa?threadID=16487&messageID=91822159&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
