dariusf / cs2103aug2013-w14-4j Goto Github PK

Allow history with up and down keys

Do the method for display of feedback

Current input is lost when the up key is pressed.

Make components of the UI resize accordingly when windows is resized

1. "add new task 2 from 11am to 12pm" only gives me an untimed task.

2. "add new task 2 from 10/10 11am to 11/10 12pm" gives me the following task: 
new task 2 12pm from 0:00 AM on Thu, 10/10/2013 to 11:59 PM on Fri, 11/10/2013

3. "add new task 3 from 11:00 am on 11/10/2013 to 12:00 pm on 12/10/2013" gives 
me the following task: new task 3 on (1) 11:00 AM on Fri, 11/10/2013 to 0:00 PM 
on Fri, 11/10/2013 or (2) 0:00 AM on Sat, 12/10/2013 to 11:59 PM on Sat, 
12/10/2013

Task objects require implementation of Comparable interface.

[deleted issue]

When user inputs help, the method: displayOnWindow should show help instead of 
tasks.

Implement the interface for feedback objects based on the class diagram 

Could possibly be done via a background process to capture input

One contains feedback from input and the other displays tasks

Undo is not working properly. The behaviour is weird.
It is very unpredictable hence it is very very hard to describe.
Undoing delete works, but undo add does not work, etc..

During class

Finalise architecture and start working on individual components.

The application still has to be started from the command line.

A possible intermediate solution could be use a batch/sh file.

After a certain command, gives help (in grey). Something like what google does.

If the person spells the wrong command, then it gets added as a task!

For example, tasks are allowed to be overdue

[2pm now]
add task 10am

=> adds overdue task

Change package name to lowercase

V0.1 of the Project Manual

Your project manual is to contain following sections:

Cover page: As before. Use the same template. Change '[V0.0]' to '[V0.1]' in 
the page header.

Credits: Acknowledgements of any third party materials used (if any). Omit this 
section if you did not use any third party materials.
User guide: As before. You may modify this section if you’ve changed the 
feature set since the last submission. It is ok if some of the features 
mentioned here are not implemented yet.

Developer guide: The intended audience for this document is an incoming 
developer (i.e. a new project member) that will depend on this document to tell 
how the product has been designed and implemented.That is, it will be used for 
‘onboarding’ new developers. The document contains just enough information 
required for that person to get into the project. The basic questions you 
should ask yourself when writing this document are:
What do we know about the system at this point?

Which part of that knowledge will be useful for a new project member?
What is the best way to pass that knowledge to the new member? Note that some 
information can be passed on in the form of code without any additional 
documentation.

Given below are some things you could consider including. Note that you are not 
required to include them all. Neither you are restricted to what is listed 
below.
Architecture
important APIs
Design descriptions (can include class diagrams, sequence diagrams, notable 
algorithms ...)
Code examples
Instructions for testing

Suggested max length for this section: 10 pages excluding appendices.

submission: Submit a single pdf file that contain all sections described above. 
File name is as before, but change ‘V0.0’ to ‘V0.1’. No need to submit 
to IVLE. Just push it to the ‘doc’ folder of your repo. We’ll pull it 
from there.

evaluation:  15++ points.

add task 3 by: 10:00pm
add task 3 by: 23:00

both results in an output of 10 AM. why is that?

When a new task is added, the display window should be scrolled to the bottom

Storage should retain the list of tasks. When i relaunch the application, all 
the tasks are gone.

More information to Logic

Get input and feedback to work.

By next Monday! 14th Oct

To describe:
1. design
2. implementation

- short intro: purpose of developer guide and target user (1-2 sentences)
-Architecture
-important APIs
-Design descriptions (e.g. class diagram, sequence diagrams, notable algorithms)
-Code descriptions (e.g. code examples, coding standards etc0
-Instructions for testing
-Development Infrastructure (e.g. IDE, Testing Framework, Versioning mechanism)
-known issues and future work* optional items to be left to v0.5
-Appendixes*

Need to include all error messages and status code in constants class

Add icon

I am including two new methods under Storage: isEmpty() and size()
I am also including another method called getDisplayString() in Feedback, which 
is used to return the string to display on the GUI. 

Finish up help strings

Program crashes when user tries to hit enter while the input is empty

Added toString() methods to Task and Feedback. Added getAdd() method to 
Storage. Added another field commandString to Feedback.

The first date will contain the current time while the second date will have 
current time + 1.

Eg add haha from 1/4/2013 to 2/4/2013 will return a task from 12.00pm to 1.00pm 
(or some other current time). Would be better if it returns time from 0000 to 
2359

What steps will reproduce the problem?
1. Construct the Task object with the no-argument constructor
2. Call the method setStartTime

Expected: Task set with specified start time and default end time
Actual: NullPointerException (i think)

This happens because the interval field is initialised to null. This is good 
because it plays well with the JSON parser. Allow me to suggest that a check be 
performed for a null object in the method. Delegating to the setInterval method 
may also be wise.

Consider what to display as feedback

Feasibility testing of proposed API

Capital letters removed are removed in the following execution:

Submit V0.1 by 11:59 pm 30/9/2013
Command2 [commandType=ADD_TASK, description=ubmit 0 1, 
deadline=2013-09-30T11:59:00.000+08:00, intervals=[], commandAttributes={}]
add Submit V0.1 by 11.59 pm 30/9/2013
Command2 [commandType=ADD_TASK, description=ubmit 0 1 by 11 59 pm 30/9/2013, 
deadline=null, intervals=[], commandAttributes={}]
add LKJHLKJHKjkhdk
Command2 [commandType=ADD_TASK, description=jkhdk, deadline=null, intervals=[], 
commandAttributes={}]

System testing 

Integrate UI with Logic

Deep copy for Task objects is required to properly implement undo.

Stuff like 10pm

After search the displayOnWindow works fine.
but after doing the search and we add, displayOnWindow is not showing all the 
tasks.

What is not working? Help!
so lame.
Anyway the parser doesn't support 'help'?

Command string shouldn't have backspaced characters.

Ability to launch with hotkey

I think it's weird to tell the user that you have this existing file that he 
can just go and edit.

Have fields instead of a hash map, and add getters and setters. The latter 
might be more important, because then we can get rid of the hash map later.

Task list is empty when application is launched. It is only when the first 
command is entered then the list will be displayed.

No scrollbar for the display fields

Eg:
add 1
add 2
add 3
add 4
Press up twice to get "add 2" then hit enter
Now hit up. The expected command is "add 4" but "add 1 is obtained"