On Friday, 28 June 2013 14:31:21 CEST, Thomas Lübking wrote:
The point about a common class is to allow generic job handlers as well as not to have to write the same stupid "stop", "cancelled", "finished" interface multiple times.
Speaking about the KJob, I'd prefer to keep the interface small and not export stuff like uiDelegate(), percent(), speed() etc which make little sense in this particular context. Do you have any specific example of what would be easier if the password and abook jobs shared a common ancestor? Cheers, Jan -- Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
