kronenpj / iqapps-broken Goto Github PK

The time chooser should "snap" to the chosen alignment interval.  That
functionality isn't provided by the base Android class, but I have seen it
in another application.

The source code for the TimePicker class is available, so this should be
relatively easy, though I'm not sure simply extending the class will be enough.

The database is currently stored under
/data/data/com.googlecode.iqapps.IQTimeSheet/databases, but that area is
inaccessible except by the application.  The database should be able to be
stored on the SD card as well.

Provide an option to address the potential data inconsistency where a task
was never ended properly.  This should be much less of a problem than it
once was, but it's still a concern for me.

What steps will reproduce the problem?
1. Not applicable.  Enhancement Suggestion.

What is the expected output? What do you see instead?
A built-in "break/lunch" category that will keep track of how long you are on 
break/lunch for, but without adding that time to the hours worked for the day.  
You can currently make a lunch/break charge code, but the time on break will 
count towards total number of hours worked for the day.

What version of the product are you using? On what operating system?
v2012.beta1 on Android 2.3.4.

Please provide any additional information below.

Find anything that could be specific to developer's situation and make into a 
generalized preference.

Past example is hard coding 6-minute intervals rather than allowing 
even-multiples of an hour to be selected in a preference.

Adjust time on previous/next tasks when one is being edited to maintain
continuity of time worked.  Eg: When a task change was forgotten until 20
minutes later, switching to task two and editing the start time should also
adjust the end time of the previous task.

Re-learn the current ADK testing methodology and implement.  Increase coverage 
substantially.

Information stored in the database is not human-readable.  Even if the
contents of the database are available, timestamps in milliseconds since
1/1/1970 isn't a useful timestamp to a human.  Create an application that
can display a useful form of the data, edit that data and perhaps produce
reports.

More of a toy thought.  Chime when the # hours/day has elapsed and when the # 
hours/week has passed.  Allow for different and user selectable notification 
sounds for each.

Probably just a bug where the report is including open activity from current 
day, but need to investigate.

Clear time sheet table for previous year.
Clear time sheet table for current year.
Clear time sheet table for given start and end dates.
Purge all time sheet data.
Purge all tasks.
Purge inactive tasks.

What steps will reproduce the problem?
1. Edit a task.
2. Change the date to February in Date Chooser.
3. Accept change.

What is the expected output? What do you see instead?
Expected: Date displayed in edit screen shows February.  Instead it shows
January.

Please use labels and text to provide additional information.

Basic import/export of tasks.  Probably omitting split associations unless some 
way can be invented.
Basic import/export of time card data.  Convert clocking data to date and time 
with timezone (when implemented).  Insert task description in place of numeric 
reference.  Import should create tasks as needed.

Some method should be provided to backup and restore the database to
/sdcard/ so that people without rooted phones can secure their data.

When a clocking is changed by editing the task, when returning to the main 
list (with the green buttons), sometimes the task highlighted is incorrect 
because it changed position in the database, but not yet on the screen.  
Probably just need to refresh the screen, but it will take extra cycles 
every time.

The times in the header do not update except on application start.  Make
this update more frequently either by background thread or when activities
complete.

What steps will reproduce the problem?
1. Probably run current branch development version.
2. Delete some tasks.
3. Start a new task
4. Open day report, see currently open task isn't there.
5. Go to previous day in day report, see task there with negative time.

What is the expected output? What do you see instead?
Task currently active should be on current day.

This is most likely due to a recent, as yet unpublished set of changes.  
Putting this here to keep track of it.