In order to implement this we will need to do following:
Instead of creating date label when main label is missing we will need to show non-editable date label when main label is missing. We already have date column in DB (see insertDate) therefore DB side is not affected.
Changing over-time is more complicated to implement. To avoid slowness in calculator we might take two approaches:
1) Assume that user will close and open calculator frequently and update date information only on start;
2) Use timer and update date information each 5 minutes (I think that's delta user will tolerate).
As well I highly recommend reusing the fact that history is always go date-by-date - our list is always consistent. Therefore when first entry older than one week is met we can stop updating text of dates because exact date is used in such cases.
In order to implement this we will need to do following:
Instead of creating date label when main label is missing we will need to show non-editable date label when main label is missing. We already have date column in DB (see insertDate) therefore DB side is not affected.
Changing over-time is more complicated to implement. To avoid slowness in calculator we might take two approaches:
1) Assume that user will close and open calculator frequently and update date information only on start;
2) Use timer and update date information each 5 minutes (I think that's delta user will tolerate).
As well I highly recommend reusing the fact that history is always go date-by-date - our list is always consistent. Therefore when first entry older than one week is met we can stop updating text of dates because exact date is used in such cases.