iP:
A-BetterGui
tP:
A-BetterGui
docs
folder.
docs
folder and named Ui.png
exactly (even if the file format is not png
, name it png
)Ui.png
correctly and set up the product website correctly, you should be able to see your screenshot in the iP Showcase page (a link to the iP Showcase page is also available in the top navigation menu → Links) and you should be able to access the image using the link https://{your user name}.github.io/{repo name}/Ui.png
(e.g., https://johndoe.github.io/ip/Ui.png
).Soft deadline: midnight before the tutorial
Create a new jar file
Do the following smoke tests to ensure the jar file works (reason: a similar flow will be used when grading your iP).
Create a new release on GitHub (e.g., v0.2
) and upload the JAR file.
indicates an individual task (i.e., each team member has to do the task, graded individually) while indicates a team task (some or all members may do the work; graded for the whole team).
tP tasks progress is graded. Completing individual and team tasks are considered for grading the project management component of your project grade.
Most aspects of project progress are tracked using automated scripts. Please follow our instructions closely or else the script will not be able to detect your progress. We prefer not to waste admin resources processing requests for partial credit for work that did not follow the instructions precisely, unless the progress was not detected due to a bug in the script.
Milestone requirements are cumulative. The recommended progress for the mid-milestone is an implicit requirement for the actual milestone unless a milestone requirement overrides a mid-milestone requirement e.g., mid-milestone requires a document to be in a temp format while the actual milestone requires it to be in the proper format. Similarly, a requirement for milestone n
is also an implicit requirement for milestone n+1
unless n+1
overrides the n
requirement. This means if you miss some requirement at milestone n
, you should try to achieve it before milestone n+1
or else it could be noted again as a 'missed requirement' at milestone n+1
.
{team-id}.pdf
e.g., CS2103-T09-2.pdf
, and upload to LumiNUS.Recommended: Divide i.e., work related to the User Guide and the Developer Guidedocumentation work among team members equally; preferably based on enhancements/features each person would be adding e.g., If you are the person planing to add a feature X, you should be the person to describe the feature X in the User Guide and in the Developer Guide.
Reason: In the final project evaluation your documentation skills will be graded based on sections of the User/Developer Guide you have written.
Tutorial: tracing code
. In the description, add a 2-3 screenshots you took while at various points of the tutorial. You may close the issue soon after.tutorial-adding-command
, push to your fork, and create a PR from your fork to your team's repo. You may close the PR soon after.