- WebKit: merging web technologies and desktop applications. Things like accessing signals/slots from javascript or moving things around in the DOM from C++
- Mobile: mobile
- Enhanced XML support: xml streams (in 4.3 actually) and they are looking at a better xml tree implementation; XQuery/XPath are coming
- IPC: shared memory and locks, file mapping and local sockets ... all crossplatform
- Concurrency framework: multithreaded apps with mutexes and wait conditions in your app code
- Multimedia: audio and video playback. Yes, this is Phonon. =) QuickTime, DirectX and GStreamer backends are all coming.
- Help system: WebKit for rendering, componentized (viewer, index, contents, full text search)
- Fully resolution independent user interfaces (and then we can use this in Plasma instead of our own set of widgets)
- Qt for Cocoa: 64-bit Mac version based on the Cocoa API
- QPlainTextEdit
- Next generation of Itemviews to make them rock a lot more, though just how was light on details; apparently this is an ongoing field of research right now for the Trolls
- More Qt Jambi, following the Qt release cycle
There are apparently plans for at least a 4.7 and there are no current plans for Qt5. If a Qt5 were to happen, it wouldn't be before 2011/2012 and it would not be a major API design break with Qt4 as Qt4 was to Qt3. However, they feel that Qt4 has what is needed for years of innovation to come and so there are no plans at all for a Qt5 right now.
Neat =)
11 comments:
Wow. Can't wait! Definitely solidifies my choice of Qt for my contract work. Trolltech's small business program makes it all affordable.
full-text-search -- usin strigi?
also, looking forward to read more about QPlainTextEdit
Any news of Qt-Coco? You talked about that 2 years ago, but no news yet.
Hello Aaron,
Can you elaborate a little about this point:
"Multimedia: audio and video playback. Yes, this is Phonon. =) QuickTime, DirectX and GStreamer backends are all coming."
Will Trolltech develop those backends? If so, please let me know.
What I'm kind of curious about is, how come they choose GStreamer but not Xine? Or, if they'll ever create a way to use xine?
accessing signals/slots from javascript or moving things around in the DOM from C++
Ah, that's the news I was waiting for. Any additional details how this will affect QtScript or will >=Qt4.4 really contain 2 full JavaScript-implementations?
What I'm kind of curious about is, how come they choose GStreamer but not Xine? Or, if they'll ever create a way to use xine?
Gstreamer is just one of many engines for Phonon to be used on Linux, I think a xine engine is already close to completion. I'm pretty sure a couple more engines were started but development was stalled.
Quote:
"I think a xine engine is already close to completion. I'm pretty sure a couple more engines were started but development was stalled."
Indeed, but the stalled development is for a reason. The Phonon library (is) was still in development and (changes) changed rapidly.
I've picked up the development for a GStreamer backend again. As you can imagine, GStreamer is pretty complex which means that the backend will get complex and takes a lot of time to get it right.
But what I would like to know is:
Will Qt develop those backends?
If so, I don't need to put all my time into developing such a backend myself.
Qt5 in 2012 is probably the best news among the lot.
Any word about GPLv3?
@lucio: Qt-Coco did not end up being productized, it seems.
@tbscope: they'll help as needed. they are 100% working with the community on this one, so they won't be duplicating work internally. if anything, they may help out if someone is working on a specific feature set that they have an interest in.
@sebastian sauer: it doesn't affect QtScript at all; the javascript implementation that is part of webkit is internal to it...
@anonymous: the GPLv3 question did indeed come up; no new info yet, just that it is being worked on (we already knew that ;)
Post a Comment