Re: [Development] Two source incompatibilities in Qt 5.5 with Clang
On Monday 16 March 2015 14:54:53 Thiago Macieira wrote: On Monday 16 March 2015 21:05:41 Stephen Kelly wrote: Thiago Macieira wrote: Because we want to benefit from the new code and remove the unnecessary #ifndef and Q_UNUSED. If we don't change the current macro, then we deprecate the old one and convert all the code to the new one You could deprecate the old behavior. #ifdef QT_BUILDING_QT || QT_DISABLE_DEPRECATED_BEFORE = 0x050500 #define USE_NEW_ASSERT #endif #ifdef USE_NEW_ASSERT // ... #else // ... #endif We could do that. Opinions for or against? I think it's a good idea, just like we have QT_USE_QSTRINGBUILDER, we could have QT_CHECK_ASSERT or something like that. -- Olivier Woboq - Qt services and support - http://woboq.com - http://code.woboq.org ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Deprecating modules with 5.5
Some of our applications are relying on Qt Script and Qt Webkit. So I just had a look at the replacements (Qt Webengine and Qt QML). The documentation says ... WebEngine ... doesn't give direct access to the network stack and the HTML document through C++ APIs. Does this mean there is no way to access the DOM anymore? This would be fatal for us. Accessing the DOM is essential for all of our applications that use QWebView. Is there some replacement/workaround? Also we use the QScriptEngineDebugger but there seems to be no debugger for QJSEngine. Is there some replacement/workaround? Are there other significant differences that I should consider? -- Kind Regards Bernhard Lindner -Ursprüngliche Nachricht- Von: development-bounces+private=bernhard-lindner...@qt-project.org [mailto:development-bounces+private=bernhard-lindner.de@qt- project.org] Im Auftrag von Knoll Lars Gesendet: Dienstag, 3. Februar 2015 08:34 An: development@qt-project.org Betreff: [Development] Deprecating modules with 5.5 Hi, I’d like to mark a few modules as deprecated with 5.5, and most likely remove them from the binary packages with 5.6. These modules are: * Qt WebKit * Qt Declarative (Qt Quick 1) * Qt Script All of these modules are by now a couple of years old, don’t receive updates above the bare minimum and have a replacement that is actively being developed in Qt 5. Cheers, Lars ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development attachment: winmail.dat___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt mailing list migration
On Monday 16 March 2015 18:29:58 Oswald Buddenhagen wrote: On Mon, Mar 16, 2015 at 05:42:40PM +0100, Marc Mutz wrote: On Monday 16 March 2015 13:57:57 Järvenpää Petri wrote: The change should be invisible to the normal user, Are you going to break List-Id again? that seems *very* unlikely given the 1:1 copy plan. So you guarantee that development.qt-project.org will _still_ be List-Id when hosting moves over to qt.io? That would be a (welcome) first! Thanks, Marc -- Marc Mutz marc.m...@kdab.com | Senior Software Engineer KDAB (Deutschland) GmbH Co.KG, a KDAB Group Company Tel: +49-30-521325470 KDAB - The Qt Experts ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Adding .mtl files into qt3d+qt5.5 based applcation
Hi, When i export blender files into .obj files, i get .mtl supporting files as well. However, I am able to add .obj files but am not sure how to add the .mtl file information. Additionally, are there any documentation for qt3d 2.0 (5.5 branch) ? I am trying to understand the APIs from the example. Any extra help would be great. Thanks Regards Arjun ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Debug category for sql drivers
Hi, could have have an sql category for the sql drivers? Currently the postgres driver drives me crazy. :-D I get constantly a warning: Unable to free statement: ERROR: prepared statement qpsqlpstmt_23 does not exist Does not look like I can do much to remove the cause of this warning in my code. Therefore I checked, if I can disable it. Unfortunately at least the postgres driver does not use any categories, but spams default. I really don't want to disable default globally. Guido ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Deprecating modules with 5.5
On Tuesday 17 March 2015 17:14:38 Jan Kundrát wrote: On Tuesday, 3 February 2015 08:33:46 CET, Knoll Lars wrote: * Qt WebKit While I understand the reasons on why you want to remove this one, I think that this goes against the promise of compatibility at [1]: Qt essentials define the foundation of Qt on all platforms. They are available on all supported development platforms and on the tested target platforms. They will remain source and binary compatible during Qt 5. Both Qt WebKit and Qt WebKit Widgets are listed under Essentials. QtScript and QtDeclarative are listed as Addons, and could probably go. You're of course free to do whatever you want to do -- it's just that the project has promised that this won't happen. We promised not to break source or binary compatibility. Where are we doing that? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Two source incompatibilities in Qt 5.5 with Clang
On Tuesday 17 March 2015 09:40:08 Olivier Goffart wrote: Opinions for or against? I think it's a good idea, just like we have QT_USE_QSTRINGBUILDER, we could have QT_CHECK_ASSERT or something like that. Ok, I'll prepare a patch. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5.5 Alpha released
Hi all! Qt 5.5 Alpha release is out, see http://blog.qt.io/blog/2015/03/17/qt-5-5-alpha-available/ As earlier, Alpha is source code delivery only. The plan forward is now to create a beta (including binary packages) during the next few weeks. Big thanks for everyone who were involved to make this happen! Br, Jani ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Deprecating modules with 5.5
Regarding QJSEngine, some things are unclear to me.
Let's say I have a QObject-derived class. how do I create an instance of
that class from a script ?
c++ : class Foo : public QObject { Q_OBJECT }; js : var foo = new Foo()
How do I call a c++ function from a js script ? That use case seems not
supported at all, I'm I right ?
Those two features seems essential to me for QJSEngine to ever replace
QScriptEngine. They also are pretty basic.
I understand one will have to heavily modify the C++ code to port to
QJSEngine, but, I find the fact that the port will break the scripts...
worrisome
I think QJSEngine should aim to be compatible with any script that worked
with QScriptEngine (provided the C++ code is modified accordingly)
Regards,
Corentin Jabot
2015-02-10 4:30 GMT+01:00 Thiago Macieira thiago.macie...@intel.com:
On Monday 09 February 2015 22:52:34 Kevin Kofler wrote:
Guido Seifert wrote:
Did something like that happen before?
Yes, RHEL has never shipped QtWebKit, as far as I know because of support
(especially with security updates) concerns. (They're likely to also not
ship QtWebEngine, but that will be a topic for RHEL 8. QtWebEngine did
not
exist yet when RHEL 7 was released.) They also ship kdelibs with
Plasma::WebView patched out, kdepim without KMail (because it depends on
QtWebKit), Qt Assistant built against QTextBrowser, and similar such
feature
removals/degradation throughout KDE.
If all that stuff moves to QtWebEngine, we will likely end up with Fedora
and Debian getting similarly crippled. :-(
You'll probably have to provide a repository for packages supported less
thoroughly. There are just too many requirements for Web parsing.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Deprecating modules with 5.5
On Tuesday, 3 February 2015 08:33:46 CET, Knoll Lars wrote: * Qt WebKit While I understand the reasons on why you want to remove this one, I think that this goes against the promise of compatibility at [1]: Qt essentials define the foundation of Qt on all platforms. They are available on all supported development platforms and on the tested target platforms. They will remain source and binary compatible during Qt 5. Both Qt WebKit and Qt WebKit Widgets are listed under Essentials. QtScript and QtDeclarative are listed as Addons, and could probably go. You're of course free to do whatever you want to do -- it's just that the project has promised that this won't happen. Cheers, Jan [1] http://doc.qt.io/qt-5/qtmodules.html -- Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/ ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
