Handle errors that can arise during downloading of formats

[GoogleCodeExporter]

There is a complex set of possible errors that could occur during the 
downloading of an item. Currently, such errors are 'consumed', ie, do not show 
on the screen.

Original issue reported on code.google.com by steven3...@gmail.com on 12 Jun 2014 at 6:48

[GoogleCodeExporter]

Original comment by steven3...@gmail.com on 13 Jun 2014 at 5:59

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by steven3...@gmail.com on 17 Aug 2014 at 5:14

• Added labels: Priority-Medium
• Removed labels: Priority-High

[GoogleCodeExporter]

To handle download errors, we guide the download format process by using an 
action dialogue box.

In the first stage, we ask for confirmation from the user, showing a message 
that is related to the context of whether the user is downloading an Overdrive 
Read format type or a type for reading in an e-reader. If there are errors 
arising from misusing the API, it will appear within the action box as normal.

In the next stage, a content link will have been gotten. The URL will be 
rendered as a link within the action box with a label suggesting the user 
should right-click. The user can then choose to show the content in a new tab 
or window.

The link is valid for the next 60 seconds. To prevent the user from using the 
link after it expires, we automatically close the action box after 59 seconds. 
If the user missed the opportunity to download, the user can simply re-initiate 
by clicking the download button again. (The auto-close mechanism is available 
for use in other actions; there we auto-close their action boxes after two 
seconds.)

There are errors that can arise from using the content link. There is another 
set of errors that can arise from downloading Overdrive Read content 
specifically. They will all be shown in a floating notification box centred on 
the same page in lieu of the content that should have been downloaded. To test 
it, I manually corrupted a content link to provoke an error before 
right-clicking it.

Original comment by steven3...@gmail.com on 15 Sep 2014 at 6:31

• Changed state: Fixed