So, should i start implementing new VFS or someone will port KIO to use pure qt and include it in qt5?)
17.10.2011, в 23:53, Alexander Neundorf написал(а): > On Monday 26 September 2011, Иван Комиссаров wrote: >> 26.09.2011, в 14:41, Thiago Macieira написал(а): >>> On Monday, 26 de September de 2011 14:10:57 Иван Комиссаров wrote: >>>> Also, KIO doesn't seems to be 'vfs' in my opinion - it just provides >>>> asynchronous methods for common operations. I'm not sure, but i don't >>>> think people will be glad to see al this "job" stuff. >>> >>> Just rename the classes. >>> >>> QNetworkReply is a "job". You post the job using QNetworkAccessManager. >>> >>> We're not suggesting using KIO. The API was designed back in 2000 for KDE >>> 2 and, while it works, I'd rather have a smaller, leaner API for Qt. >>> Some of that learning I applied in QNetworkReply, for example, which >>> works as a hybrid of KIO::TransferJob and KIO::StoredTransferJob. >> >> Well, i meant people won't be happy to see Jobs as they are. API is ok in >> general, but it uses inheritance from KJob which is not necessary for VFS >> and Qt. So it should be renamed to class that looks like job, behaves like >> a job, but not a "job" in API. We can't do that in KIO, so we have to >> reinvent wheel) > > No, it can be done. > The work on KDE frameworks is to a verry big part motivated by making the > bits > and pieces more easily available to Qt-only applications. > Source-compatibility also should be kept as much as possible, but this can > also be achieved via KDE4-libs wrappers (if it's only name changes). > > So, it's not an "impossible". > > Alex > _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
