think there may be some other benchmarks that specifically cover startup
time, but it's been a long time since I looked at it, so I don't really know
where to point you off the top of my head.
--
Robin Burchell
ro...@crimson.no
___
Developm
loper costs was seen as the better option,
as it was possible to cut back on or outsource as needed.
None of these things reflects positively on Qt's _sustainability_ to me, even
if they don't directly speak one way or another about _profitability_.
--
Robin Burchell
ro...@crimson.no
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Tue, Nov 26, 2019, at 8:56 AM, Ulf Hermann wrote:
> We're also changing the way views and delegate work. If you want to use
> the "index" in a Repeater's delegate you'll have to declare that in QML
> 3, using a required property:
>
> Repeater {
> model: 10
>
> Text {
> req
On Mon, Nov 25, 2019, at 4:55 PM, Robin Burchell wrote:
> The situation for QML3 seems to be much less clear cut
(This got sent a bit too early (hotkey mixup). Pretend this was at the bottom
of my last mail.)
I can't really comment on all of this stuff individually, because I'd b
On Mon, Nov 25, 2019, at 3:53 PM, Ulf Hermann wrote:
> Yes, but the problems with this construct are the same as with generic
> context properties: Your QML component requires some context that it
> doesn't declare. Therefore your code is not reusable and brittle wrt
> addition of properties in
MouseArea {
id: bar // is visible in scoped lookup (via 'provides' at the top)
}
}
I guess you might also be able to use this for context properties - which
suffer from many of the same unclear scoping issues rather than
de faster.
> I have the feeling that some participants of these discussions thought
> they joined an adulation club for Qt API lovers instead.
I don't agree with this kind of attack, though, even if it was not directed at
any one individual by name. Let's (_everyone_)
On Wed, Apr 3, 2019, at 1:24 PM, Giuseppe D'Angelo via Development wrote:
> I may like the overall approach. However, this would imply that such
> tests require exceptions / RTTI turned on inside QtTestLib / user code;
> is it "OK" in the grand scheme of things?
Note that testcase.prf already en
t exceptions unconditionally, but
since it's "just" test code, perhaps this isn't that big a problem.
--
Robin Burchell
ro...@crimson.no
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Wed, Jan 30, 2019, at 9:17 AM, Alex Blasche wrote:
> I am clearly missing something here. Could you please outline why such a
> monolithic repo would be good? As you pointed out yourself, the
> conceptual problem that different libraries won't walk in lockstep
> remains and segmented builds c
On Tue, Oct 30, 2018, at 5:40 PM, Oswald Buddenhagen wrote:
> on top of that there are long-term savings to be made from increased
> productivity (which several posters to this thread have confirmed or
> implied). that alone won't offset the cost vs. using cmake (it would vs.
> developing and using
n my view, a code
of conduct is not a political tool, nor a legal document (if it is done well).
It is a codified form of what is acceptable to the project, which at the purest
form might be: contributions good from all comers of all types, and if bad
things happen, here's how they are r
https://testresults.qt.io/coin/ shows the last successful integration at ~4pm,
and the integrating list is full again:
https://codereview.qt-project.org/#/q/status:integrating,n,z
So I guess it's not fixed, or something else broke?
--
Robin Burchell
ro...@crimson.no
On Thu, May 31,
On Fri, May 25, 2018, at 9:14 PM, Uwe Rathmann wrote:
> On the Qt Conn 2016 Andrew ( Knight ) presented our very first results,
> when comparing 4 different implementations of an average button.
>
> a) a button from Quick Controls 1
> b) a button from Quick Controls 2
> c) a custom button compose
On Fri, May 25, 2018, at 4:31 PM, Uwe Rathmann wrote:
> But at the time, when Controls 2 has been started everything was on the
> table and - at least from the outside - it looked like a comfortable
> situation for making good decisions. And this is what I had expected to
> happen:
What happens
ou find
surprising or unpleasant in the performance area, by all means, keep filing
issues. Just because that one bug is closed doesn't mean the story is over:
performance is a crucial feature in product development, and it is something
that we must remain vigilant about, and work on c
+1, and I'm surprised it wasn't already the case actually :)
--
Robin Burchell
ro...@crimson.no
On Fri, Feb 9, 2018, at 2:18 PM, Rainer Keller wrote:
> Hello everybody,
>
> I'd like to nominate Kari Oikarinen for approver status in the Qt Project.
>
> Kari h
don't specify an implicit
version themselves. That would reduce clutter for anything which
actually has a qmldir (which tend to be most larger more complex
things), maybe that's good enough? Then, an application template could
use that out of the box, too. I don't know offhand how hard this would
be, but I don't think it would be too difficult.
--
Robin Burchell
ro...@crimson.no
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
be a 1:1 port - but the existing plugins
provide pretty good guidance on how to lay things out, and your existing
code would be adaptable without too much work I think.
Good luck,
Robin
--
Robin Burchell
ro...@crimson.no
___
Development maili
ny such
measurements).
[1]: https://gist.github.com/rburchell/3026d3229d4211f71b947e3f9eee6d9f
-- run with qmlscene, setting QV4_MM_STATS=1 in the environment, to get
information about when the GC runs and what the impact is. Uncomment the
animation & onCompleted hook to scroll automati
On Wed, May 31, 2017, at 02:50 PM, Oswald Buddenhagen wrote:
> On Wed, May 31, 2017 at 02:38:53PM +0200, Robin Burchell wrote:
> > To me, it's implicit that each release will ideally have improvements in
> > terms of stability, so I think that there's less point in foc
"sorry we
released 1.0.0 yesterday, but it turns out that feature foo was totally
broken, have 1.0.1 today to fix that" would be newsworthy, but "we fixed
a crash that has existed for the past 3 years" - less so, but that's my
own personal view.
--
Robin Burchell
r
ceholder.
A potential additional advantage of using braces (which you include in
your examples) is that they are familiar from use elsewhere:
https://msdn.microsoft.com/en-us/library/txafckwd(v=vs.110).aspx.
--
Robin Burchell
ro...@crimson.no
___
De
Thanks for the report. I'll take a look at finishing this tonight.
--
Robin Burchell
ro...@crimson.no
On Tue, May 16, 2017, at 06:43 PM, Тимур Артиков wrote:
> Hi,
> I believe, QTBUG-60547 should be fixed before the release.
> ___
oid the
conversion penalty.
--
Robin Burchell
ro...@crimson.no
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
my opinion, and 5.9 isn't yet released.
Just my (personal) $0.02...
--
Robin Burchell
ro...@crimson.no
On Tue, May 9, 2017, at 03:35 PM, Lars Knoll wrote:
> Hi everybody,
>
> I believe I have some good news to share with regards to our releases
> moving forward. As you all
way, way more
expensive which dwarf that cost in my experience...
Robin
--
Robin Burchell
ro...@crimson.no
On Tue, May 9, 2017, at 06:43 PM, Shawn Rutledge wrote:
> This is of concern only to those who subclass QQuickItem in C++ and build
> custom items that handle touch events.
>
e handled "specially" in documentation.
And the good old subject of "variant" functions like Item::mapFromItem,
which will need special casing...
--
Robin Burchell
ro...@crimson.no
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Core already sort of being one aside: at least then it's consistent).
--
Robin Burchell
ro...@crimson.no
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
able? How is it "a new way"?
We have three targets: dev, the stable branch (more or less 5.9, since
5.8.1 is DOA) and the LTS (5.6). Adding an additional "level" there as
you seem to be proposing with a "more-stable-than-stable" would be
something I would consid
the
two being allocated in separate pieces (given that malloc usually has
some kind of book-keeping overhead).
Robin
--
Robin Burchell
ro...@crimson.no
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
here are some bugs related to this prototype, We have to solve that
> within this process.
As I said, as it stands, our implementation is currently not doing what
you need - it would need to be fleshed out to actually use the provided
arguments. However, I think that extending this
cma-402/3.0/index.html#sup-date.prototype.tolocaledatestring
Disclaimer: I'm not intimately familiar with this API, but stumbled
across it while looking into other possible alternatives for this
problem.
--
Robin Burchell
ro...@crimson.no
___
Dev
s API on anything that did not have a QGuiApplication.
I'd say that ultimately, requiring a QGuiApplication instance is a
lesser evil than providing an API that won't work universally.
--
Robin Burchell
ro...@crimson.no
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
mises here, just a rough idea would be a help so I can know when I
need to start trying to pay closer attention to anything touching the
area.
Thanks again.
--
Robin Burchell
ro...@crimson.no
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
y this early,
but do you have any idea what kind of timeframe you have in mind for
landing? Fingers crossed for "not 5.9"! ;-))
--
Robin Burchell
ro...@crimson.no
On Sat, Jan 14, 2017, at 01:37 PM, J-P Nurmi wrote:
> Hi,
>
> I'd like to request a WIP branch for the
My (slightly delayed) $0.02:
On releasing in general: I would agree that releases take too long,
often, but I am of the belief that a good part of this is a mess of our
own making. For instance, due to an end-user or project requiring a
specific version or purely out of fear that the next release
On Fri, Sep 30, 2016, at 11:00 PM, Kai Koehne wrote:
> Interesting. Indeed, I wouldn't have thought it makes any measurable
> difference. IIRC we had a qml mimizer once, I guess this is still around?
tools/qmlmin in qtdeclarative
> It's certainly not that important to me that I will spend a day o
problem or bug with the QPA plugin you're using (you mention
embedded, so I'm going to guess you're using eglfs or something like
that)
4) Relatedly, a problem or bug with the windowing system (particularly
if you're doing something rather custom. If you're using e.g.
ll
part of Qt.
Long story short, I don't see that happening. I don't think it's
actually written down or formalised anywhere, but AFAIK, fix version
tends to only be set on bugs that are actually fixed, to indicate which
version the fix is
And another +1 from me.
--
Robin Burchell
On Wed, Jun 1, 2016, at 09:23 PM, Andy Nichols wrote:
> +1 to specify the coding style to be the "butt ugly" one.
>
> I'm one of those who has (not so secretly) been committing and approving
> the offending style after all
+1 :)
On Fri, May 20, 2016, at 02:49 PM, Simon Hausmann wrote:
> Hi,
>
>
> I would like to nominate Frank for approver status. He has done a fair
> bit of surgery in the QML engine and also seems to be active on
> qtopcua/serialbus.
>
>
> I appreciate his input on my patches and I trust him to
On Tue, Mar 22, 2016, at 10:37 AM, Hausmann Simon wrote:
> I'm not sure what you'd like me to answer at this point. I think that it
> is possible to fix the
> build of these modules, the CI system is in place for that. However it
> requires a fair bit of
> work (ask Robin about qtmessagingframework
On Fri, Feb 5, 2016, at 05:58 PM, Thiago Macieira wrote:
> - QWindowSystemInterface: binary incompatible (class is \ingroup qpa,
> but not
>in a _qpa.h header, therefore it's public API)
I don't agree with this. None of the QPA files have a _qpa.h extension
(and haven't since 2012 -- see
qt
On Fri, Jan 22, 2016, at 03:57 PM, PCMan wrote:
> > The following three seems to be using at least qpa/qplatformtheme.h
> >
> > * KDE's frameworkintegration 5.16.0
> > * libqtxdg 1.3.0
> > * lxqt-qtplugin 0.10.0
> >
> > Maybe for being able to create it's own theme?
> >
>
>
> Yes, but it's not on
On Thu, Nov 5, 2015, at 06:13 PM, Oswald Buddenhagen wrote:
> > Problem: performance impact, complexity of the atom/quark solution.
> >
> to lessen the performance impact, we could have a #define to control the
> construction behavior of QSL at compile time. i'm not quite sure whether
> to make th
He already is
(https://codereview.qt-project.org/#/admin/groups/12,members) - I guess
it just never transferred to his other account.
--
Robin Burchell
ro...@viroteck.net
On Tue, Oct 27, 2015, at 09:07 PM, Richard Moore wrote:
> Not quite sure how Markus has managed not to be an appro
On Fri, Sep 18, 2015, at 08:15 PM, Nurmi J-P wrote:
> > I have some opposition to the idea because it entirely prevents us from
> > making changes if they are needed. An example of this came up just the
> > other day on IRC: Window{} has a number of major (or at least quite
> > irritating) flaws. A
On Fri, Sep 18, 2015, at 05:12 PM, Nurmi J-P wrote:
> - QtQml 2.2
> - QtQml.Models 2.3 (++)
> - QtQuick 2.6 (++)
> - QtQuick.Particles 2.0
> - QtQuick.Controls 1.5 (++)
> - QtQuick.Layouts 1.3 (++)
> - QtQuick.Dialogs 1.2
You missed QtQuick.Window I think :)
... which brings me to this:
> Is thi
On Wed, Sep 16, 2015, at 06:03 AM, Leslie Zhai wrote:
> For a new PC, there is no sharp difference between QML and QWidget, but
> in a very very old PC, how old? about 7 years ago, QML is very slow! and
> it needs to close all effects for KDE5, even that when clicked, for
> example, calendar ap
Hi,
I would like to nominate plfiorini for Approver status.
He's been quite helpful in working on Wayland (client & compositor) side
things in conjunction with the Hawaii desktop (http://hawaiios.org/),
and offering review on related patches. He also has knowledge of QPA
thanks to this work, and
It seems that nobody took proper notes of the session (oops!) so I'm
sending the notes Gunnar and I wrote up in preparation for the session.
If anyone else has any recollections they'd like to add, please go ahead
and do so :)
=
# Performance!
* Why it's important
* What needs to be checked?
Notes I took on the deprecation session follow. If I missed anything, or
misrepresented it in the notes, please chime in -- I was pretty tired
when I was writing this :)
(P.S. Did someone take notes on the QtQuick Performance discussion?)
==
Introduction
* Qt 5 is now a few years old, a lot
On Tue, Jun 2, 2015, at 11:44 PM, rpzrpz...@gmail.com wrote:
> Another concern I have is the Render Thread issues VS Gui thread issues.
Can you elaborate on this concern? The current description is impossible
to address, which might explain the lack of response.
--
Robin Burchell
On Sat, May 9, 2015, at 11:41 PM, Alan Alpert wrote:
> > Can we declare the module in Deprecated state and keep bug compatibility
> > with
> > previous versions? If people are using it to transition from Qt 4, it should
> > retain as much of Qt 4's behaviour as possible. That includes buggy
> > b
For the specific case of QtQuick1, I'd say that closing any issues that
aren't applicable to QtQuick2 (or won't be done) with a useful message
explaining the situation makes sense. It might also make sense to close
reporting of new issues for that component.
On Fri, May 8, 2015, at 06:10 PM, Hausm
Hi,
On Fri, May 8, 2015, at 02:39 PM, Frederik Gladhorn wrote:
> One question is if there is any reason to maintain Qt Quick 1 in the
> future.
I know of some projects that are still out there using QtQuick1
(unfortunately). I think that moving to remove it now might be a little
too quick, altho
On Fri, Feb 27, 2015 at 9:20 AM, Oswald Buddenhagen
wrote:
>> The argument is that it implies runtime overhead. See Robin's email for
>> numbers. This is asking for making the code slower on the very devices where
>> it needs to run faster.
>>
> i don't trust this number. i don't know how qMalloc
On Wed, Feb 25, 2015 at 10:17 PM, Konstantin Ritt wrote:
> Maybe a bit off-topic: can we introduce our own (probably customizable)
> memory allocation API, something like Apple's CFAllocator [1], and move Qt
> internals to use it instead of malloc/realloc/free (and maybe instead of
> some new/dele
Hi,
Since nobody else has replied to this yet, my understanding of what
happened with license checks is roughly as follows. I was not
involved, so YMMV - this is all just gained from observation of what's
happened - someone else please correct me if I'm wrong.
a) someone, somewhere, made a decisi
On Fri, Feb 13, 2015 at 12:41 AM, Andrew den Exter
wrote:
> First of all it's accumulative, any QML application is going to end up
> constructing many items, hundreds, thousands even and costs, even small ones
> add up. Secondly yes constructing and interacting with QObjects can be
> expensive an
On Wed, Feb 11, 2015 at 2:49 PM, Rutledge Shawn
wrote:
>> Being able to do 500+items rectangles in one frame is decent, but not
>> awesome. Being able todo 130 text items in one frame, is less than ideal,
>> given that we often use several text items per cell in a list or table. Text
>> is prob
Thanks. That's what I assumed, but it's nice to have it confirmed.
On Tue, Feb 10, 2015 at 9:24 PM, Hausmann Simon
wrote:
> Hi,
>
> Friedemann made a fix: https://codereview.qt-project.org/#/c/105750/
>
> Simon
>
> Original Message
> From: Robin Burchell
>
Can someone with Windows please take a look at unblocking
qtdeclarative/dev, or give an update if you know what's going on? It's
been failing since February 5[1](!).
The failures are consistent. See some examples: [2][3][4].
In light of it being just under a week since the last successful
integra
Hi,
Rationale: Text.AutoFormat is a terrible misfeature in almost every
case out there.
Design implications: In many cases in applications, a format is not
specified, with the assumption that only plain text will ever be
displayed because that is all it is ever tested with. In actuality,
this is
On Mon, Dec 15, 2014 at 12:37 PM, Massimo Callegari
wrote:
> So, my application runs on Maynard using "-platform wayland" but all the
> windows are not decorated. So basically I have the same result as if I run
> it on eglfs.
See: https://codereview.qt-project.org/#/c/93128/
> So, my questions t
On Fri, Sep 26, 2014 at 5:17 PM, Nichols Andy wrote:
> My suggestions for replacement would be either Giulio Camuffo who as been
> main driver for the QtWayland project this year, or Jorgen Lind who was the
> previous QtWayland maintainer and who still has a deep interest in the
> project.
+1
On Fri, Sep 19, 2014 at 10:48 PM, Jeremy wrote:
> It’s the repo hosted on qt-project.org and clones such as qt.gitorious.org
> that I’m wondering about. Leaving qtjsondb at its current URL is not what I
> would expect for something that is not part of the Qt 5 bundle. Do we start a
> qt-abandon
Thanks for starting the thread, Alex. I still hadn't had time to
really do my homework on my side of this problem, apart from talking
to you :-)
On Mon, Aug 25, 2014 at 5:25 PM, Blasche Alexander
wrote:
> It is my understanding that the current Linux release binary packages are
> built on Ubuntu
On Mon, Aug 18, 2014 at 7:57 PM, Allan Sandfeld Jensen
wrote:
> Is it a problem that they have fake dependencies listed in gerrit? I often
> upload lists of patches like that, and land them out of order as they get
> reviewed. It appears to pose no particular problem, except that it can look a
>
Hi Marc,
It doesn't specifically do what you want, I think, but you might want
to take a look at Android's repo tool:
https://source.android.com/source/developing.html
https://source.android.com/source/using-repo.html
I've been using it to interact with Qt's Gerrit for quite a while now
and am p
On Thu, Aug 14, 2014 at 9:52 PM, Pier Luigi wrote:
>>> Now the question is: how can Qt applications set this app_id?
>>>
>>> Since app_id should be the same for all xdg surfaces I would propose
>>> adding an applicationIdentifier property to QGuiApplication.
>>
>> Why do they have to? Just like WM
On Thu, Aug 14, 2014 at 8:15 PM, Pier Luigi wrote:
> This used to be the class in wl_shell_surface and I know the concept
> exists on X11 as well (WMCLASS if I recall).
WM_CLASS I think, but don't quote me, it's been a long, long time
since I've looked into anything X11 related.
... a quick grep
On Fri, Jul 11, 2014 at 11:13 AM, Hunger Tobias wrote:
> I see why you would want journal data in your output, but I do see a
> problems making that work for remote debugging/running. Even sailfish is
> apparently forcing output to stderr when starting applications on-device
> via Qt Creator.
Don
On Wed, Jul 9, 2014 at 11:43 PM, Thiago Macieira
wrote:
> == Problematic ==
> Qt 5.3 and dev are currently able to send the output of qDebug, qWarning and
> the rest of the logging framework to somewhere other than stderr. That's done
> on Windows, BlackBerry, Android, and on Linux systems with jo
On Wed, May 28, 2014 at 11:19 PM, Mathias Hasselmann
wrote:
> As a side note: A similar problem exists for the messaging framework
> libraries (QMF). Its library names are:
There's renames for that planned, but not yet executed. See the
archives for my original mail on the subject.
__
Hi,
On 23 Apr 2014, at 14:14, cincirin wrote:
Sorry for re-open this topic, but as someone else already pointed out,
what do you think about the Unreal engine guys to abandon the unreal
script which was used until now for many years ?
I don’t think this topic is really suited for this list, bu
On Thu, Jan 23, 2014 at 8:48 AM, Thiago Macieira
wrote:
> On quinta-feira, 23 de janeiro de 2014 07:37:14, Knoll Lars wrote:
>> On 23/01/14 00:32, "Thiago Macieira" wrote:
>> >However, knowing Valerio from the past, I would be ok with giving him
>> >approver
>> >rights throughout.
>>
>> +1 (inclu
On Mon, Feb 17, 2014 at 1:41 AM, Sze Howe Koh wrote:
>>> The repository is currently comprised of two main libraries:
>>> QmfMessageServer and QmfClient. I would propose:
>>>
>>> QmfClient => QtMail
>>> QmfMessageServer => QtMessageServer
>>>
>>> Classes in QMF are already using the QMail* prefix.
Hi,
Sorry for the delay in replying.
On Mon, Feb 10, 2014 at 6:34 PM, Konstantin Ritt wrote:
>> QmfClient => QtMail
>> QmfMessageServer => QtMessageServer
> Two modules in one repo (aka QT += mail messageserver), right?
Yes. Same situation as it is now.
> BTW, are you planning an API review/re
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.
QMF's
Hello,
I'd like to propose Approver rights for Valerio on messaging framework.
Justification: Valerio has worked on (& with) QMF for a long time, on
both the Nokia N9 and now with us at Jolla on QMF-on-Sailfish. QMF
also doesn't exactly have an abundance of approvers, so especially now
that I'm d
Hi Alan,
On Mon, Jan 20, 2014 at 11:33 PM, Alan Ezust wrote:
> Meego is still a "supported" platform, with Jolla and all, right?
While we use a number of components that were part of or have their
roots in MeeGo, Sailfish is a rather different beast, particularly on
the UI level. Think of it as
Hi Elvis,
On 27 Dec 2013, at 03:23, Elvis Lee(KwangWoong Lee)
wrote:
I’m looking for good way to handle objects which have called deleteLater.
According to what I understood until now, there are 2 ways to handle them.
One is making control return to the event loop. Another is calling
QCoreApplic
On Tue, Nov 19, 2013 at 6:22 PM, Frederik Gladhorn
wrote:
> (did you know that improving unit tests is one of the most fun things ever and
> leads to instant fame and glory? you should try it too some day)
http://qtmemes.tumblr.com/post/67517056364/nice-try-fregl
_
On Thu, Nov 14, 2013 at 3:08 PM, Topi Mäenpää wrote:
> Or rather could, if the interface wasn't a moving target.
If an interface is a moving target, that means that trying to promise
compatibility for it is generally a bad idea.
Once something is made public, you're stuck with it. For a very lon
On Wed, Nov 6, 2013 at 6:01 PM, Lisandro Damián Nicanor Pérez
wrote:
> In Debian we are considering if the problem of breaking ABI without a soname
> bump is worth the effort for armhf, but it would be also good to try and
> coordinate between distros so as to try to keep binary compatibility betw
+1
On Thu, Oct 24, 2013 at 8:50 PM, Frederik Gladhorn
wrote:
> Hi,
>
> I'd like to nominate Gatis as approver. He has been with us in the Digia Oslo
> office for quite some time now. Gatis fixed many input/key handling and XCB
> issues and started looking at sensors lately.
>
> Patches by Gatis:
And today marks weekday 15 since the proposal, with no negative
comments. I guess that means it's time to congratulate Andrew.
Can someone please grant the necessary JIRA/Gerrit rights?
Thanks,
Robin
On Fri, Aug 30, 2013 at 1:37 PM, Robin Burchell wrote:
> Hello,
>
> I'
On Thu, Sep 12, 2013 at 9:24 PM, Knoll Lars wrote:
> We might be able to simply cache the time zone offset once and cache it.
> Then it should be at the same speed.
This would also probably provide hidden wins in various places, making
changes like b9ef4a9c3047228ec007ac81ff0a304f8cc274b7 in qtba
On Mon, Sep 9, 2013 at 3:21 PM, BogDan wrote:
> I'm trying to stage this https://codereview.qt-project.org/#change,64292
> patch, but CI complains that 2 files don't contain "a license header". But
> I'm pretty sure they do.
At a guess, they are there, but aren't valid. Date ranges aren't
a
+2 :)
(and sorry, Steve, this time to the ML)
On Fri, Aug 30, 2013 at 3:05 PM, Stephen Kelly wrote:
>
> Hello,
>
> I'd like to nominate Thorbjørn for approver status. Thorbjørn has been
> contributing to Qt for almost two years, and has been quite active in the last
> year in submitting patches
Hello,
I'd like to nominate aknight for approver status. Andrew has been
doing some solid work that I've noted in QtWayland (and with wayland
in general), and also appears to have some solid knowledge of Windows
from his dashboard:
https://codereview.qt-project.org/#dashboard,1001190. Also useful:
Hi,
(apologies in advance for the wall of text)
It's inevitable when working with Qt that sooner or later, you
probably have a desire to work on tracing Qt - or at least part of it.
Qt Creator's QML profiler is one such very prominent example of an
area where this may be useful, but there are man
On Tue, Aug 20, 2013 at 12:14 AM, Thiago Macieira
wrote:
> Right now, I've got most modules compiling with -Werror with GCC 4.7. I'd like
> to start adding the CONFIG to enable the flag.
>
> Objections?
One potential problem I see (I haven't looked at your changes, sorry,
holiday and lack of time
On Thu, May 2, 2013 at 9:40 PM, Alan Alpert <4163654...@gmail.com> wrote:
> Given those guidelines, our possible answers are either "No (i.e.
> there is no permission given for public logging)" or "list it in the
> channel topic for logged channels (and possibly leave some channels
> deliberately u
Hi,
In addition to hosting qt_gerrit, I have for a very long time
generated IRC statistics for #qt and #qt-labs. These were perhaps not
all that well publicized, but they did exist.
After my recent server outage, obviously, this all got lost. I got
around to restoring it this evening (see http://
On Thu, Apr 18, 2013 at 2:05 PM, Robin Burchell wrote:
> - he announces gerrit changes in qt_gerrit
Ahem. #qt-gerrit. I shouldn't be trusted with an email client as well
as server management, apparently. :)
___
Development mailing list
Develo
Hi,
A short PSA: qt_gerrit had some downtime this morning (and is now
back, at least in a few channels).
The post mortem: some fat-fingered user of that server hosting
qt_gerrit (i.e. me) made a rather serious mistake that meant the
server needed reinstallation. The code for qt_gerrit was safe (a
On Tue, Mar 5, 2013 at 8:28 AM, Dominik Holland
wrote:
> Yes this makes sense and it's similar to my solution... But why do you
> need to multiply it with 0.9 ?
To start fetching (hopefully) before the data is really needed. Models
may involve asynchronous access (network etc) which might take a
1 - 100 of 239 matches
Mail list logo
