CS2113/T - Admin: iP: Week 6

Add Increments as parallel branches: Level-6, Level-7
Add Increment: A-Jar

1 Add Increments as parallel branches: `Level-6`, `Level-7`

Practice using parallel git branches, as explained below:
1. First, do Level-6 in a branch named branch-Level-6, but do not merge it.
2. Then, go back to the master branch and implement Level-7 in a separate branch named branch-Level-7.
3. Now, go back to the master branch and merge the two branches one after the other.
  If there are merge conflicts, you'll have to resolve them first.
4. As before, tag the commit (in the master branch, after merging) that achieves the respective deliverable, and push to your fork.
As before, Merge without a fast-forward so that git creates a separate commit for the merge.
Advanced git users: do not delete the branch after merging.

Duke Level-6: Delete

Level 6. Delete

Add support for deleting tasks from the list.

Example:

list
    ____________________________________________________________
     Here are the tasks in your list:
     1.[T][✓] read book
     2.[D][✓] return book (by: June 6th)
     3.[E][✗] project meeting (at: Aug 6th 2-4pm)
     4.[T][✓] join sports club
     5.[T][✗] borrow book
    ____________________________________________________________

delete 3
    ____________________________________________________________
     Noted. I've removed this task: 
       [E][✗] project meeting (at: Aug 6th 2-4pm)
     Now you have 4 tasks in the list.
    ____________________________________________________________

When implementing this feature, you are also recommended to implement the following extension:

A-Collections

↳ Use Java Collections classes

Use Java Collections classes for storing data. For example, you can use an ArrayList<Task> to store the tasks.

Duke Level-7: Save

Level 7. Save

Save the tasks in the hard disk automatically whenever the task list changes. Load the data from the hard disk when Duke starts up. You may hard-code the file name and location e.g., [project_root]/data/duke.txt

The format of the file is up to you. Example:

T | 1 | read book
D | 0 | return book | June 6th
E | 0 | project meeting | Aug 6th 2-4pm
T | 1 | join sports club

If you use file paths in your code,

remember to use relative paths rather than absolute paths such as C:\data. If not, your app can cause unpredictable results when used in another computer.
remember to specify file paths in an OS-independent way. If not, your app might not work when used on a different OS.

Your code must i.e., if the file is missing, your code must creat ithandle the case where the data file doesn't exist at the start. Reason: when someone else takes your Duke and runs it for the first time, the required file might not exist in their computer. Similarly, if you expect the data file to be in as specific folder (e.g., ./data/), you must also handle the folder-does-not-exist-yet case.

2 Add Increment: `A-Jar`

In case this increment does not require any code changes, you may tag the commit at which this was achieved as A-Jar (even if that commit has another tag already).
Upload the jar file to your fork as explained in the panel below.

Duke A-Jar: Create a JAR File

A-Jar

↳ Package the App as a JAR file

Package the app as an executable JAR file so that it can be distributed easily.

You can assume the user will run the jar file in the following way only:

Copy the jar file into an empty folder
Open a command window in that folder
Run the command java -jar {filename}.jar e.g., java -jar Duke.jar (i.e., run the command in the same folder as the jar file)

Refer to the tutorial Working with JAR files @SE-EDU/guides to find how to create JAR files.

Do not commit the JAR file created. Instead, you can make the JAR file available in the following manner.

Go to your fork on GitHub and create a new release.
In the page where you fill the details of the release,
- give an appropriate version number e.g., v0.1
- attach the JAR file where it says Attach binaries by dropping them ....

iP: Week 6