Implement the system you specified in the previous lab. All team members must contribute to this implementation. Be sure to fix any issues identified by your instructor during their review of the previous lab.
You can use SceneBuilder to update the bee_simulator.fxml file or you can edit it directly. If you edit it directly, be careful; errors from loading broken .fxml files are often vague. Rebuild your solution after each small change to make sure the program still runs.
Randomly generate the locations of the bees and flowers. Ask if you need help with this!
Allow the user to adjust the number of bees and flowers. The user should be able to enter 0 for both, and allow at least 100 of each. Note the default will be the same as in the previous lab. A slider is a good way to implement this feature, but a simple text box is fine. Just ensure that the default for either the slider or the text box matches the default numbers defined in the previous lab.
Your implementation will have a number of parameters that are somewhat arbitrary such as how far a bee moves on each step and how much energy is drained when a bee encounters a “bad” flower. Experiment with different values so a simulation with a reasonable number of bees and flowers illustrates all of the behaviors and all bees die off within about 30 seconds (while pressing the arrow key continuously). As an example of a parameter that might need adjusting, if bees gain too much energy from flowers then the bees will never die, but if they lose too much while flying between flowers then they die too quickly.
Check that your user experience is reasonable. For example, the number of bees and flowers should be adjustable on the main screen, either with a text box with a default or a slider. Ensure focus is on the right element so pressing the arrow key does not require clicking somewhere else first. The image legend (showing types of bees and flowers) should be placed (possibly in a separate window) so that the garden space is as large as possible. In general, ensure the program’s user experience is consistent with what you would expect on Windows. To make this happen, you will want to call
setFocusTraversable(true) and requestFocus on the main panel after responding to user input changing the number of bees and flowers.
Check that your solution meets your instructor’s coding standard. Document responsibilities for classes, but you do not have to write Javadoc for methods.
Check your project in to the Git repository as in the previous lab. Remember all changes need to be committed and pushed to the main branch.
Check out your project in a new folder and ensure it builds. This helps ensure you did not fail to check in a critical file and that files are in the correct location. Mistakes in this often lead to losing points for easily-corrected issues.
When you are finished, create a PDF containing the following:
Main.java, container types, JavaFX classes, or other elements that are important to developers rather than users. Do not use reverse-engineering to generate this diagram.You will upload this PDF to Canvas. You can use MSWord or similar tools to create the PDF.
See Canvas for any additional submission instructions.