Networked Graphics MV3500 Course Assignments using Netbeans
Initialization and Refresh
To submit homework via Netbeans to the gitlab server you will first need to clone a copy of the course repository at
Use Netbeans to upload/update your homework assignments as follows:
- context menu: Git > Remote > Pull from Upstream to first always ensure you update your repository
- Making sure: Did you perform step one and pull git to refresh your local version?!
- Select file of interest in Netbeans tab for Files
- context menu: Refactor/Rename and take spaces out of file name (gets wacky on various operating systems, email etc.)
- Ensure Java classes and source files start with your last name
- context menu: Run file(s) to test
- context menu: Git > commit; provide comment documenting the change
- Verify that the entry in Files tab goes from green to black, indicating you have committed to your local repository.
- context menu: Git > Remote > Push to Upstream
Adding and Editing Your Files
All MV3500 cohorts have source code collected under a common Netbeans project.
- Find your current cohort src subdirectories, for example
- assignments / src / MV3500Cohort2024JulySeptember (we are here!)
- You can look at earlier cohort submissions, for example
- Locate the correct subdirectory (for example homework1) to put your files.
- Name all of your files starting with your last name, e.g. LastnameProgram.java LastnameScreenshot.png etc.
- Be sure that names match for LastnameProgram.java and the class name, i.e. public class LastnameJava
- Be sure to start each .java source file with correct package name, for example:
- package MV3500Cohort2022MayJune.homework1;
- package MV3500Cohort2022MayJune.homework2; etc.
- Add a copy of package-info.java file to your directory. If you use NetBeans to copy, then it helpfully performs a rename refactoring and the file's package name is correct.
- Check the javadoc by going to build.xml and running target javadoc.custom
- Be sure to Commit (with description) and Push Upstream, as discussed above.
After committing and pushing, you can now verify that your files are been shared by checking the website:
Clarity is key. Good practices
- Note your changes in a README.md file.
- For nontrivial projects, you will also need to add a UML flow diagram and a UML timing sequence diagram.
- Visio has templates for UML diagrams, drawings with another tool or hand sketches are fine.
References
- Netbeans and Using Git Support with tutorial video, version 8.2
- GitLab Flavored Markdown (GFM) and Markdown Cheatsheet
- UML Sequence diagram on Wikipedia
- Wireshark network protocol analyzer