Enhance ignored-files feature to distinguish between different type of ignored files

[scott-ainsworth]

Actual Behavior

Ignored files do not trigger an obvious warning or error state. The user must remember to manually check the log.

Expected Behavior

Not all ignored files should be treated equally. Many really don't matter (desktop.ini), but some cause problems. The status icon should reflect the difference.

Discussion

As noted in OwnCloud Architecture Appendix, files containing question marks are ignored, as are files in the ignored files list. In both cases, synchronization is considered successful even if files are ignored--see Issue #942 for the reasoning behind this.

Please consider the following case:

1. Use BibDesk to manage articles and reference material.
2. Use PocketBib for portability.
3. The BibDesk files are in ~OwnCloud; PocketBib synchronizes via WebDav.

Synchronization is truly simple, just open a BibDesk .bib file in PocketBib, wait a few seconds, and wa-la! synchronization is done.

However, BibDesk (and JabRef and others) name their files based on article titles, many of which contain question marks and colons. These files are silently ignored based on the reasoning in issue #942, which seems to work from the assumption that all (or at least most) of these can be ignored without harm--which is not the case for the BibDesk scenario above. But how can the harmful and benign be separated?

Suggestions

1. Files that match a pattern in the ignored files list are benign; others are errors.
2. In addition to Move SslErrorDialog into Application #1, enhance the ignored files list so that users can mark which files are ignored silently (but logged as they are now) and which produce a warning.
3. Enhance the status icon to reflect up to three states: success, warnings, and errors.
4. Enhance the log so that individual files flagged as warning or error can be marked "okay" and treated as ignored.

Client Configuration

Client version: 1.6.1 (build 539)
Operating System: OS X 10.9.4