On Sat, 26 Jan 2019, Olivier Goffart wrote:
I think the "monorepo" is clearly a good approach. And git is evolving with
shadow clones and partial checkout. LLVM/Clang recently choose the monorepo
approach as it moves to git.
Of one problem is that this will make CI integration slower because
On Fri, 6 Oct 2017, Tomaz Canabrava wrote:
> We have recently been working on a research project looking into the
possibilities for creating a lightweight server component that can easily enable Qt
applications to serve over HTTP. We would like to make this work public
and
On Sat, 2 Sep 2017, Oswald Buddenhagen wrote:
if we wanted to be really conservative, we'd leave the old meaning of
the sha3 constants and introduce realSha3 (or something to that effect)
instead, in 5.10+. keccak aliases would be also provided for a smooth
migration.
Fwiw, I would have
On Thu, 6 Jul 2017, Thiago Macieira wrote:
By the way, how does it break the cycle?
Like I was saying before, node_ptr enlists each pointee object to the
associated root_ptr and when the root_ptr is destroyed then everything
gets wiped out.
See above. Your answer is "it doesn't break the
I got reminded of something:
On Tue, 3 May 2016, Thiago Macieira wrote:
Still, note that this is not an error. It's a warning turned to error because
of the -Werror, which means that you used -developer-build. In that case,
please send a patch. :-)
I've seen my Qt users use -developer-build
On Fri, 5 Feb 2016, Thiago Macieira wrote:
* QtGui:
- QPixmapCache::allPixmaps(): innocent, was not public API, but you could get
to it.
- qt_sendShortcutOverrideEvent: affects QtTest binary compatibility
Our product (and its users) were bitten by this as well. As the function
wasn't
On Tue, 19 Jan 2016, Marc Mutz wrote:
I think we agree that std containers are in many cases faster than the Qt
containers. But they are harder to use and especially developers that come
from other languages often appreciate the ease of use of the Qt
containers.
I always cringe when I hear
On Fri, 15 Jan 2016, Marc Mutz wrote:
And no, I cannot believe that using the Qt containers leads to faster
applications. It may lead to applications faster, but not to faster
applications.
Amen! Now each side of the discussion please pick one of the above
possible outcomes and be happy :)
On Fri, 20 Nov 2015, joh...@fastmail.com wrote:
I'll contact them, and get them involved in the bug if I can, and get
off this list where I don't belong -- I just need to figure out who
"They" are and stop this ping-pong-ball business.
Speaking of business: keep in mind that the people you
On Thu, 28 May 2015, Cristian Adam wrote:
Does anyone know what happened with the Testablity Driver?
I can only confirm what Gerry said: it couldn't keep up with the speed of
Qt development.
For our own tool Squish we are also kept busy constantly with advances not
only in QML but especially
On Thu, 26 Mar 2015, Adam Light wrote:
I'd like to move my checkout to git://code.io.qt.
I got reminded of your mail when I just did a new clone:
http://wiki.qt.io/Building_Qt_5_from_Git suggests the usage of:
git clone git://code.qt.io/git/qt/qt5.git
but the /git/ part is probably just
On Fri, 6 Mar 2015, Oswald Buddenhagen wrote:
1) i'd like to propose the introduction of the code review score -3.
I often wished for Gerrit have a non-sticky -2. The proposed introduction
of -3 is a good solution.
2) i'd like to propose the introduction of the code review score +3.
Could
Hi!
I see that the first decisive commit is already merged but I'd like to
comment on it anyway:
On Mon, 2 Mar 2015, Rutledge Shawn wrote:
It may be a surprise though, for some applications, that
QGuiApplication::primaryScreen() can return null in the case where there
is really no screen
On Sun, 18 Jan 2015, Kevin Kofler wrote:
Thiago Macieira wrote:
The one requirement that came from the Qt Project was that the tools would
not be renamed.
And the one requirement that came from the distros was that the tools must
be renamed. This was made very clear from the beginning. All
On Wed, 15 Oct 2014, Smith Martin wrote:
But maintaining binary compatibility is now a necessary facet of
software engineering, so maybe it is time for the C++ standard to
support it. A keyword could be added to the parameter declaration,
compatibility or placeholder for example, could
On Mon, 29 Sep 2014, Simon Hausmann wrote:
Yes, with emphasis on until. Note that we are now talking about the end of
the application situation, so our agreement ends right there ;-). We are
talking about the time the QQmlEngine destructor is executed, which from a QML
engine perspective is
On Fri, 28 Feb 2014, Thiago Macieira wrote:
Em sex 28 fev 2014, às 18:30:24, Hausmann Simon escreveu:
Note that this is not a new dependency but has been there since Qt 5.0.0
(when v8 required python)
Right.
But now we need Python for a single file, in something that is almost entirely
On Fri, 29 Nov 2013, Tony Van Eerd wrote:
in the cases I am looking at, if isValid() == false, then all the other
properties are invalid, and return , -1, etc. It really does mean the
whole object is invalid.
(except maybe an 'id', in the case of, say, a Battery object - the id
telling you
On Thu, 10 Oct 2013, Olivier Goffart wrote:
Removing inline is not enough. One need to put back the definition in the
.cpp file.
Please fill a bug report. (or a patch :-))
https://codereview.qt-project.org/#change,67867
Confirmed with nm on Linux.
Harri.
Hi!
I just learnt about what looks like an ABI regression in Qt 5.2:
The function QFontDatabase::supportsThreadedFontRendering() got deprecated
in 5.2 with commit b0b786a2f05e9451a65519ab8904f55c35f51b7d:
-static bool supportsThreadedFontRendering();
+#if QT_DEPRECATED_SINCE(5, 2)
+
On Sat, 7 Sep 2013, Konstantin Ritt wrote:
one would probably prefer
[code]
job = someoperation(some parameters);
manager-enqueue(job);
[/code]
, where someoperation could be manager's registered job factory or QJob
sub-class, etc.
I am not sure why everyone prefers to have a manager ;)
On Tue, 7 May 2013, Koehne Kai wrote:
Since apparently nobody has picked the ball up, I uploaded
https://codereview.qt-project.org/#change,55521,patchset=5
We can confirm that the patch achieves the intended goal of namespacing
the discussed symbols.
It's just that one should restrain from
On Thu, 9 May 2013, 魏越闽 wrote:
I have a crash issue when use QtQuick2 and QtQuick1 together:
https://bugreports.qt-project.org/browse/QTBUG-31064
Shall I try out this patch
https://codereview.qt-project.org/#change,55521,patchset=5 ?
Yes, please.
We'll hopefully have our own test results
Hi!
Don't ask why but we ran into the known[1] segfault caused by symbol name
conflicts between Qt5Qml and Qt5Declarative. Checking the symbol tables it
appears to because by 6 symbols only:
qmlContext(QObject const*)
qmlExecuteDeferred(QObject*)
qmlAttachedPropertiesObject(int*,
On Wed, 24 Oct 2012, Jedrzej Nowacki wrote:
I added that tests durring Qt5 development, sadly streaming was never tested
with older versions. What is the bug, can I help somehow? Is it only Qt5 or
Qt4 too?
We found the reason now:
https://bugreports.qt-project.org/browse/QTBUG-27700
On Tue, 23 Oct 2012, Mitch Curtis wrote:
After https://codereview.qt-project.org/#change,37988, the Serializing
Qt Data Types page lists the QDataStream version as 13. I thought it'd
be a good idea to ask everyone who is interested to take a look and see
if the descriptions of the data
Hi!
We started publishing code coverage results of Qt 5 unit test runs as
produced by our tool Squish Coco:
http://download.froglogic.com/public/qt5-squishcoco-report/ (results)
http://download.froglogic.com/public/effectively-testing-qt5-using-squishcoco/
(setup and example)
From that
Hi!
On Wed, 27 Jun 2012, Thorbjørn Martsum wrote:
I do think that it would be a very good idea to have a QtWidget
maintainer. Not because Girish isn't a good approver (since he obviously
is) - but in order to ensure that people sees QtWidgets as alive. One of
the reasons people consider Qt
On Thu, 3 May 2012, Thiago Macieira wrote:
My suggestion is to replace them by callbacks and keep the setters in a
private header. Someone is against this idea?
Not at all.
I suggested that the Squish and Gamma Ray developers get together and put
together a proper callback implementation
On Fri, 9 Dec 2011, Friedemann Kleint wrote:
I was wondering if the QWorkspace-widget should be removed in Qt 5. It
has been out of maintenance for a long time.
Still heavily in use in the real world however.
Harri (representing several customer's interest).
On Wed, 16 Nov 2011, David Faure wrote:
Thiago suggested that I post the header file here, to see if anyone had
feedback on the (rather short) API.
Actually I'll post the .cpp file too, since the documentation of the API is
there :)
I tried without the documentation. Feedback based on
31 matches
Mail list logo
