gabrielseow / duke

User Guide

Welcome to Duke, a simple and easy-to-use chat bot that will help manage your tasks.

Features

Add new tasks

Duke allows you to add new Events, Deadlines or To Do tasks to your list of tasks.

Mark a task as completed

Once a task is added, you can then update Duke once you have completed the task.

Find tasks by keyword

You can also filter tasks according to the keyword you input.

List all tasks

You may also enter a command and Duke will list your current tasks.

Delete a task

Duke also allows you to delete a task when you no longer need it.

Usage

help - Display user commands

The help command brings up a list of tasks the user can use in Duke.

Expected outcome:

    Welcome to Duke. The following are a list of possible commands:
    
    todo <description> --- Creates a ToDo task
            
    deadline <description> /by <dd/mm/yy hhmm> --- Creates a Deadline task
            
    event <description> /at <dd/mm/yy hhmm> --- Creates an Event task
            
    list --- Lists all tasks
            
    done <task number> --- Mark a task as completed
            
    delete <task number> --- Delete a task
            
    help --- Display the help menu
            
    bye --- Exit Duke

todo - Add a To Do task

Example of usage:

todo CS2100 Tutorial

Expected outcome:

Got it. I have added this task:
 [T][✗] CS2100 Tutorial
 Now you have 1 tasks in the list.

event - Add an Event task

Example of usage:

event Sister's Birthday /at 20/10/19 1900

Expected outcome:

Got it. I have added this task:
 [E][✗] Sister's Birthday (at: 20th of October 2019, 7pm)
 Now you have 1 tasks in the list.

deadline - Add a Deadline task

Example of usage:

deadline CS2103T Post Lecture Quiz /by 30/9/19 2359

Expected outcome:

Got it. I have added this task:
 [D][✗] CS2103T Post Lecture Quiz (by: 30th of September 2019, 11.59pm)
 Now you have 1 tasks in the list.

done - Mark a task as complete

The user also inputs the number of the task he completed.

Example of usage:

done 2

Expected outcome:

Nice! I've marked this task as done:
 [D][✓] CS2103T Post Lecture Quiz (by: 30th of September 2019, 11.59pm)

find - Find tasks containing a keyword

The user also inputs the keyword that he is searching for.

Example of usage:

find CS2100

Expected outcome:

Here are the matching tasks in your list:
 1.[T][✗] CS2100 Tutorial

list - List all tasks in Duke

Expected outcome:

Here are the matching tasks in your list:
 1.[T][✗] CS2100 Tutorial
 2.[E][✗] Sister's Birthday (at: 20th of October 2019, 7pm)
 3.[D][✓] CS2103T Post Lecture Quiz (by: 30th of September 2019, 11.59pm)

delete - Delete a task in Duke

The user also inputs the number of the task to delete.

Example of usage:

delete 1

Expected outcome:

Noted. I've removed this task:
[E][✗] Sister's Birthday (at: 20th of October 2019, 7pm)
Now you have 2 tasks in the list.

bye - Close Duke

Exits the Duke application.

duke's Issues

Feedback on week 5 project progress for gabrielseow

Leftovers from the previous week

• A version tagged Level-1 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-2 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-3 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-4 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-5 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-6 is in the repo(:exclamation: try to do by next milestone)

• A version tagged A-MoreOOP is in the repo(:exclamation: try to do by next milestone)

• A version tagged A-JUnit is in the repo(:exclamation: try to do by next milestone)

• A version tagged A-Jar is in the repo(:exclamation: try to do by next milestone)

• A version tagged A-Gradle is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-10 is in the repo(:exclamation: try to do by next milestone)

• Fewer than two branches detected in the repo(:exclamation: try to do by next milestone)

• You have added comments on at least two PRs(:exclamation: try to do by next milestone)

Progress of this week

• At least 2 PRs are in your fork(:exclamation: try to do by next milestone)

• You have no tag from categories B/C/D(:exclamation: try to do by next milestone)

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-09-12 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

Feedback on week 7 project progress for gabrielseow

Leftovers from the previous week

• A version tagged A-TextUiTesting is in the repo (:heavy_check_mark: well done!)

• A version tagged Level-10 is in the repo (:heavy_check_mark: well done!)

• At least two branches are in the repo branch-A-Assertions branch-A-CodeQuality branch-A-CodingStandard branch-A-JavaDoc branch-Level-9 gradle master (:heavy_check_mark: well done!)

• A version tagged C-Help is in the repo (:heavy_check_mark: well done!)

• At least 2 PRs are in your fork (:heavy_check_mark: well done!)

• docs/REAME.md is updated (:heavy_check_mark: well done!)

• docs/Ui.png has been added (:heavy_check_mark: well done!)

• a jar file has been released in the past week (:heavy_check_mark: well done!)

• product website available at http://gabrielseow.github.io/duke (:heavy_check_mark: well done!)

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-01 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

Feedback on week 4 project progress for gabrielseow

Leftovers from the previous week

• A version tagged Level-1 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-2 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-3 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-4 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-5 is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-6 is in the repo(:exclamation: try to do by next milestone)

• A version tagged A-MoreOOP is in the repo(:exclamation: try to do by next milestone)

• A version tagged A-JUnit is in the repo(:exclamation: try to do by next milestone)

• A version tagged A-Jar is in the repo(:exclamation: try to do by next milestone)

• Fewer than two branches detected in the repo(:exclamation: try to do by next milestone)

• A pull request exists from your repo to the module repo(:heavy_check_mark: well done!)

Progress of this week

• A version tagged A-Gradle is in the repo(:exclamation: try to do by next milestone)

• A version tagged Level-10 is in the repo(:exclamation: try to do by next milestone)

• You have added comments on at least two PRs(:exclamation: try to do by next milestone)

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-09-05 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

Feedback on week 6 project progress for gabrielseow

Leftovers from the previous week

• A version tagged Level-1 is in the repo(:heavy_check_mark: well done!)

• A version tagged Level-2 is in the repo(:heavy_check_mark: well done!)

• A version tagged Level-3 is in the repo(:heavy_check_mark: well done!)

• A version tagged Level-4 is in the repo(:heavy_check_mark: well done!)

• A version tagged Level-5 is in the repo(:heavy_check_mark: well done!)

• A version tagged Level-6 is in the repo(:heavy_check_mark: well done!)

• A version tagged A-MoreOOP is in the repo(:heavy_check_mark: well done!)

• A version tagged A-JUnit-incomplete is in the repo(:heavy_check_mark: well done!)( :warning: The tag is slightly different from the expected value (A-JUnit). Please follow the exact tag in future )

• A version tagged A-Jar is in the repo(:heavy_check_mark: well done!)

• A version tagged A-Packages is in the repo(:heavy_check_mark: well done!)

• A version tagged A-Gradle is in the repo(:heavy_check_mark: well done!)

• A version tagged Level-10 is in the repo(:exclamation: try to do by next milestone)

• A version tagged A-CheckStyle is in the repo(:heavy_check_mark: well done!)

• Fewer than two branches detected in the repo(:exclamation: try to do by next milestone)

• You have no tag from categories B/C/D(:exclamation: try to do by next milestone)

• At least 2 PRs are in your fork(:exclamation: try to do by next milestone)

Progress of this week

• docs/REAME.md is updated(:exclamation: try to do by next milestone)

• docs/UI.png has been added(:exclamation: try to do by next milestone)

• a jar file has been released in the past week(:exclamation: try to do by next milestone)

• product website available at http://gabrielseow.github.io/duke (:exclamation: try to do by next milestone)

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-09-19 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}