Opening a document via content hub doesn't actually open it

[Cris Dywan]

When I open documents from another app in the document viewer they are imported but never actually open unless I manually pick it from the list of documents.

[Stefano Verzegnassi (verzegnassi-stefano)]

This is actually the behaviour used also in gallery-app. I decided to handle imported document in this way in order to provide a consistent behaviour with the rest of the platform.

To be fair, there's an issue here: gallery-app has some animations that highlight the entry of the imported image as side-effect. It's still not possible to archive this in docviewer beacuse the FileWatcher we use is still in an early stage.

Also, there are two user scenarios while handling with content-hub import:
1) A third party application that wants to store a document in the user's folder. In this case, opening automatically a document is an unwanted behaviour, IMHO.
2) An user that chooses the docviewer as a peer for opening a document that he wants to see (e.g. when downloding via webbrowser-app). In this case, the document should be automatically opened.

I think we could go for a third way.
By default, no document is automatically opened. A toast notification is shown instead on the bottom edge of the screen, informing the user that the document has been successfully imported.
This notification will also provide a button, that the user can tap to open the document.
For design references, I suggest to see how Quick Memo (it's an application that I wrote some time ago) works. It provides toast notifications when a note is created/modified/deleted.

I feel like this solution is the less invasive for both the scenarios, and it's informative enough to be useful for users.

[Ubuntu Phone Apps Jenkins Bot (ubuntu-phone-apps-jenkins-bot)]

Fix committed into lp:ubuntu-docviewer-app at revision 120, scheduled for release in ubuntu-docviewer-app, milestone 2014-10-30