This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am getting really close to finish this baby up!! I have been working on the client for the last month and I must say that swing rocks. I've applied it to several java installers kinda like sun's and it works like a charm. Getting to this assignment, I'm attempting to implement the database dialogue box where the user must enter the database location or server and port number depending on the mode in execution. That being said, since I'm trying to use the observer pattern in this case, does it make sense to store settings when the user connects to the main application, more programmtically, within my Observable update() method? Or should the users have the ability to save it at thier own descretion within in the main console?
The instructions.html say the following:
Your programs must not require use of command line arguments other than the single mode flag, which must be supported. Your programs must not require use of command line property specifications. All configuration must be done via a GUI, and must be persistent between runs of the program. Such configuration information must be stored in a file called suncertify.properties which must be located in the current working directory.
I guess this is really preference but I'm totally open to some input.