Re: [Development] Proposal: rebranding QMF as QtMail
Am 10.02.2014 17:02, schrieb Robin Burchell: Hello folks, After some build system reworking recently and a little discussion amongst the interested parties (Matt Vogt, Valerio), I'd like to propose renaming QMF (Qt Messaging Framework) to QtMail with the longer term goal of making it a module of Qt properly - no longer a labs project. Making it a proper Qt module? That's awesome news. QMF's naming is historical: QMF originally handled other types of messages than purely mail (SMS/MMS also, for instance). This has not been the case for quite some time - QMF now handles *only* email, so this renaming makes the whole thing sound a bit less meta and less awkward. I don't mind the naming: The data model clearly is email oriented, therefore expressing that in the class names is fine. What bothers me: Do you plan keeping support for other message types, or did you even consider extending it? I am thinking of Kolab's IMAP server that stores contacts and calendars in dedicated IMAP folders. Even more I think of instant messaging: As a spare time project I am experimenting with an unified EMail + XMPP client right now and considered implementing a XMPP plugin for QMF/QtMail, so that I could benefit from its abstractions. Instead of hiding QMF and XMPP behind my own, rather ad-hoc abstraction layer. Ciao, Mathias ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] OTHER_FILES in Qt Creator 3.1.1
Hello,
I have a little problem. I want to set OTHER_FILES in our framework to
load all files in the Qt Creator 3.1.1. I want to use an lib.pri to load
dinamically in each pro-File. The problem is, that the other files are
shown under the subfolder lib.pri and not under the header- and
cpp-files. If I write to each pro-file I have it in the correct
subfolders. Is there a possibility to change it.
In the lib.pri I have following code:
defineTest(otherfiles) {
files = *.sql *json *lst * txt
return($$files)
}
and in the pro-File:
OTHER_FILES = $$otherFiles()
It works but only in the way I told above.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qmake Ninja generator
Putting my 2¢ in, Qmake is IMHO good enough. Qbs is kind of vaporware, sparse documentation, needs Qmake to build (woot?!). Altogether it sounds like a clinch, we don't want to extent Qmake with ninja or anything, because there comes Qbs. But Qbs isn't really there, because one needs lot of work to make it more less feature equal to CMake. So we are back to Qmake, huh. Regards, -- Adam ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Update on iOS / SSL implementation
A while back I posted some proof of concept code to show what an
implementation of QSslSocket might look like using Secure Transport. I
have continued along these lines, and wanted to keep you updated.
1. GENERAL
Apple's Secure Transport API is available both on OS X and iOS. As I do
not have a iDevice, I have been developing on OS X exclusively, but
making sure the methods I use are available on iOS (iOS only has a
subset of OS X's capabilities).
Secure Transport API:
- provides close to nothing for manipulating certificates / keys = I
had to write a minimal (DER-only) ASN.1 parser
- only accepts certificates + keys .. in PKCS#12 form = I had some
write some ASN.1 serialisation code, and a lot of PKCS#12 code (I
absolutely hate that standard by now)
2. WHAT WORKS
I am now getting to the point where a lot unit tests are passing.
- QSslSocket works in client and in server mode
- QSslCertificate works, with no external dependencies
- QSslKey : ditto
What still needs work:
- the build system needs to be updated to allow building the SSL
classes, even when OpenSSL is not found
- QSslCertificate::isSelfSigned needs implementing
- QSslKey : serializing to a password-protected PEM does not work yet
- there is some duplicated code between the OpenSSL and Secure
Transport backends
- QSslConfiguration : no work done yet
3. HOW TO GET IT
As previously stated, my current work has been on OS X only, not actual
iOS devices.
1/ Checkout the qssl-ios branch from
https://qt.gitorious.org/qt/sharkys-qtbase on a OS X machine
2/ Apply the attached patch to fix / disable some QSslSocket unit tests
3/ Build it
4/ Run some unit tests
5/ Help fix the errors :)
Cheers,
Jeremy
PS: no unfortunately I cannot make it to the contributor summit
diff --git a/tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp b/tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp
index baaf21e..e00cb18 100644
--- a/tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp
+++ b/tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp
@@ -81,6 +81,8 @@ Q_DECLARE_METATYPE(QSsl::SslProtocol)
typedef QSharedPointerQSslSocket QSslSocketPtr;
#endif
+#define OPENSSL_NO_SSL2
+
class tst_QSslSocket : public QObject
{
Q_OBJECT
@@ -262,6 +264,7 @@ void tst_QSslSocket::initTestCase_data()
QTest::addColumnint(proxyType);
QTest::newRow(WithoutProxy) false 0;
+#if 0
QTest::newRow(WithSocks5Proxy) true int(Socks5Proxy);
QTest::newRow(WithSocks5ProxyAuth) true int(Socks5Proxy | AuthBasic);
@@ -269,6 +272,7 @@ void tst_QSslSocket::initTestCase_data()
QTest::newRow(WithHttpProxyBasicAuth) true int(HttpProxy | AuthBasic);
// uncomment the line below when NTLM works
//QTest::newRow(WithHttpProxyNtlmAuth) true int(HttpProxy | AuthNtlm);
+#endif
}
void tst_QSslSocket::initTestCase()
@@ -423,6 +427,7 @@ void tst_QSslSocket::constructing()
QVERIFY(!socket.waitForDisconnected(10));
QCOMPARE(socket.protocol(), QSsl::SecureProtocols);
+#if 0
QSslConfiguration savedDefault = QSslConfiguration::defaultConfiguration();
// verify that changing the default config doesn't affect this socket
@@ -439,6 +444,7 @@ void tst_QSslSocket::constructing()
QVERIFY(QSslConfiguration::defaultConfiguration().ciphers().isEmpty());
QSslConfiguration::setDefaultConfiguration(savedDefault);
+#endif
}
void tst_QSslSocket::simpleConnect()
@@ -810,6 +816,7 @@ void tst_QSslSocket::privateKey()
void tst_QSslSocket::privateKeyOpaque()
{
+#if 0
if (!QSslSocket::supportsSsl())
return;
@@ -836,6 +843,7 @@ void tst_QSslSocket::privateKeyOpaque()
QFETCH_GLOBAL(bool, setProxy);
if (setProxy !socket-waitForEncrypted(1))
QSKIP(Skipping flaky test - See QTBUG-29941);
+#endif
}
void tst_QSslSocket::protocol()
@@ -1025,17 +1033,17 @@ protected:
if (m_interFile.isEmpty()) {
QListQSslCertificate localCert = QSslCertificate::fromPath(m_certFile);
QVERIFY(!localCert.isEmpty());
-QVERIFY(localCert.first().handle());
+QVERIFY(!localCert.first().isNull());
socket-setLocalCertificate(localCert.first());
}
else {
QListQSslCertificate localCert = QSslCertificate::fromPath(m_certFile);
QVERIFY(!localCert.isEmpty());
-QVERIFY(localCert.first().handle());
+QVERIFY(!localCert.first().isNull());
QListQSslCertificate interCert = QSslCertificate::fromPath(m_interFile);
QVERIFY(!interCert.isEmpty());
-QVERIFY(interCert.first().handle());
+QVERIFY(!interCert.first().isNull());
socket-setLocalCertificateChain(localCert + interCert);
}
@@ -1525,7 +1533,7 @@ protected:
// Only set the certificate
QListQSslCertificate localCert = QSslCertificate::fromPath(SRCDIR certs/fluke.cert);
QVERIFY(!localCert.isEmpty());
-
Re: [Development] Qmake Ninja generator
On May 29, 2014, at 6:03 AM, Adam Strzelecki o...@java.pl wrote: Putting my 2¢ in, Qmake is IMHO good enough. Qbs is kind of vaporware, sparse documentation, needs Qmake to build (woot?!). Altogether it sounds like a clinch, we don't want to extent Qmake with ninja or anything, because there comes Qbs. But Qbs isn't really there, because one needs lot of work to make it more less feature equal to CMake. So we are back to Qmake, huh. Qbs has by definition more features than cmake because it is a make tool. Neither cmake nor qmake build anything, they just generate makefiles or project files. In that respect qmake and cmake are quite alike. Qbs is a full-featured build tool: it takes care of generating the DAG *and* executing it. It’s like qmake and ninja in one. In the long run I think Qt either need Qbs as the default build system, or ninja support in qmake. Ninja makes all the difference when building llvm. On a modern system I can get null llvm rebuild times on the order of 100ms with ninja, and under a second with a single changed .cpp file - and that’s a big project. The 1 second single-file rebuilds on fairly small make-based projects (like examples bundled with Qt) are really bad. With cmake+ninja, a single changed .cpp rebuild of a small Qt example on OS X takes about 250ms. Cheers, Kuba ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Update on iOS / SSL implementation
What Jeremy has done here is fantastic. My estimate when I was previously asked how hard it was to write a new backend to the SSL support was approximately a man month given a developer who already knew the subject area. I'm extremely please that someone has been willing to make this investment in time, effort and given the nature of SSL/TLS sheer frustration. Thank you. Not having a Mac, I can't test this, but I'll have a long look over the code and see what I can do to help get this integrated. Rich. On 29 May 2014 18:26, Jeremy Lainé jeremy.la...@m4x.org wrote: A while back I posted some proof of concept code to show what an implementation of QSslSocket might look like using Secure Transport. I have continued along these lines, and wanted to keep you updated. 1. GENERAL Apple's Secure Transport API is available both on OS X and iOS. As I do not have a iDevice, I have been developing on OS X exclusively, but making sure the methods I use are available on iOS (iOS only has a subset of OS X's capabilities). Secure Transport API: - provides close to nothing for manipulating certificates / keys = I had to write a minimal (DER-only) ASN.1 parser - only accepts certificates + keys .. in PKCS#12 form = I had some write some ASN.1 serialisation code, and a lot of PKCS#12 code (I absolutely hate that standard by now) 2. WHAT WORKS I am now getting to the point where a lot unit tests are passing. - QSslSocket works in client and in server mode - QSslCertificate works, with no external dependencies - QSslKey : ditto What still needs work: - the build system needs to be updated to allow building the SSL classes, even when OpenSSL is not found - QSslCertificate::isSelfSigned needs implementing - QSslKey : serializing to a password-protected PEM does not work yet - there is some duplicated code between the OpenSSL and Secure Transport backends - QSslConfiguration : no work done yet 3. HOW TO GET IT As previously stated, my current work has been on OS X only, not actual iOS devices. 1/ Checkout the qssl-ios branch from https://qt.gitorious.org/qt/sharkys-qtbase on a OS X machine 2/ Apply the attached patch to fix / disable some QSslSocket unit tests 3/ Build it 4/ Run some unit tests 5/ Help fix the errors :) Cheers, Jeremy PS: no unfortunately I cannot make it to the contributor summit ___ 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
[Development] Qt (5.3.0) QML on Mali 400 armsoc driver. Could it be broken?
Hi, I'm trying to run Qt5 QML examples on the odroid-x. That device has the mail 400 gpu with the armsoc driver. I have a working graphical environment and i can run a OpenGL ES 2 demo benchmark (non Qt) glmark2-es2. That seems to be working just fine. However, if i try to run qmlscene (or qmlviewer) i'm keep getting this message: Cant find EGLConfig, returning null config Unable to find an X11 visual which matches EGL config 0 Could not initialize OpenGL followed by a core dumped line. Could this driver + Qt5 be broken? If there are any commands or tests you want me to run for more information, please don't hesitate to ask. I'd gladly help. Cheers, Mark ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt (5.3.0) QML on Mali 400 armsoc driver. Could it be broken?
Op 30 mei 2014 01:39 schreef Mark Gaiser mark...@gmail.com: Hi, I'm trying to run Qt5 QML examples on the odroid-x. That device has the mail 400 gpu with the armsoc driver. I have a working graphical environment and i can run a OpenGL ES 2 demo benchmark (non Qt) glmark2-es2. That seems to be working just fine. However, if i try to run qmlscene (or qmlviewer) i'm keep getting this message: Cant find EGLConfig, returning null config Unable to find an X11 visual which matches EGL config 0 Could not initialize OpenGL followed by a core dumped line. Could this driver + Qt5 be broken? If there are any commands or tests you want me to run for more information, please don't hesitate to ask. I'd gladly help. Cheers, Mark And it's fixed. When people see me using root in pastebins for console output they always say you really should not use root, make a user or something along those lines. (I fully agree to that BTW) Well, I did for the Qt stuff. As a user I get the issues mentioned in the first post. As root I actually have everything working just fine. Qt QML examples work perfectly. I actually wasn't expecting an example like samegame to be buttery smooth, but it is! Pros to the Qt team! So it seems to be some issue with permissions. And that is certainly not clear when looking at the output I saw (in the first post). On big fat note though. Do not use startx with twm. Qt examples and windows then open in some bugged transparent way. Use a slightly more modern window manager like openbox. Now I just have to figure out which permissions are missing for the user. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Failing test for qtlocation
Hi! While packaging Qt 5.3.0 I'm trying to run all the possible tests I can. I'm now stucked with qtlocation: * Finished testing of tst_QNmeaPositionInfoSource_Simulation_Generic * make[6]: Leaving directory '/«PKGBUILDDIR»/tests/auto/qnmeapositioninfosource/qnmeapositioninfosource_simulation_generic' make[5]: Leaving directory '/«PKGBUILDDIR»/tests/auto/qnmeapositioninfosource' FAIL! : DefaultSourceTest::requestUpdate_defaultTimeout() '(spyUpdate.count() 0) (spyTimeout.count() == 0)' returned FALSE. () Loc: [testqgeopositioninfosource.cpp(620)] PASS : DefaultSourceTest::requestUpdate_timeoutLessThanMinimumInterval() FAIL! : DefaultSourceTest::requestUpdate_repeatedCalls() '(spyUpdate.count() 0) (spyTimeout.count() == 0)' returned FALSE. () Loc: [testqgeopositioninfosource.cpp(645)] FAIL! : DefaultSourceTest::requestUpdate_overlappingCalls() '(spyUpdate.count() 0) (spyTimeout.count() == 0)' returned FALSE. () Loc: [testqgeopositioninfosource.cpp(662)] FAIL! : DefaultSourceTest::requestUpdateAfterStartUpdates_ZeroInterval() '(spyUpdate.count() 0) (spyTimeout.count() == 0)' returned FALSE. () Loc: [testqgeopositioninfosource.cpp(676)] FAIL! : DefaultSourceTest::requestUpdateAfterStartUpdates_SmallInterval() '(spyUpdate.count() == 1) (spyTimeout.count() == 0)' returned FALSE. () Loc: [testqgeopositioninfosource.cpp(700)] FAIL! : DefaultSourceTest::requestUpdateBeforeStartUpdates_ZeroInterval() '(spyUpdate.count() = 2) (spyTimeout.count() == 0)' returned FALSE. () Loc: [testqgeopositioninfosource.cpp(725)] FAIL! : DefaultSourceTest::requestUpdateBeforeStartUpdates_SmallInterval() '(spyUpdate.count() 0) (spyTimeout.count() == 0)' returned FALSE. () Loc: [testqgeopositioninfosource.cpp(746)] PASS : DefaultSourceTest::removeSlotForRequestTimeout() FAIL! : DefaultSourceTest::removeSlotForPositionUpdated() '(m_testSlot2Called == true)' returned FALSE. () Loc: [testqgeopositioninfosource.cpp(782)] PASS : DefaultSourceTest::cleanupTestCase() Totals: 27 passed, 20 failed, 0 skipped * Finished testing of DefaultSourceTest * I think I might be missing some service running here, as for example I need to setup dbus for the tests to run. Can anyone give me a hint of what could be happening? Is this the right list for asking tests questions? Kinds regards, Lisandro. -- Sea estricto cuando envíe y tolerante cuando reciba. En otras palabras, solo envíe paquetes que cumplan rigurosamente con lo estándares, pero espere paquetes que tal vez no cumplan del todo y trate de lidiar con ellos. Andrew S. Tanenbaum, de su libro Computer Networks Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
