[Development] A QtCore class for event-driven jobs

Harri Porten porten at froglogic.com
Sat Sep 7 10:19:53 CEST 2013


On Sat, 7 Sep 2013, Konstantin Ritt wrote:

> one would probably prefer
> 
> [code]
> job =  someoperation(some parameters);
> manager->enqueue(job);
> [/code]
> , where "someoperation" could be manager's registered job factory or QJob sub-class, etc.

I am not sure why everyone prefers to have a "manager" ;)

> This way, job not necessarily should derive from QObject; all required 
> signals and methods could be provided by some kind of job watcher [or 
> job sequence watcher] or even by the manager itself.

That limits the available API to the lowest common denominator, no? No 
job-specific features available unless some typeless QVariant properties 
or similar are used.

Harri.


More information about the Development mailing list