As an agile FileMaker Developer I want to be able to see in fmLogAnalyser fast so that I can focus on fixing breakages rather than

[mrwatson-de]

User Story

With time fmLogAnalyser gets slower and slower, since the import.log file gets larger and larger.

This is wasted time, and occasionally one is distracted by making a copy of the import.log file and deleting or emptying it.

A FURTHER related functionality is the desire to archive the import.log file, so that it is possible to later analyse how import errors have been handled over time.

Acceptance Criteria

Given I am an agile FileMaker developer, wanting to archive my import.log files on a regular basis in order to keep performance up
When I select the option in fmLogAnalyser to archive my logs, when the processing time drops under, say, 4 seconds
Then when I load the log the load time is measured
And when the load time is greater than my chosen 4 seconds a flag is set, so that
when fmLogAnalyser is closed, or when I load the log again the file is archived before being imported.

Note: This is my first issue formatted in Agile user-story style, inspired from GitHub Best Practices: Taking Issues from Good to Great ... and in need of improvement