CMIS 242


Change the posted DateDriver.java so that it uses Swing GUI widgets
instead of JOptionPanes and System.out for input and output.

Make it look like the image DateDriverGUI.gif
Notice not every command of the DateDriver is being done in the GUI version.

To create the GUI use the code in SwingGUIsFrameDemo.java 
Basically you are merging the DateDriver and the SwingGUISFrameDemo.

Each command in the DateDriver should be a button.
Every keyboard-inputted data should be a textfield.
Output is to go the textarea.
No JOptionPanes or printlns are to be used.

Design what widgets are needed and then copy and paste the
"incantations" to create widgets. Only labels, textfields, buttons and
a textarea are needed. Change the names of the labels, textfields and
buttons to meaningful names.  The event handler(s) will mostly just do
the desired action to the Date object in the array and display a
message to a textarea (i.e. pretty much what the DateDriver does now).

Implementation hints:
Declare the array as an instance variable and instantiate it
(i.e. create it) in the constructor.
The do loop and the command String won't be used.
The println stuff will instead go to the textarea.
actionPerformed will be a cascaded else-if structure determining which
button was pressed and doing the same actions that was done in the do loop.
Suggestion: make the noArg button along with the index field and the
toString button first so you can see that objects are being created.
Then add the month, day and year textfields and the 3arg button. etc.
The non-static getIndex method can return the value in the index field.
The program can be brittle, i.e. if erroneous input is given, or more
likely if none is given, it can crash.  Don't worry about that.

Make no changes to Date.java

Submit just your DateDriverGUI.java file.

This is a good exercise to start to learn how to do Swing GUI and
event-driven programming.