By Jasmine Yeo Jia Min, A0185321L
This is an individual project done for CS2103T module in NUS. It is based on the basic duke structure provided by the module. Through guided incremental modifications and enhancements, this is the final product of my Duke individual assignment though it has many areas of improvement.
Adds task into the task list according to 3 types of labels: todo
, deadline
, event
.
todo
Tasks classified under todo
are basic tasks with no timestamps.
For example, cleaning the room or buying bedsheets.
Format: todo <TASK_DESCRIPTION>
Examples:
todo clean the room
todo buy bedsheets
deadline
Tasks classified under deadline
are tasks with a deadline.
For example, submit CS2103T quiz by 19 September 2019 at 23:59 or plan SEP module mapping by 30 September 2019 at 17:00.
Format: deadline <TASK_DESCRIPTION> /by <dd/MM/yyyy> <hh:mm>
Examples:
deadline submit CS2103T quiz /by 19/09/2019 2359
deadline plan SEP module mapping /by 30/09/2019 1700
event
Tasks classified under event
are tasks with a fixed timestamp.
For example, family gather at 15 December 2019 at 14:00 or job interview at 20 January 2020 at 10:00.
Format: event <TASK_DESCRIPTION> /at <dd/MM/yyyy> <hh:mm>
Examples:
event family gather /at 15/12/2019 1400
event job interview /at 20/01/2020 1000
delete
Removes task corresponding to the task’s index in the task list.
Format: delete <TASK_INDEX>
Examples:
Assuming the initial task list contains these tasks:
1. T - Read book
2. E - Project meeting (at: 02-12-2019 18:00)
3. T - Join sports club
4. D - Team submission (by 11-12-2020 23:59)
delete 1
Removes the first task T - Read book
from the task list according to the order of the initial task list.
The modified task list will look like the following:
1. E - Project meeting (at: 02-12-2019 18:00)
2. T - Join sports club
3. D - Team submission (by 11-12-2020 23:59)
delete 2
Removes the second task T - Join sports club
from the task list according to the order of the modified task list.
The modified task list will look like the following:
1. E - Project meeting (at: 02-12-2019 18:00)
2. D - Team submission (by 11-12-2020 23:59)
done
Marks the task corresponding to the given task’s index as completed, denoted by +
sign.
Format: done <TASK_INDEX>
Examples:
Assuming the initial task list contains these tasks:
1. T - Read book
2. E - Project meeting (at: 02-12-2019 18:00)
3. T - Join sports club
4. D - Team submission (by 11-12-2020 23:59)
done 1
Marks the first task T - Read book
from the task list as completed.
The modified task list will look like the following:
1. T + Read book
2. E - Project meeting (at: 02-12-2019 18:00)
3. T - Join sports club
4. D - Team submission (by 11-12-2020 23:59)
done 2
Marks the second task E - Project meeting (at: 02-12-2019 18:00)
from the task list as completed.
The modified task list will look like the following:
1. T + Read book
2. E + Project meeting (at: 02-12-2019 18:00)
3. T - Join sports club
4. D - Team submission (by 11-12-2020 23:59)
list
Lists all the tasks in the task list.
Format: list
Example of an expected outcome:
Here are the tasks in your list:
1. T - Read book
2. E - Project meeting (at: 02-12-2019 18:00)
3. T - Join sports club
4. D - Team submission (by 11-12-2020 23:59)
find
Finds task(s) corresponding to given keyword(s).
Format: find <KEYWORD>
<KEYWORD>
can be 1 or many.
Examples of <KEYWORD>
: book, find book, meeting and team meeting.
Examples:
Assuming the initial task list contains these tasks:
1. T - Read book
2. E - Project meeting (at: 02-09-2019 18:00)
3. D - Join sports club (by 15-10-2019 17:00)
4. E - Team Meeting (at 11-12-2020 23:59)
find meeting
Example of an expected outcome:
Here are the matching tasks in your list:
1. E - Project meeting (at: 02-12-2019 18:00)
2. E - Team meeting (at 11-12-2020 23:59)
find team meeting
Example of an expected outcome:
Here are the matching tasks in your list:
1. E - Team meeting (at 11-12-2020 23:59)
exit
Exits the program.
Format: exit
Example of the expected outcome:
Bye. Hope to see you soon!