Team Members:

Name: Stephanye Floyd
Email: [email protected]
Slack: stephiefloyd
GitHub: stephiefloyd

Name: Kayran Ehteshami
Email: [email protected]
Slack: kehtesha
GitHub: TremblingOdin

Name: David Siemens
Email: [email protected]
Slack: DavidSiemens
GitHub: DavidSiemens

Name: Ian Barney
Email: [email protected]
Slack: ianbarney96
GitHub: ianbarney

Name: Elliott Fries
Email: [email protected]
Slack: elliottfries
GitHub: elliottfries

Milestones

Milestone 1

The main objectives of this milestone is becoming accustom to the demands of the project and forming good team communication. We will first want to make sure all team members have all the necessary tools for working on the project installed and working properly on their own computers. From there we jump into to work on issues #192, #193, and #229. Issues #192 and #193 are related to one another and both focus on JavaFX so it seemed like a good idea to work on them together. These issues will give us a feel for what working on this project is like and what kind of workload we can take on for future milestones.

Milestone 2

This week Team 9 will focus on issue #259. We were pretty successful with completing our issues in Milestone 1, but we are encountering some odd errors with issue #192 and while we have it working the way we want, we still need to take care of those before we can close out the issue completely. Last week we worked on some client side gui issues and realized that there wasn't much the gui could do, so we thought this week we thought it might help to add some way to test the functionality of the gui by adding folders and files, so we created issue #259. Some of our team has spoken with team 12 and intends to aid them in completing issue #204.

Milestone 3

For milestone 3, we will continue working on issue #266 which involves finishing up the Directory Object so that we can change directory by double clicking on a folder. While we closed issue #192, the changes in the code made it obsolete so will be revising it by adding functionality to the search button. If we get done with these first two issues, we will work on Issue #270 which involves the ServerSideGui.

Milestone 4

For this week our team will focus on issue #296 making a directory tree for the left side of the gui. We can do this through working in Scene Builder as well as the clientAppController class. We may need to create a class for the files similar to the fileIcon class we use for the main directory display area. This Milestone will be complete when we have the tree showing up in the client gui.

Milestone 5

For this week our team will focus on issue #296 again, but, instead of just adding an element that can display the directory tree, we will be giving the gui's treeview functionality to show the directories in the tree. We will continue working in the clientAppController class to give the tree functionality. Additionally, we will continue work on issue #270 as it will be useful for implementing the directory tree. This Milestone will be complete when the client side gui displays the available directories and allows the user to interact with them. If we get done with both issues this week, we will assist in the database implementation. (issue #291)

Milestone 6

Our last milestone focused on issue #296, but we realized that the milestone was too broad and should be split into multiple issues that the team can tackle individually. So this week, we split #296 into #318, #319, and #321. With #318 we want to create a javabean in order to populate the directory tree with each unique database. Issue #319 deals with actually populating the tree by looping through each individual bean so that the tree is displayed once the GUI is loaded. Finally, with #321, we intend to create event handlers that allow users to access the contents of the various directories through mouse clicks. This milestone will be considered complete when all three of these issues have been implemented. Additionally, issue #296 will be considered complete once these three issues are completed.

Milestone 7

This week we will continue to focus on implementing a directory tree into the GUI. (issue #296) Last week, we found it helpful to split that issue into several smaller issues, and we will continue that trend this week. We will continue working on issues #319 and #321, but we will focus on some smaller issues as well. Issue #319 has some implementation, but has not been completed yet because nothing is being displayed to the GUI. We need to implement and observable list to display the contents of the tree. Issue #343 was created to detail that implementation. Issue #321 deals with event handlers so that the tree can be interacted with, but because the tree is not displayed in the GUI yet, we will carry this issue into this week. Finally, we also created issue #342 as we realized we need our own set of images to display icons next to each element of the tree. This issue is the last thing on the agenda because the tree can be implemented without them and is mainly aesthetic. We created a getImages( ) method last week with some code in preparation for this issue.

Milestone 8

This week, we will continue work on the directory tree. (issue #296) Last week, we got the tree to display elements within the gui and created an image to use with the tree. With that being said, we are in a good position to populate the tree with the projects directories. (issue #319) We plan on looping through the available directories and creating a TreeItem for each individual directory. This issue will be completed once the client side gui displays each directory. If issue #319 is finished this week, we will begin working on creating event handlers for the tree to handle user interaction. (issue #321)

Milestone 9

This week, we will be continuing and, hopefully, be finishing up issue #296. With the tree displaying the available directories, we will now start creating event handlers for the tree. (issue #321) We will be creating an event handler that will display the content of a directory when clicked on. For example, if src is clicked on in the tree, edu will display underneath src. This will continue down until there is nothing more to display. This issue will be considered complete once when the event described above is functioning properly. If we finish up the event handlers this week, we will implement error handling where the method loops through and prints out the directories to the tree, that way potential crashes can be avoided. (issue #366)

Milestone 10

This week will be working issues #374, #296, and #375 In issue #374, we will be creating a TreeItem class to help with event handling. As it stands currently, the tree displays the upper level directories, but does not display the contents. This class will help with that problem. Issue #296 is about creating a working directory tree, so that issue will be considered complete once #374 is completed. Finally, issue #375 was created to get the treedev branch ready for merge. The team will make sure the code is sufficient for merge and commented appropriately.