Originally posted by Jeffry Kristianto Yanuar:
I think most of the candidates use ActionListener. You just decide how to use the ActionListener.
I implement inner classes that implements ActionListener such as BookButtonListener, SearchButtonListener, ExitButtonListener, etc. Judging from its name, you can figure out what the functionality of these classes.
Your user interface should be designed with the expectation of future functionality enhancements, and it should establish a framework that will support this with minimal disruption to the users when this occurs.
As I didn't expect I lost marks in GUI which makes me regret not putting more usability features in the UI (and my work domain is UI).
Originally posted by Alecsandru Cocarla:
Why do you need to know how many rows are in the database?