[Qt-interest] What is likely to be in Qt 4.8?

[Stephen Chu]

On 2/25/2011 2:44 AM, Thiago Macieira wrote:
> If you want custom, please consider modifying your operating system's kernel,
> or using a virtual filesystem layer. Trying to make QFile be a VFS was a
> mistake back in Qt 4.1 days we're only now correcting.

Not every OS allows you to plug/change the kernel. File engine provides 
a platform-independent way of handling my issue which is why I choose Qt 
in the first place.
>
>> I use custom
>> file engine to handle different compression schemes of our files so the
>> code that reads them doesn't have to know which type they are. will this
>> still be possible in the new file system?
>
> You can still do the same by using your own classes deriving from QIODevice
> instead of relying on QFile. KDE has been doing that with the KArchive classes
> for 10 years.

QIODevice maybe the solution for me then. Although with file engine, my 
class derived from QFSFileEngine only have to override 4 functions and 
none of the client code need to change. With custom QIODevice, I 
probably have to duplicate all functions in QFile, and all client code 
has to change.

As to why am I asking question instead of testing? My specific question 
has nothing to do with testing. It's is the first time I read about the 
deprecation of file engine and it (or any new feature/deprecation) was 
not announced any where before.

I have to say Qt has grown. A lot of us new Qt programmers do not have 
the do-everything-yourself attitude toward all the tools we use. We want 
to get the job done and Qt is part of the solution, not the job.