Welcome to the Java Programming Forums
The professional, friendly Java community. 21,500 members and growing!
The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.
>> REGISTER NOW TO START POSTING
Members have full access to the forums. Advertisements are removed for registered users.
LinkBack URL
About LinkBacks
Event Handling - Best Practice?
Greetings All
I am a C++ programmer who is attempting to learn Java with the ultimate aim of sitting the Oracle certification. I have (hopefully) a very simply question.
What is the best method for implementing listeners? Should I be putting them into anonymous inner classes or into a fully fledged private inner class? I have googled this question but my efforts haven't yielded a definite answer.
Many Thanks
Nikki
Related threads:
Re: Event Handling - Best Practice?
In my opinion there really isn't a best method. I've seen listeners implemented in a large number of ways...many with a different reason behind the implementation. My .02 - always think about code re-usability and adaptability to change. Sometimes writing inner classes locks you into an implementation that is difficult to modify in the future, in other situations it encapsulates the implementation details which can be beneficial - both are case dependent.
ishtar (October 5th, 2011)
Re: Event Handling - Best Practice?
It depends if listener has to be used by multiple object than making it a full fleged class make sense but if its only attached to one element than having them as inner class is ok.
Re: Event Handling - Best Practice?
Oracle suggests use of inner classes for listeners. Switch statements are not good OOP design .
On the downside, you will start having tons of .class files for each event handler. That could ,for example, affect loading time of applets. But until then, it is better to go with the suggestion.
ishtar (October 5th, 2011), kyasuleyman (May 1st, 2012)
Re: Event Handling - Best Practice?
Curious where this is suggested. Do you have a link? Because from the standpoint of making code loosely couple, adaptable, and reusable this advice needs to be scrutinized.Oracle suggests use of inner classes for listeners.
Last edited by copeg; October 1st, 2011 at 01:55 PM.
ishtar (October 5th, 2011)
Re: Event Handling - Best Practice?
You are right. Oracle just points out use of inner classes is inefficient but is a good OO design. But does not recommendOriginally Posted by copeg
any of the methods
General Information about Writing Event Listeners (The Java™ Tutorials > Creating a GUI With JFC/Swing > Writing Event Listeners)We can not recommend a specific approach because one solution would not suit all situations.
It must be some pro-OO design website that I got the suggestion from. Among the three methods they compared
(switches, annonymous classes, inner classes), they suggested inner classes as best OO practice.
ishtar (October 5th, 2011)
Re: Event Handling - Best Practice?
Just a quick post to say thank you all
Regards
Nikki
Reply With Quote