11 or above installed on your computer.duke.jar here.duke.jar to the folder you want to use as the home folder for Duke.duke.jar to launch Duke.Duke supports the creation of three different types of tasks: todo, deadline and event. todo allows the user to give a description to the task while deadline and event allows the user to specify a date in which the task must be completed by or at respectively.
Duke is able to list the tasks the user has added. Duke displays the type of the task, description of the task and status of the task.
Duke allows the user to mark a task as done once the user has completed the task.
Duke is able to delete tasks that has already been added.
Duke can find tasks that include a certain string in its description and list them for easy access.
Duke can undo the last command that made a change to the task list.
Words in UPPER_CASE are parameters that should be provided by the user. All parameters are compulsory.
todo - Adding a ToDoAdds a ToDo task to the task list.
Format:
todo DESCRIPTION
Example of usage:
todo tutorialExpected outcome:
Got it. I've added this task:
[T][✗] tutorial
deadline - Adding a DeadlineAdds a Deadline task to the task list.
Format:
deadline DESCRIPTION /by YYYY-MM-DD
Example of usage:
deadline submit assignment /by 2020-09-16Expected outcome:
Got it. I've added this task:
[D][✗] submit assignment (by: Sep 16 2020)
event - Adding a EventAdds a Event task to the task list.
Format:
event DESCRIPTION /at YYYY-MM-DD
Example of usage:
event finals /at 2020-12-02Expected outcome:
Got it. I've added this task:
[E][✗] finals (at: Dec 02 2020)
list - Listing all tasksLists all tasks with their respective indexes currently in the task list.
Format:
list
Example of usage:
todo tutorialdeadline submit assignment /by 2020-09-16event finals /at 2020-12-02listExpected outcome:
1. [T][✗] tutorial
2. [D][✗] submit assignment (by: Sep 16 2020)
3. [E][✗] finals (at: Dec 02 2020)
done - Marking a task as doneMarks a task as done. Best used after list to get the indexes of tasks.
Format:
done INDEX
Example of usage:
todo tutorialdeadline submit assignment /by 2020-09-16event finals /at 2020-12-02done 1Expected outcome:
Nice! I've marked this task as done:
[T][✓] tutorial
delete - Deleting a taskDeletes a task from the task list. The rest of the tasks after the deleted tasks will have their indexes shifted up by one. Best used after list to get the indexes of tasks.
Format:
delete INDEX
Example of usage:
todo tutorialdeadline submit assignment /by 2020-09-16event finals /at 2020-12-02done 1delete 1Expected outcome:
Noted. I've removed this task:
[T][✓] tutorial
find - Finding a taskFinds tasks whose description contain the keyword provided. The indexes of the tasks found correspond to their actual index i.e. the indexes provided in list.
Format:
find KEYWORD
Example of usage:
todo tutorialdeadline submit assignment /by 2020-09-16event finals /at 2020-12-02done 1delete 1find finalsExpected outcome:
Here are the matching tasks in your list:
2. [E][✗] finals (at: Dec 02 2020)
undo - Undoing previous commandReverts the task list to the last state that made changes to the task list i.e. todo deadline event done delete. All subsequent undo commands continues to revert the state up to a maximum of four times. The first change made to the task list after running the application for the first time cannot be undone.
Format:
undo
Example of usage:
todo tutorialdeadline submit assignment /by 2020-09-16event finals /at 2020-12-02done 1delete 1undolistExpected outcome:
1. [T][✓] tutorial
2. [D][✗] submit assignment (by: Sep 16 2020)
3. [E][✗] finals (at: Dec 02 2020)
Q: How do I transfer duke to another computer?
A: Copy the folder duke.jar is in to the other computer. Alternatively, just copying duke.jar and the folder data is enough.
todo DESCRIPTION
deadline DESCRIPTION /by YYYY-MM-DD
event DESCRIPTION /at YYYY-MM-DD
list
done INDEX
delete INDEX
find KEYWORD
undo