[Kget] Error handling in KDE 4.5

[Lukas Appelhans]

Hey!

I thought about this a bit  more...

For example there can also  be temporary error which will be worked around 
anyway... (for example one mirro rnot working)

I would propose to go this way about it:
if the transfer does setError() and also setStatus(Job::Aborted); we will take 
the error as non-temporary and show the error-message all the time...

If it's just setError() then we take it as temporary...

Lukas

PS: I wonder if we need the Job::Error enum, as it doesn't really make a 
difference if kget-core knows *what* error it is...

Am Mittwoch 27 Januar 2010 23:07:24 schrieb Lukas Appelhans:
> Hey!
> 
> As anybody knows our error handling in KDE 4.4 is far from optimal... we
> leave the plugins pretty  much alone handling those errors (and not every
> plugin reports much...).
> 
> For 4.5 we should improve the situation...
> 
> So my idea was to add some setError(Job::Error, const QString
> &errorMessage); to the transfer-class, which would handle the notification
> + give solutions on how to solve the error...
> 
> For example...
> our transfer does setError(Job::DiskFull, i18n("Your harddisk is running
> out of memory"));. With that information we automagically show the error
> in the GUI and show an option to 1) move the transfer's files to somewhere
> else and 2) to continue downloading... (+ we could detect automagically if
> the user removes files from the disk and resume the transfer).
> 
> If anyone agrees on this solution we would need a set of errors and proper
> names for it...
> 
> Lukas
> _______________________________________________
> Kget mailing list
> Kget at kde.org
> https://mail.kde.org/mailman/listinfo/kget