https://developer.mozilla.org/en-US/docs/Mozilla/Projects/XU...
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/XU...
https://groups.google.com/forum/#!topic/mozilla.dev.platform...
It'll still be possible to use Firefox to run XUL apps, though.
Isn't that what Qt is for, with the added bonus that it's what Qt is actually for and thus e.g. documented and supported?
(I haven't used Chromium libs and have no opinion about them)
Edit: in fact just to highlight how similar it is, the way that QtWebKit works is that it is built on top of these modules in a [hand wavy] similar way that blink is built on top of the chrome development platform (I have hacked on Qt, WebKit, and Chrome).
There are a lot of cross-platform base libraries out there, many of them (like Qt, GTK/GLib, and Mozilla's stack) well-documented and well-supported. These systems are meant to be reused; Chrome? Not so much. Besides the buzz factor, why would you want to base a product on Chrome instead of one of the codebases designed to be used that way?
Qt is a C++ application framework, it has both low- and high-level components, much like e.g. Cocoa.
> We were looking for lower-level constructs - especially in the networking and P2P areas.
Which Qt provides. Qt is modular and Qt has plenty of low- or intermediate-level modules, including extensive networking, storage and concurrency systems. Using Qt does not mandate using Qt's UI components.
If you want a fairly high level, cross platform C++ library, there is no reason NOT to use Qt.
I worked for a high end audio company and used it in one of their acoustic simulation softwares.
One of my main jobs was porting this project to Qt.
Which coincidentally, Chrome & Chromium are based on, making the cross-library usage full circle.