This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hi reader, What does this mean : "Your user interface should be designed with the expectation of future functionality enhancements, and it should establish a control scheme that will support this with minimal disruption to the users when this occurs." what is this control scheme that will support this with minimal disruption to the users when this occurs ?. What is going to occur ?. Thank you,
Hello Gurpreet, All this means is basically adhere to the MVC architecture. Then you can put in your write up that you allowed for future enhancements by seperating Data, GUI and Control logic. Good luck Ian
Joined: Jun 09, 2002
Hi reader, I would be using MVC for my JTable component. But I didn't understand the meaning of your last line which says "you allowed for future enhancements by seperating data, GUI and control logic ". Secondly, I dont want to use JTabbedPane for my GUI application Is this OK ?. I am much more interested in using independent windows which will interact with user only for specified reasons. For my knowledge I write you about MVC architecture. If I am wrong then please do correct me. M stands for Model which I would be using as AbstractTableModel. This class will handle the contents of my JTable. V stands for View . This is what we see data encapsulated in JTable. Thirdly, Controller are the methods in Model which actually control the view of the component. Is that OK. Is there any problem If I use different windows in lieu for searching and retrieval of database records and these records get hightened on JTable component which resides on another Main user application interface. I have this idea to implement on my GUI. Please correct me If I am wrong. Thank you, :roll: