This application is used to keep track of inventory information. A c.pdf
- 1. This application is used to keep track of inventory information. A company wants to allow users to input information about inventory items and then print a list of items in inventory that need to be re-ordered. There are three classes in this assignment (specific details further down) in addition to the application main class: The Inventory Class o This is the class that you wrote in Assignment 1. o You must make any necessary corrections to this class before you write this assignment. See your Assignment 1 evaluation. The InventoryList class o Models an Array or List of Inventory objects that are input by the user. The Assign2Controller class o Has an object of the InventoryList class to store and manage the information of items in the inventory. o This class must contain all event handling code needed to run the application (more details below). All classes must be part of the same package. 1. Inventory Class You wrote this class in Assignment 1. You must make any corrections to this class before you finish Assignment 2. 2. InventoryList Class The InventoryList class models a list of the inventory items entered by the user. For this assignment it will be used to contain Inventory objects as they are input by the user. The specs for the InventoryList class are shown in the diagram below: Class: InventoryList Data Members: - invList : ArrayList Method Members: + InventoryList() + add(inventory : Inventory) : void + get(index : int) : Inventory + length() : int The invList member is an Array or ArrayList of Inventory objects. You can instantiate the empty ArrayList in the same statement in which you declare it.
- 2. The add() method accepts an Inventory object to add to the invList. There is nothing special going on here: simply add the object to invList. The get() method accepts an integer index and returns the Inventory object at that index, but only if the index is a valid index. If the index is invalid, the method should simply return a null object. The length() method returns the size of the invList (the # of elements that contain Inventory objects). You don't need a toString() at this time, but you could add one if you wanted to. The UI Controls, Layout, and Styling The Main UI Your program has the following UI elements (specific details about functionality are outlined later): A label heading with the text "Inventory Tracker". The label is bound to the top of the screen and remains centred, regardless of screen width. Label/TextField pairs to be used for data entry by the user. There is one pair of controls for each field input. The labels contain the String captions. The ADD button. This button has the hot-key "A" and is used to clear the input fields so that the user can easily type inputs for a new Inventory object. The SAVE button. This button has the hot-key "S" and is used to save the current input values as an Inventory object to the InventoryList. The inputs entered by the user are validated before the Inventory object is added to the InventoryList: any errors are displayed in Alert dialog boxes. The ORDERS button. This button has the hot-key "O" and, when clicked, will display a list of Inventory objects from the InventoryList that need to be re-ordered (qoh <= rop). The list of items is displayed in the TextArea below the input area. The EXIT button. This button is used to exit the program, upon confirmation from the user. The input fields and buttons are laid out in the "Input Area", in a GridPane container (instead of AnchorPane, details later). The Messages Label. This label is at the bottom of the UI. It is used for: - It displays a message "No items to list. Add some." in red when the user clicks the ORDER button while the InventoryList is empty. - It displays a message "No items to re-order." when the user clicks ORDERS and there are items in the InventoryList, but none that need to be re-ordered. The UI elements must be laid out and displayed exactly as shown in the screen shots. Your UI
- 3. must contain a meaningful title in the title bar. The UI's Functionality Use event handlers to add control functionalities as follows: When ADD Button is clicked or Hot key: A is used, the following tasks are done: All text fields emptied of all text. Depending on how you deal with the message label, you might also need to remove the "error" from the message label at this point and empty its text. When SAVE Button is clicked or Hot key: S is used: Construct a new Inventory object and use the mutator methods to assign the user inputs to each field. Handle any error: display an Alert dialog box for the field that has the error. Note: only show one error message at a time. Showing several error dialogs at once is extremely cumbersome for the user. Alert dialogs appear with Inventory error messages when an input is invalid. If no exceptions occur: Add the new Inventory item to the InventoryList. When ORDERS Button is clicked or Hot key: O is used: Display only those items from the InventoryList that need re-ordering If the InventoryList is empty, display the message "No items to list. Add some." in the bottom message label. If there are items in the InventoryList, display each Inventory object that needs to be re- ordered by adding those Inventory objects to the TextArea on a separate line. If no items get added to the TextArea, display the message "No items to re-order." in the bottom message label. EXIT Button Displays an Alert dialog that asks if the user is sure that they wish to exit (Yes/No). If the user says Yes, exit the program. If the user says no, do nothin