On Freitag, 28. Juni 2013 14:20:33 CEST, Pali Rohár wrote:
On Friday 28 June 2013 14:10:35 Thomas Lübking wrote:
On Freitag, 28. Juni 2013 12:35:19 CEST, Kevin Krammer wrote: ...
Now I'm rewriting addressbook requests to use jobs. But I do not
think that we need common interface for both addressbook and
password jobs. I do not see trojita code where could be general
job object needed. Everywhere I need to know if it is password or
addressbook job type, so common interface for both classes is not
needed...
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.
Compare
http://api.kde.org/4.10-api/kdelibs-apidocs/kdecore/html/classKJob.html
Cheers,
Thomas
