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

[Scott Aron Bloom]

On Friday, 25 de February de 2011 00:41:08 Jeffery MacEachern wrote:
> On Fri, Feb 25, 2011 at 00:35, Thiago Macieira <thiago at kde.org> wrote:
> > On Friday, 25 de February de 2011 00:18:24 Scott Aron Bloom wrote:
> >> How does the resource area fit into that view of the QFileSystem?
> > 
> > It's kept for compatibility.
> 
> So is it then treated as a special case, with the actual abstraction
gutted?

More or less.

The abstraction for the classes deriving from QAbstractFileEngine is
still there. Compatibility is retained for existing applications.

However, the presence of any file engine (besides the resources one)
will trigger the old, slower, compatibility codepaths. So if you want
the benefit of the new and improved performant file I/O support, remove
all file engines from your code.

PS: why are you guys asking me questions instead of testing Qt 4.8? The
code is already there. It's not like we hide the development without
cause...
------------
Really???

I love Qt.. I really do.. I have been involved in upwards of 50 Qt
commercial licenses to my customers because when they hire me, I promote
Qt,because I can be more efficient coding in Qt then in .Net or Java or
the other frameworks I get asked to code in by my customers...

However, I also, tend to be 4-6 months behind any one of the Qt
releases.. I cant justify the risk of moving to a new release, so I
usually wait for the .1 release (or the .2) based on the chatter on IRC
and/or the mailing lists...

And when I see a deprication, I like to prepare for it...  So I don't
get burned by the QDom vs QXmlStream again....

Now, for me to go "test to see whats in 4.8" it would take the
download/checkout (20-30mins) plus the configure and build (1-2 hours on
windows debug and release, and 1+hour on linux release only and 1+hour
on mac release only)...

Then the time to review the changes and see whats going on.. 

So, I could invest 500-1000 dollars of my billable rate.. Or ask a 10
second question to the product manager?????

ReallY???

Scott