CMSC203 GUI Lab solution

Description

Overview: In the Graphical User Interface (GUI) Lab we will construct a simple GUI step by step.

Data Manager: (Provided to the student) It is good programming practice to separate functionality into distinct classes.  To accomplish this, GUI functionality is kept separate from the management of the application.  The DataManager does not interact with the user.  Rather, the GUI collects any user input like mouse-clicks and calls methods of the DataManager, and the DataManager reports results to the GUI which may be displayed to the user.  Within the DataManager, there are usually one or more Data Structures, which are populated with one or more types of Data Elements.  This DataManager has only simple functionality which does not require data structures other than simple fields.

FXDriver: (Initial version provided to the student) The class called FXDriver is the starting point for the FX version of the GUI.  FX is the framework we will use, and is available beginning with Java 8.  There are many ways to organize the GUI, but one way is to hold the basic startup features in a single simple file, which calls an instance of the main panel.

In FX, the main method (as in any Java application) is the starting point.  In FX it calls only the method launch(args), where args is the array of data passed in to the application, usually null.  This launch method executes various setup code, hidden from the programmer, including creating a so-called “stage”, and calls the method start(Stage stage);  Everything that the programmer wants to execute must be placed in start.

FXMainPane: (Initial version provided to the student) In this approach to GUI building, an instance of the class FXMainPane does all the programmer’s work of creating the GUI.  The initial version is simply a stub with a constructor, so that FXDriver will compile and run.

Each task has a comment in the java files such as //student Task #n

with a statement about what is to be accomplished.

Task #1

• Create a java project in Eclipse. Load the files FXDriver.java, FXMainPane.java, and DataManager.java from Blackboard into this project.
• In the FXDriver class, create an instance of FXMainPane and set it to a new instance of FXMainPane called
• Using the parameter called stage (provided by Java FX when launch calls start), call the method setScene(new Scene(root, [width],[height])); The parameters width and height specify the dimensions of the scene window in integer pixels.

Compile and run.  Note that a window appears but does not have any content.

Take screenshots of run a program.

Task #2

Note that FXMainPane extends VBox, so the class is a VBox.

• In the FXMainPane class, declare five buttons, a label, and a textfield. Declare two HBoxes that will hold the these components and go inside the VBox.

• Instantiate the buttons with the arguments “Hello”, “Howdy”, “Chinese“, Clear”, and “Exit”.

• Instantiate the label with the argument “Feedback:”.

• Instantiate the textfield.

• Instantiate the HBox

• Compile and run the FXDriver.

• Take screenshots of run a program.

Note that even though the buttons and other components are instantiated, they do not appear in the window.

Task #3

To cause components to appear, they must be added to a containing component, which itself is added to its containing component, all the way up to the component that is added to Scene.

• Add the buttons to one of the HBoxes using getChildren().addAll(button1, etc…)

• Add the label and the textfield to the other HBox

• Add the HBoxes to the FXMainPane (which is a VBox) using getChildren().addAll(…). Note that we have already added FXMainPane to the new Scene in FXDriver.

• Compile and run the FXDriver.
• Take screenshots of run a program.

Note two things: The buttons do not respond to mouse-clicks, and the components are not well-spread, but are all positioned in the upper left corner of the containing window.

Task #4

• Declare an instance of DataManager at the FXMainPane class level so that its scope extends throughout the class. Instantiate it in the constructor.

• To set the buttons to respond to mouse-clicks,
  1. create an inner class at the class level (for example, called ButtonHandler) that implements EventHandler<ActionEvent>. For each button, use setOnAction(new ButtonHandler()).
  2. This interface requires the method handle(ActionEvent event) to be implemented. The mouse event is provided to the handle method, and getTarget() returns the object that caused the event, allowing a selection to be made.
  3. Implement an if-else-if structure that gets the target button that was selected and executes the appropriate block of code.
     1. If the “Hello”, “Howdy” or “Chinese” buttons were selected, call the DataManager instance’s methods getHello, getHowdy, or getChinese and call the text field’s method setText with the response from the DataManager.
     2. If the “Clear” button was selected, call the text field’s method setText(“”); to clear out the text field.

• If the “Exit” button was selected, call exit(); and System.exit(0);

• Position the components so they are generally centered and spaced apart.
  1. To set margins for each component, call the static method on the containing component, e.g., setMargin(button1, inset); where inset is an instance of the class Inset.
  2. To center each HBox, use setAlignment(Pos.CENTER); where Pos is an Enum that will need to be imported.

• JUST FOR FUN (optional): create a sixth button that says “Hello” in another language. Add a method to the DataManager class to return the string.

• Add the files to GitHub in a directory named CMSC203_Lab2
• Compile and run FXDriver. Select each of the buttons to ensure they are working correctly.

• Take screenshots of run the program.

Deliverables:

• Submit the three java files to Blackboard.
• Submit screenshots of run Program for each Task: Task#1, Task#2, Task#3, Task#4 to confirm all buttons work.