laconc / mathquest Goto Github PK

1. Create the FXML file.
2. Alter the FXML file so that the screen looks like the wireframe.

A lot of the code between the methods is repetitive.

Alter the FXML file so that the screen looks like the wireframe.

I'm thinking that we just show a dialog box with a message to the effect: "Contact your local admin so that they may reset your password." Thoughts?

1. Create the FXML file.
2. Alter the FXML file so that the screen looks like the wireframe.

1. Basic FXML files and controllers need to be created for all of the screens.
2. Handlers need to be written to jump to the appropriate screens.
3. Menu.fxml needs to be altered to include the onAction handles.

Avatars should be a property of Entity types.

A user needs to be able to login and view the main menu.

1. Create Option class.
2. Modify User class to include an Option object.

1. Create the FXML file.
2. Alter the FXML file so that the screen looks like the wireframe.

Need code for:

1. Save button
2. Quit button
3. Cancel button

1. Create the FXML file.
2. Alter the FXML file so that the screen looks like the wireframe.

1. Create the FXML file.
2. Alter the FXML file so that the screen looks like the wireframe.

1. Create the class.
2. Write the code for the button handlers.
3. Write the code for the radio button group.

We need notifications for situations such as when time runs out. As it stands, the user isn't given much feedback at all.

Alter the FXML file so that the screen looks like the wireframe.

Admin Tools should only show up if the account logged in is of type 'admin'.
Options should only show up if the account logged in is of type 'user'.

handleSaveButtonAction could stand to be rewritten.

Thought: Stick the checkbox objects into an ArrayList.

Only a basic skeleton was created - still needs to be made to look as it was designed in the Class Diagram.

1. Create the FXML file.
2. Design the interface - possibly wireframe.
3. Alter the FXML file so that it looks like the design.

We need a class that will represent an individual game session.

For each session we need to save:

• time started
• time ended
• games completed
• stages completed
• problems solved & missed for each problem type
• average time to solve a problem

Randomly generates math problems based on the user's settings.