Structure/Content autosave refactor

[GoogleCodeExporter]

Right now, we have a poor user interface for applying changes in the 
structure and content panes. The user double clicks a table cell to make a 
change, but that change is not saved until the user deselects the row. 

This can be confusing for quick edits and leads to saving more often than 
ideal for serious edits (esp. structure changes).

Proposed solution for Structure and Content:

 * drop current "save on deselect behaviour" all together
 * store edits in RAM instead of writing them immediately
 * add an "unsaved changes" dot on the far left side of every row which has 
been edited
 * when there are unsaved changes, slide down a bar near the top of the 
window with "Abandon Changes" and "Apply Changes" buttons.
 * all changes are saved (with a single query where possible) when the 
Apply Changes button is clicked.

In addition, the Content pane will have a new toggle button in the status 
bar "Autosave Changes" which is turned on by default. When enabled, 
autosave will apply all changes *instantly* once the NSTableView reports 
the user has finished editing (do not wait for the row to be deselected).

This is likely also a good chance to refactor some of our code.

Original issue reported on code.google.com by abhibeck...@gmail.com on 17 Feb 2010 at 12:53

[GoogleCodeExporter]

Issue 210 needs to be closed once this is finished.

Original comment by abhibeck...@gmail.com on 17 Feb 2010 at 12:56

[GoogleCodeExporter]

Issue 578 has been merged into this issue.

Original comment by stuart02 on 8 Mar 2010 at 4:50

[GoogleCodeExporter]

Original comment by stuart02 on 2 Jan 2011 at 11:30

• Added labels: Component-Logic, Priority-Medium
• Removed labels: Priority-High

[GoogleCodeExporter]

Issue 961 has been merged into this issue.

Original comment by rowanb@gmail.com on 29 Jan 2011 at 8:39

[GoogleCodeExporter]

Original comment by abhibeck...@gmail.com on 24 Mar 2012 at 1:09

• Added labels: Milestone-ReleaseFuture