cs2103aug2016-w11-c2 / main Goto Github PK

Feedback had been recorded as comments on the PR: nus-cs2103-AY1617S1#117

so that I can update the task details (in particular the title) to reflect the latest change

Check what I have entered and redo actions easily

Tasks should be nicely laid out so that the user can read the information quickly.
Should reflect the deadline/start time/end time (month + day + time ), the status of completion (completed/uncompleted) and eventually if it is overdue or coming
Add colors to reflect the changes and update spacing

Follow the documentation in the sample project in terms or organization, level of details, etc.
Update User Guide to match what you plan to deliver at V0.5
Update Developer Guide to match your current design or the design you plan to have at V0.5

Note: Please merge Weiguang/Justin PR first
Due by Monday 7pm (do 2101 simultaneously)

Readme

• Update our UI screenshot (Weiguang)
• Remove link to Learning outcome (Weiguang)

User guide

• Add introduction from CS2101 (Weiguang)
• Add FAQ (Justin)
• Add command summary (Rachael)

User guide features

• Vishnu: adding a task, scheduling, undo
• Rachael: renaming, deleting, mark and unmarking tasks
• Weiguang: List, find, keyboard shortcuts, help
• Justin: General command format, alias, unalias commands, specifying a data storage location (is load added as well?)

Developer guide
(individually graded, advice is one seq diagram, one class diagram, with justifications)
(might be a good idea to look at collate)
(decide on how we want to store previously entered commands for scrolling and separately for undo which will actually affect the diagrams)
Follow: https://github.com/collate/collate/blob/master/docs/Developer-Guide.md (Notable API table)

Weiguang

• Introduction
• Setting up
• UI component (add your new classes, consider using inheritance for task card)

Justin

• Appendix A: user stories
• Appendix D: glossary
• Storage component
• Common classes (the description is non-existent)

Vishnu

• Appendix B,C: use cases and non-functional requirement (maybe use cases should be embedded in developer guide)
• Add product survey for Omnifocus?
• Logic component (update design and consider making parser abstract, with date time and individual command parsers after refactoring)
• Implementation

Rachael

• Appendix E: product survey
• High level design
• Model component
• testing and dev ops

Active branch: Update-user-guide-for-v0.3

If today is Monday and the command is write "Add something from Wed 10 am to 12pm" it should parse as: From: Wednesday 10am To: Wednesday 12pm. Instead of To: Monday 12pm

Decide on what needs to be done soon

I will do a final check on the deadline

For example,

When i type "add", which is a wrong command,
The cursor will reset to the starting position e.g. "|add" instead of "add|"

Tutor feedback: We should be using a logging framework. The built-in java.logger is a suitable one. Have a standardised decision on when to use each kind of logs {minor, major, critical, etc}.

Input: "renam 1 toThis"
Output: "We don't recognised that command. Did you mean 'rename'"?

This is a major blocker - preventing #43 from being merged.

LogicManagerTest.java is getting bloated. Let's move the tests for each command out to its own class. AddCommandLogicTest.java, UndoCommandLogicTest.java, etc.

so that I can easily correct any accidental mistakes in the last command

Allow user to add command "drop by school" without throwing an invalid add/date time format exception. (Options: use -by or /by, ignore words enclosed within inverted commas, check if word after by is a time)

It's a UI bug.

I know this is not descriptive. I'll update this take with details soon.

Hey @rachx, could you update the Github projects so that it's updating to what v0.3 should be?

Just add tasks to the 'Next' or 'Current' so that it contains every task we want to achieve by Wednesday tutorial.

Thanks, just wanna know how many tasks left for the deadline this week.

Close this issue when done.

• Readme.md has addressbook's UI shot. Please change this asap.
• Learning Outcomes links to addressbook's outcomes. Not sure if this is relevant to your app.

View my tasks grouped by their state of completion.
Review my completed tasks and decide on what I should do next

(Ideally, the lists should come with count/statistics)

Hey @rachx @INCENDE @fanwgwg, could you update the v0.2 release with notes about what features our app supports right now? Thanks!

So that I can keep track of events with defined start and end dates (or deadlines)
Similarly, I should be able to edit and remove start/end time/deadlines so that I can respond to changes accordingly.

• Implement DateTimeParser
• Implement Schedule Command

Note

• Cater for the possibility of task description containing keywords such as ‘from’ ‘to’. e.g., The user can add the task ‘watch day after tomorrow’ without the software interpreting ‘tomorrow’ as the day for the task.
• Support floating tasks, tasks with deadlines and event with start and end times
• Consider using PrettyTime time parser: http://www.ocpsoft.org/prettytime/nlp/

Right now, prepareAdd, prepareDelete etc are all in the same class. Consider having individual parsers.
Check and simplify common regex.
Remove StringUtils isUnsignedInt?

Keep track and update the status of completion of my tasks

• Enalbe result popup to resize automatically according to the length of result message
• Create seperate panels to result list of different categories, like completed, overdue, upcoming...

Customise the feedback messages for Agendum
Error message for Add to be updated as well
Make it more user friendly e.g. what task indexes are invalid, what tasks are deleted

Hey @INCENDE @fanwgwg @rachx,

I had to do a rebase that this caused all the commits in our fork to get regenerated. Please delete your local copy of the repo and clone it again from Github.

Sorry I'll try to make sure this action wouldn't be needed again

• Only care about events with start&&end time
• On sync on, it should push up all tasks
• CRUD should work from Agendum -> GCal
• Bonus point: CRUD backwards from GCal -> Agendum
• Bonus point: In Gcal, give a "alert" 10mins before end time

so that I can enter commands faster
I should also be able to remove/edit these short hand commands to update them to commands that are more suitable

https://github.com/CS2103AUG2016-W11-C2/main/blob/master/docs/UserGuide.md#adding-a-person-add

And some other instances

Easily locate the raw text file for editing and potentially syncing the file to a cloud storage service

At the moment it's all over the place

@rachx @burnflare @fanwgwg are we going to remove tags from our project entirely?

So that I can easily find a task without going through the entire list (even if I only remember a few key words)

Some improvements

• Make search case insensitive

In the jar release

If i type the help command multiple times after i open help, App cannot be shutdown.
Multiple instances of help will appear each time i close each help.

I will need to enter fewer commands if I am making similar changes

Refer to instructions when I forget how to use the app
(Link to the Github user guide or have a short summary similar to address book level 3)