I think it is a good idea to introduce a playground module until we have the API clean and stable, and then we might want to include it right into QtCore.
Regards, Konstantin 2013/9/7 Thiago Macieira <thiago.macie...@intel.com> > On sexta-feira, 6 de setembro de 2013 19:52:47, David Faure wrote: > > * relation to QNetworkReply? > > If that one didn't exist yet, we'd definitely write it as a QJob > subclass. > > So instead, I propose to wrap QNetworkReply into a QNetworkJob or > > something, in order to offer the QJob interface for QNAM requests. On one > > hand this doesn't have to go in at the same time as QJob itself, but OTOH > > it could be a real- world testcase for it, proving its usefulness and > > correctness... > > > > Any other questions? > > What if we put the QJob class and convenience derived classes like > QNetworkRequestJob, QProcessJob, QThreadJob, etc. in one new library. > > This library could be extended later with more job types. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > >
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
