Tracking GUI changes to activity data

[tmillross]

#6 highlights that the user should be able to make changes through AB confidently, in the knowledge that mistakes can be identified and recovered from. To satisfy this general class of functionality. Some preliminary ideas for tracking user data changes and giving them visibility of all edits performed through AB have been added as separate issues: Interface Cues #11, Logfile #12, 'Revert changes' button #13.
Ideas listed are complementary rather than mutually exclusive from my perspective at this time. They each offer different advantages for common use-cases. The only downside is due to coding implementation time, and perhaps a slightly increase of interface detail/complexity.
BW2 is of course also version control friendly. This could satisfy the data tracking requirements of some users in a way which overlaps with the options described in those issues. But AB users conducting LCAs often may not run VC on their data directories. Perhaps they should be encouraged to do so through AB?

[aj-9636]

Activity data changes: color coding changed data #7