26.09.2011, в 13:24, David Faure написал(а): > With Qt 5 I think we should start thinking much more in terms of "a > collection > of libraries on top of a few core libraries". For something to be available, > it doesn't have to be "inside Qt" (i.e. Core, Gui, Network). > > What I mean by that, is that we'll soon have a set of independent libraries > that can be used with Qt, including libkarchive (ZIP/TAR/XZ/gzip/bzip2...), > libkauth, libkplotting, solid (hardware detection), itemmodels (common > proxies > etc.)... and soon KIO, i.e. an existing, proven stable, implementation of a > VFS. > > Why reinvent the wheel in Qt when you can use an existing framework? > (I'm not saying to use the KDE 4 kio, well you can but it comes with more > dependencies than one might want. However the goal is for KDE Frameworks 5 to > provide these pieces exactly in a way that make it easy for any Qt > application > developer to use them.). > > To give you an idea, KIO supports at least the following protocols: > > about cgi fish gzip knewsservice magnet network pop3 settings thumbnail > zip > akonadi data floppy help man nfs pop3s sftp trash applications > desktop fonts http konvirc mbox nntp programs sieve videodvd ar > feed ftp https konvircs metainfo nntps remote smb webcal bookmarks > > filenamesearch ghelp imap4 ldap mms perldoc rtsp smtp webdav bzip2 file > > groupwise imaps ldaps mmst plasma rtspt smtps webdavs bzip finger > groupwises info lzma mmsu pnm rtspu tar xz > > (some of these are internal, but you can still recognize many useful virtual > filesystems)
As you said, KIO provides lot of dependencies. I don't think this dependencies will be removed in future. 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. _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
