Skip to content
Snippets Groups Projects
Select Git revision
  • master default
1 result
Compare
user avatar
[Terry N.] NB 23 updates?
git authored
e4558695
History
user avatar e4558695
History
Name Last commit Last update
..
images
nbproject
pduLog
src
README.md
ReportingForDuty.md
build.xml
README.md

Networked Graphics MV3500 Course Assignments using NetBeans

Initialization and Refresh

To submit homework via NetBeans to the gitlab server you will first need to use Git to clone a copy of the course repository at

Use NetBeans to upload/update your homework assignments as follows:

  1. context menu: Git > Remote > Pull from Upstream to first always ensure you update your repository
  2. Making sure: Did you perform step one and pull git to refresh your local version?!
  3. Select file of interest in NetBeans tab for Files
  4. context menu: Refactor/Rename and take spaces out of file name (gets wacky on various operating systems, email etc.)
  5. Ensure Java classes and source files start with your last name
  6. context menu: Run file(s) to test
  7. context menu: Git > commit; provide comment documenting the change
  8. Verify that the entry in Files tab goes from green to black, indicating you have committed to your local repository.
  9. context menu: Git > Remote > Push to Upstream

Adding and Editing Your Files

All MV3500 cohorts have source code collected under a common NetBeans project.

  1. Find your current cohort src subdirectories, for example
  2. You can look at earlier cohort submissions, for example
    1. assignments / src / MV3500Cohort2022MayJune
    2. assignments / src / MV3500Cohort2021JulySeptember
    3. assignments / src / MV3500Cohort2020JulySeptember
    4. assignments / src / MV3500Cohort2019JulySeptember
    5. assignments / src / MV3500Cohort2018JulySeptember
    6. assignments / src / MV3500Cohort2018JanuaryMarch
  3. Locate the correct subdirectory (for example homework1) to put your files.
  4. Name all of your files starting with your last name, e.g. LastnameProgram.java LastnameScreenshot.png etc.
  5. Be sure that names match for LastnameProgram.java and the class name, i.e. public class LastnameJava
  6. Be sure to start each .java source file with correct package name, for example:
    • package MV3500Cohort2022MayJune.homework1;
    • package MV3500Cohort2022MayJune.homework2; etc.
  7. 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.
  8. Check the javadoc by going to build.xml and running target javadoc.custom
  9. 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